{"repo":"rithinch/event-driven-microservices-docker-example","free":true,"listed":false,"github":"https://github.com/rithinch/event-driven-microservices-docker-example","clone":"git clone https://github.com/rithinch/event-driven-microservices-docker-example.git","description":"🐳 Simple example of event driven communication between microservices, based on Docker containers, Docker Compose and RabbitMQ. Microservices are implemented in Node.js using Koa.","language":"JavaScript","stars":281,"topics":["event-driven-microservices","nodejs","docker","rabbitmq","boilerplate","koa","rest-api","mongodb","jest-tests"],"license":"MIT","category":"deployment-docker-iac","readme_excerpt":"Event-Driven Microservices Backend Sample Proof of Concept for a scalable Local News Application, based on simplified event-driven microservices architecture and Docker containers. :whale: Introduction This repo presents a proof of concept of a highly scalable local news application backend. The application was developed keeping a local news domain in mind, but the principles used can easily be applied to design software solutions for any domain. One of the primary business requirements for a local news application domain is that it has to be blazing fast since news updates are requested very often by customers and it would largely benefit the business if the system architecture can support such scale. After evaluating several different system architectures, a hybrid event-based microservices architecture was designed to meet the requirements. This approach leverages RabbitMQ message broker for events communication between the microservices and all the services are containerized using Docker such that they can independently developed, deployed, monitored and scaled. Full Application Backend Demo The following video demo shows all the currently supported features for the proof of concept. It goes through how to run the application stack and perform operations requesting the api's. Event-based communication samples are highlighted in following two scenario's: When a new article is added through articles-management service, the notification service picks up that event and sends ","default_branch":null,"files":null,"tree":[],"storefront":"/r/rithinch","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/rithinch/event-driven-microservices-docker-example/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}