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.
Visualizing cross-channel campaign performance can blend data from a few different sources to compare performance metrics like spend, clicks, and conversions side-by-side in a single view, which helps in quick budget reallocation decisions. When dealing with massive volumes of data (millions of rows) or highly complex queries, Looker Studio dashboards can become slow, laggy, or even crash. Performance issues are a frequent complaint when working with large datasets, making it unsuitable for enterprise-level companies
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
Breath of data - the number of ways to interrogate the data is endless, and the options to view metrics alongside each other make for comprehensive datasets.
Data visualisation and customisation - the options for presenting data and separating out across pages allow for clean visuals and segmented information.
Easy shareability/usability - a quick and simple tool to introduce colleagues to, and easy to grant access for them to be able to view the data, without having to understand the setup itself.
It needs better handling of complex logic. We often need workarounds to perform complex custom calculations, and it can be really unpleasant at times.
Felt it got slow with a larger data set, and in one minor report, we had to set up time filters so that calculations during spikes could be traced more quickly.
Compare to competition they need to improve with notification things.
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 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.
Looker Studio is easy to use, and it offers a sufficient variety of predefined visualizations to choose from. It's easy for us, and anyone can set up basic reporting without extensive data visualization skills. The interface layout is easy to understand, and it doesn't take long to get used to.
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.
Looker Studio is far easier to implement, stand up, and learn. The interface is simpler and user-friendly for various levels of data visualization/analysis knowledge and experience. The biggest benefit of Looker Studio, however, is its ease of connection to GA data and speed. Furthermore, since it is an online program/tool, it requires less CPU/battery/storage on the user's device.
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.
