100 Reviews and Ratings
23 Reviews and Ratings
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
If you want to stream high volumes of data, be it for ETL streaming or event sourcing, Google Cloud Pub/Sub is your go-to tool. It's easy to learn, easy to observe its metrics and scales with ease without additional configuration so if you have more producers of consumers, all you need to do is to deploy on k8s your solutions so that you can perform autoscaling on your pods to adjust to the data volume. The DLQ is also very transparent and easy to configure. Your code will have no logic whatsoever regarding orchestrating pubsub, you just plug and play. However, if you are not in the Google Cloud Pub/Sub environment, you might have trouble or be most likely unable to use it since I think it's a product of Google Cloud.
Easy commissioning of APIs.Great policies to control access.Easy mock services for testing.Incentivized
With a pub/sub architecture the consumer is decoupled in time from the publisher i.e. if the consumer goes down, it can replay any events that occurred during its downtime.It also allows consumer to throttle and batch incoming data providing much needed flexibility while working with multiple types of data sourcesA simple and easy to use UI on cloud console for setup and debuggingIt enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalabilityIncentivized
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
Would be nice if the queue could be extended beyond 7 days.We found it a bit tricky replay unacknowledged messages when needed.Incentivized
It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.
It has many libraries in many languages, google provides either good guides or they're AI generated code libraries that are easy to understand. It has very good observability too.
I have never faced a single problem in 4 years.
It's very fast, can be even better if you use protobuf.
They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.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
Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using GCP only for Pub/Sub the choice depends on other variables.Incentivized
You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.
We can always think of positive ROI impact on businessIt helps to easily facilitate the design, deployment, and maintenance of our APIs
Increased Efficiency with reliable and Google managed services up all the time wit Disaster Recovery in place as wellDefinitely Lower costs being a cloud based solution and easier to setupFaster Project delivery and go to market plan for the business use cases basis this technology at the back endIncentivized