Microservices Ecosystem

The incoming requests are split and distributed across the server container based on the required operation and invokes the specific module. Therefore unlike the monolithic architecture where a single server handles all the incoming requests, the framework in now designed to route the requests across server components to process the request.

Canvas has integrated an ecosystem for the functioning of microservice modules involving the public facing and demilitarized components.

The following architecture is the representation of microservice ecosystem with components such as HA Proxy, NGINX, WSO2, ELBK, Nagios, Kafka, Kubernetes, etc.

HA Proxy: Reverse proxy to face the incoming request and balance load.

WSO2: API Gateway for extra layer of security and provides service mash-ups by assembling multiple microservices into a larger functional service.

Mongo DB: Stores application data and metadata that is sent by Node service for faster and distributed caching.

Redis: Stores session and entitlement information as in-memory cache.

GRPC: Improves performance and reduces latency by bringing down communication time between services.

JWT: Provides security and authenticates incoming requests.

Kubernetes: Provides load orchestration and auto scaling.

Docker: Deploys images on build services.

Kafka: Broadcasts messages between services.

ELK: Centralized log monitoring tool.

For more information on configurations, refer Configurations of Component s.