Make Microservices easy peasy
Use Cases and Deployment Scope
Used for multiservice architecture to delivery ESB system for banking domain. As ESB is [a] vast Microservices system, it needs to be utilized in many ways for API exposure as well as consumption. So to make such Microservices system more synchronized and scaleable as per need to manage resource utilization and monitoring system using graphQL.
Pros
- Graphically representation in GraphQL
- Scaling system
- DevOps management
Cons
- Quota enforcement can be simplified
- Caching mechanism for API with akamai can be improved
- Gateway configuration can be simplified as details are not much elaborate
Return on Investment
- Decrease in time required for deployment and monitoring by significant amount causing less support resources needed
- Scaling applications on month-end at high usage time has reduced TAT time for issues and no of issues occurring
- Quota enforcement has allowed [managing] multiple systems and their needs in respective stakeholders hands and reduced infra teams involvement in [the] management of reoccurring problems
Alternatives Considered
AWS Auto Scaling and AWS CodeDeploy
Other Software Used
AWS CodeCommit, Google Authenticator, Apache Camel