Background

This time I am looking forward to exploring Pub/Sub and Pub/Sub Lite. The main reason is that we have options and to identify the behavior between both products and to test with a quick start.

Notes: this is only for a conceptual test, for more through deployment please follow the documentation.

Choosing Pub/Sub or Pub/Sub Lite

This is one good reference to crosscheck the option on which to choose either pub/sub or pub/sub lite.

https://cloud.google.com/pubsub/docs/choosing-pubsub-or-lite#comparison_table

The docs in a summary define several summaries around parameters:

Message Routing:

pub/sub — global message routing

pub/sub lite — zonal message routing

Resource Namespace:

pub/sub — global resources

pub/sub lite — zonal resources

Capacity Management:

pub/sub — Scale Automatically

pub/sub lite — Manual Provisioned

Delivery Modes:

pub/sub — Multiple messages delivery mode: Pull, Push (HTTPS POST), Streaming Pull (bidirectional RPC) and Pull over HTTP REST and gRPC.

pub/sub lite — Only support streaming gRPC pull.

Parallelism:

pub/sub — per-message parallelism

_pub/sub lite _ — partition-based parallelism

With those characteristics then we able to try to map which service meets our needs.

#gcp #pubsublite #nodejs #python