Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Canvas now exposes the notification/alert capabilities and metadata retrieval as microservices which can be readily consumed. Earlier it was monolithic server side architecture with the UI and server components interwoven and exposed as single unit. Now the server side components have been restructured after implementing the independently functioning services (Microservices) by distributing the requests to individual microservice components.


Benefits of implementing Microservices are:

  • Independent deployment of modules.
  • Load distribution in the server.
  • Reduction in server startup from 7 seconds to 1 second.
  • Cloning multiple copies of the container making it faster to process the requests. This increases application scalability.





The incoming requests are split and distributed across the container based on calls specific to server and calls specific to microservice components. Therefore instead of one server handling all the requests, these are routed across server components to process the request.
To deploy and orchestrate the services, Docker images are created to encapsulate the microservice and deploy those in the server. Docker images will be created for each microservice component to create a stable environment with the necessary WAR.

  • No labels