Amazon API Gateway vs. Azure API Management vs. Microsoft Viva Engage

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

APIM is useful for the standard scenarios:

1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.

2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.

3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.

Incentivized

Yammer is great when you have a company culture that encourages friendly collaboration and communication. It can be a great supplement (but certainly not a substitute) for bonding and sharing ideas and thoughts. Certain channels can be really successful, too, like a channel where people can post dog pictures or something fun like that!

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

• Easy commissioning of APIs.
• Great policies to control access.
• Easy mock services for testing.

Incentivized

• Providing a platform for social news in the company where "bottom up" topics can percolate freely across department
• Social networking across the company where folks can divide their work into topics instead of teams
• Basic collaboration within a group including document sharing with ability to pin documents to a team

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

• Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
• As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
• Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.

Incentivized

• Although the social enterprise network works very well, there is room for some slight improvement - such as the ability to attract users. By being part of the Microsoft Office Suite, it is offered as an "add-on" and many overlook it and see it as unnecessary at first. It would be smart for Microsoft to sell it as its own product so it could gather more popularity as a "social network".
• Giving an option to filter results could be better as well as giving an option to turn off the "recent activity" bar on the home page.

Incentivized

Microsoft is dedicated to continual improvement on Yammer. They realize the value that Yammer brings to the table with their clients. In the short time that we have had Yammer implemented, we are just now beginning to see the strong impact it has on becoming more effective and efficient around collaboration.

It is a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system

Incentivized

Overall easy to use and intuitive, although limited in the possibility to personalize layout and look & feel of a site. Some functionalities are not easy to use, like document editing, but some others are quick and effective (posts and tagging above all). Performance and responsiveness of the Yammer site is typically acceptable, in my experience.

Very available

It's a simple product but it does provide value.

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

We have never had to use the support for Yammer. The tool works well and we have not come across any bugs. User Interface is simple and easy to use, similar to other forum type products, thereby removing the need for any extensive training. Team members are invited in and immediately are able to start using the tool.

Incentivized

The training that Microsoft provides is very generic training for Yammer. I like the fact the training is short and easy to understand

We organically implemented the product

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

Azure APIM vs Amazon API Gateway:

1) Azure APIM was a complete package that included a developer portal.

2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.

3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.

Incentivized

Our team briefly used Salesforce.com's Chatter product before switching over to Yammer in 2012. While Chatter is essentially the same product as Yammer, it left much to be desired. Chatter's design was (and remains) clunky and difficult to navigate. Yammer is a simple, easy-to-use product that offers similar functionality as Salesforce's Chatter.

Incentivized

• 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

• We can always think of positive ROI impact on business
• It helps to easily facilitate the design, deployment, and maintenance of our APIs

• My company is pleased with the positive impact Yammer has created departmentally and on an individual basis with work flow efficiency.
• Adversely, most old and new employees are more familiar with SharePoint, causing the company to pay for training for all current and incoming employees.
• As Yammer becomes more widely used, the need for training may diminish, which is where we will see our return on investment, as the product clearly provides a more effective form of file sharing and communication between employees and their department.

Incentivized