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.
Looker Studio is well-suited for those wanting to analyze web/site data and performance quickly. It is simple enough to learn/use for quick report-building or drilling into data. Looker Studio is easier to use/understand than the GA4 console and thus has a better UI/UX. It is an efficient tool for fast, simple data needs—especially for team members with limited analytical capabilities and knowledge.
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
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 the simplest and least expensive way for us to automate our reporting at this time. I like the ability to customize literally everything about each report, and the ability to send out reports automatically in emails. The only issue we have been having recently is a technical glitch in the automatic email report. Sadly, there is almost no support for this tool from Google, but is also free, so that is important to take into consideration
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.
It is not ideal and requires time and dedication to understand how to work with it. Also, it has a lot of limitations around data it can accept. But in most cases, this tool is sufficient for everyday tasks of product and marketing departments. I wouldn't say that the interface is very user-friendly, but for people who regularly work with analytical tools, it must be ok.
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.
I give it a lower support rating because it seems like our Dev team hasn't gotten the support they need to set up our database to connect. Seems like we hit a roadblock and the project got put on pause for dev. That sucks for me because it is harder to get the dev team to focus on it if they don't get the help they need to set it up.
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.
The free version of Looker Studio is still better than the leading enterprise-embedded BI tools, despite its weaknesses. The leading embedded BI platforms have terrible visualizations that can be spotted a mile away. They are also primarily locked to a grid, making it very hard to fully customize. The price point is also a major deterrent, since users end up paying for lots of features they might never use. Looker Studio has weaknesses on the blending and modeling side, but we've been able to get by via connection to GBQ and transformation done in dbt.
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.
