Diji's Blog

Very frequently microservices need to talk to each other. For performance reasons, this communication is done asynchronously. There are two major models of asynchronous interprocess communication(IPC). Point-to-point communication Communication is from a particular microservice to another. The client sends a message to the consumer, the consumer process the message and may send a message back to the client if a response is expected. Publish-subscriber A single microservice broadcasts a message which is then consumed by zero or more microsevices which are listening for this particular message type of message. This post is focused on implementing point to point communication between two microservices using Spring Boot, Java Messaging System(JMS) and Amazon SQS. SQS Queues A message queue hold all the messages of a particular type for a microservice to process. Microservices communicate by sending messages to each other's queue. Maven dependencies Three dependencies

The acquisition of MySQL, the world's most popular and widely used DBMS(Database Management System) by Sun Microsystems was generally well received by the open source community and users of the software. After all, Sun was a notable contributor to open source software. She even had had several open source products of her own including OpenSolaris, OpenOffice suite, Netbeans, Glassfish and the Java platform. Besides, the DBMS was now under the control of a more powerful company. The future of MySQL was bright. However, all that was not going to last. Despite being owners of one of the most influential IT technologies Java, Sun Microsystems was struggling financially. Losses were declared at the end of most fiscal quarters. It was soon evident that Sun was not going to survive on her own. The question was really not whether an acquisition was going to happen but rather when it was going to take place happen and who was going to acquire her. Early 2009, news of an IBM-Sun merger beg