Canvas now offers Microservice capability for its existing functional modules which restructures the monolithic interwoven server-side architecture into independently functioning Microservices. However, by default all requests will continue to follow the existing route (monolith style). Implementation teams have the choice of either using the microservices offered by Canvas or use the default monolithic architecture. When using Canvas’ microservices, all client requests on your application will be distributed to respective individual microservice components to balance the load.
The functional capabilities that are now exposed as independent microservices that can be readily consumed are:
Metadata service
...
Node JS Metadata Service
...
Java Metadata Service
...
Business Data Cache service
The business data cache service fetches the application data such as user details, product details etc. to be displayed in grids, charts etc. The business data cache service exposes the data fetching operation as APIs and the data are retrieved from MongoDB cache. These APIs can be used to access the business data using named services where the service returns the data based on entitlements.
| Note |
|---|
The implementation teams have to provide their application JAR to Canvas team to bundle the application JAR along with this service to fetch business data from application tables. |
Authorization service
...
Authentication service
...
Notification service
...
Canvas requires the configuration of certain components to enable microservices.
Refer the following topics for more information
| Page Tree | ||
|---|---|---|
|