Cloud PubSub Multi-Team Design

When designing asynchronous microservice integrations in Google Cloud using Cloud Pub/Sub, it is important to consider the ownership of services. This will help ensure that decisions are made in the best interests of all teams involved, and that no team is unduly burdened. It is also important to allow each team to make their own tooling choices. This will give teams the flexibility they need to work efficiently and effectively. Today's video explains why certain design patterns do not work well for asynchronous microservice integrations. It also offers an alternative solution that can be used to achieve better results. It may be helpful to review your own designs in light of the information presented in the video. This will help ensure that your designs are aligned with best practices and that they will meet the needs of all teams involved. 00:22 - Tables of contents 01:18 - Cloud PubSub, let's break it down 02:12 - A design for a single team 03:17 - A multi-team design with common pitfalls 03:27 - Push Subscriber with Cloud Run Service 05:18 - Pull Subscriber with Cloud Run Job or GKE 06:57 - BigQuery Subscription 08:04 - Solution with clear separation of ownership while being flexible 10:11 - Now you might ask, how exactly... 14:12 - See it on Google Cloud 17:56 - Summary Slides: https://docs.google.com/presentation/...