Enterprise Integration for Beginners

  Just released! It is a great and humble feeling to release my very first book “Designing Microservices Platforms with NATS” on 19th November 2021 (first edition). Cover Image of Designing Microservices Platforms with NATS You can read it through  Amazon ,  Barnes and Nobel ,  Packt , and other distributors worldwide. Why another microservices book? I hear you! Why there are so many books about microservices? Is that so complicated? Why do people use it? Those were some of the questions I had when reading about microservices in the wild (internet). The more I read through, the more I realized that there is something missing.  That missing piece was the first principle and the simplicity when building microservices. That is why I thought of writing a book on microservices that people can understand and start building applications with microservices without falling into the trap of ultra complexity. This book focuses on building applications first and includes al...

Distributed systems has come a long way from where it started and have a long way to go. With more and more people connected through telecommunication technology over the largest distributed system on the planet which is the internet, the demand for an efficient distributed architecture is ever so important today. This is not a tutorial on distributed systems though. Rather some thoughts on building a futuristic distributed system which addresses the challenges of the modern needs keeping the focus at the messaging styles. In a distributed system, messaging plays a pivotal role. Data flows from one system to another through messages. Different protocols and formats are used to share data within a distributed system as messages or events. Another key aspect of messaging is the nature of communication The below post explains different messaging styles and how those can be used to build a future proof distributed system for the enterprise. https://medium.com/@chanakaudaya/a-futuris...

Apache Kafka has evolved as the defacto standard for building reliable event based systems with ultra high volumes. The unique, yet simple architecture has made Kafka an easy to use component which integrate well with existing enterprise architectures. At a very high level, it is a messaging platform which decouples the message producers from the message consumers while providing the reliability of message delivery to consumers at scale. Kafka has message producers which send messages (events) to kafka which kafka stores in a entity called a topic which will deliver the messages to one or more consumers in a reliable manner. There can be different types of producers and consumers depending on the use case. In the below post, I'm explaining how kafka architecture works and integrate with other systems. https://medium.com/@chanakaudaya/understanding-apache-kafka-the-messaging-technology-for-modern-applications-4fbc18f220d3

Messaging has been the fundamental communication mechanism which has been succeeded all over the world. Either it is human to human, machine to human or machine to machine, messaging has been the single common method of communication. There are 2 fundamental mechanisms we used to exchange messages between 2(or more)parties. Synchronous messaging Asynchronous messaging Synchronous messaging is used when the message sender expects a response to the message within a specified time period and waiting for that response to carry out his next task. Basically he “blocks” until he receives the response. Asynchronous messaging means that sender does not expect an immediate response and does not “blocks” waiting for the response. There can be a response or not, but the sender will carry out his remaining tasks. Out of the above mentioned technologies, Asynchronous messaging has been the widely used mechanism when it comes to machine to machine communication where 2 compute...

Business Requirement Today, your business is all about working with information. If you are a business owner and if you need to grow your business, best way is to make it accessible over the internet. When your business grows, it can be thousands, millions or even billions of people interacting with your business every second. If you think about online stores like ebay, amazon or google play, they need to process millions of messages per second. When a customer interact with such a system, that information need to saved in somewhere (ex:database). This can be illustrated as below. In the above figure, Client interacting with a web browser and access your system which is implemented as a web service which is hosted somewhere in the internet. At a given moment, there can be any number of parallel users accessing your business. To handle each and every request from the customers, you need to have a robust, reliable messaging system. How WSO2 can serve your requirement? WSO2 ...