Composite Microservices / Cobble Microservices ...

6 downloads 0 Views 29KB Size Report
zookeeper and Cassandra so, it works in a highly distributed manner, which supports HA & scalability. Advantages: •. Increase performance since the overhead ...
Name: Composite Microservices / Cobble Microservices.

Purpose: Simplify and decrease complexity of developing, managing, and deploying microservices

Prototype: •

Every business Service has a container configuration file, which describes required infrastructure services including it is API-gateway, which would be deployed as well in a container.



Every service would be deployed in a container.



Common and infrastructure services would be deployed in containerin-container.



Business Service container can have only once business service but can have one or many instances of this business service



Infrastructure services should work in cluster active-active models like zookeeper and Cassandra so, it works in a highly distributed manner, which supports HA & scalability.

Advantages: •

Increase performance since the overhead of communication between Gateway and services removed and replaced by inter-communications inside the container



Enhance availability and scalability after handling SPFs for the Gateway and other common and infrastructure services like discovery and configuration services



Simplify development, deployment, and test

Disadvantages: Consume more bandwidth between common and infrastructure services as they work in active-active model

Solutions: •

Using Microservices Chassis which provides most of the cross cutting concerns services with client agents



Creating Composite Docker Containers with Docker Compose so every business service container has infrastructure & common services's agent inside its container