Google offers Cloud Pub/Sub, a managed message oriented middleware supporting many-to-many asynchronous messaging between applications.
N/A
SAP Integration Suite
Score 8.5 out of 10
N/A
SAP Integration Suite is an integration platform-as-a-service (iPaaS) that helps quickly integrate on-premises and cloud-based processes, services, applications, events, and data. It is used to accelerate innovation, automate more processes, and realize a faster time to value.
$11,199
per year
Pricing
Google Cloud Pub/Sub
SAP Integration Suite
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Google Cloud Pub/Sub
SAP Integration Suite
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Access to free tier services does not expire while there is an active Pay-As-You-Go or CPEA account with SAP. Once a free tier service limit has been reached users have the option to update from a free to a paid service plan in the same account.
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.
In our case to have a such a poweful middleware in the cloud, give us a lot of benefits such as maintenance and support. In the integration part to be able to connect SAP and Non SAP applications makes SAP Integration Suite a good investment when our master data in this case is in S4HANA. Less appropriate is that sometimes the updates in production tenant failed and they have to downgrade or repair the issues. Affecting the usage of the tool. I guess SAP team have to be more aware of performing the changes and tested well on development environments and then when they know for sure that is the correct way to go with the update put it in production.
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 sources
A simple and easy to use UI on cloud console for setup and debugging
It enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalability
Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective
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 is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.
It is easy to create Google Cloud Pub/Sub topics from both Web Console and CLI commands.
Google Cloud Pub/Sub supports creation of one or more subscriptions.
By supporting a BigQuery Pub/Sub subscription to automatically write to a BigQuery table it simplifies development by avoiding implementation of a custom micro service for writes to BigQuery.
The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.
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.
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.
SAP Integration Suite was already part of our SAP stack, part of Business Technology Platform, with out-of-the-box integration with S/4 HANA transactional and ERP system that we are using as our main back-end. Thus, we are achieving significant Total Cost Optimization benefits or running both solutions on the same platform, hosted on Azure cloud.
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.
