Make Microservices easy peasy
December 23, 2021
Make Microservices easy peasy
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Akamai API Gateway
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
- 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
Akamai [API Gateway] helps better in terms of representation of graphQL and its consumption in monitoring system making a package for deployment speed with monitoring and scaling application with all services and utilizing most of a system without much knowledge of other aspects. Also, [a] user-friendly system helps people to handle [the] system with necessary options
Do you think Akamai API Gateway delivers good value for the price?
Yes
Are you happy with Akamai API Gateway's feature set?
Yes
Did Akamai API Gateway live up to sales and marketing promises?
Yes
Did implementation of Akamai API Gateway go as expected?
Yes
Would you buy Akamai API Gateway again?
Yes
Comments
Please log in to join the conversation