So, you’ve said goodbye to the monolithic application and refactored it into services. You are shipping faster and the code is cleaner. But the complexity of communication between the services is causing performance issues. And every time a new team needs to integrate, it’s a whole lot of meetings. By Priyanka Vergadia, Kir Titievsky.
The time has come to consider asynchronous communication, where services publish and react to events reliably delivered by a messaging system. In this model, a service needs only to do its computation on an event and publish it to Pub/Sub. It does not need to accommodate the different latency and availability characteristics of the downstream services. In fact, it needs to know nothing about them. This article introduces you to Pub/Sub and how it works:
- Pub/Sub
- Pub/Sub Lite
- How does Pub/Sub work?
- Pub/Sub features
- Pub/Sub use cases
Pub/Sub works as a messaging middleware for traditional service integration or a simple communication medium for modern microservices. Push subscriptions deliver events to serverless webhooks on Cloud Functions, App Engine, Cloud Run, or custom environments on Google Kubernetes Engine or Compute Engine. Low-latency pull delivery is available when exposing webhooks is not an option or for efficient handling of higher throughput streams. You will also find link to video explaining the concept in this article. Excellent read!
[Read More]