Amazon API Gateway vs. IBM Decision Manager Open Edition

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

Incentivized

Red Hat Decision Manager is well suited for developing a microservices-based application architecture where reusable components / APIs can be used across different end-user applications. It however may not be well suited for use cases where business users need low code / no-code environment to maintain business rules themselves without any developer / IT team support

Incentivized

• API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
• API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
• API Gateway's pricing can be very attractive for services that are accessed infrequently.

Incentivized

• Business rule management for filtering the candidate
• Automate the possible decision making which reduces the time and increase the productivity
• Whenever business rule changes based on the client requirement.

Incentivized

• Client certificates are troublesome when trying to attach them to API GW stages.
• Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
• Creating internal/private APIs, particularly with custom domains, can be unintuitive.

Incentivized

• It should be easy to use because it needs more knowledge
• You should be trained to your partner well
• Well Documentations are needed

Incentivized

Red Hat Decision Manager can be scaled and adapted to meet the automation needs of the organization as it grows by reusing the components and business rules data which provides a high ROI on the renewal costs.

Incentivized

Implementation phase is very difficult .Of course ,you need to know bunch of things about cloud,container,automatization

Incentivized

We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.

Incentivized

The support for Red Hat decision Manager can be improved to be more omnichannel with better response times for the customers.

Incentivized

For high volume and / or complex set of legacy business rules, plan for adequate time for data migration activities.

Incentivized

When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.

Incentivized

If you have a low budget to invest probably JBoss BRMS is the option for you, if your budget is not restricted you'll probably like to consider Bizagi

• ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
• For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
• Service is easy to set up authorization and it is easy to manage.

Incentivized

• Quickly write business rules
• Computers can take decision
• Complex event processing

Incentivized