mitt VS nodejs-pubsub

Mitt is a small (200 bytes) library that provides the same functionality. It doesn't have many updates, because it's simply perfect and there are not many things to improve there. It gets the job done. Don't be frightened, if in 2 years npm will say it's 2 years old. This library is just perfect with no bloatware. In the worst case, just copy-paste its code to your app.

The implementation can vary widely depending on the requirements. For our application, we will take a small library that will do almost everything for us:

You can use an event bus for this, looks like they removed this functionally from vue 3 so you'll need a 3rd party package like mitt

then we need to install an external library implementing the event emitter interface, in this case mitt

date-fns and mitt (event emitter) are also frequent helpers, but I'm considering dayjs and nanoevents for these cases.

Not sure I understood the post right, bit you may want to check Mitt. It's popular event emitter package that quite nicely deals with this very issue.

As suggested in official docs you could use mitt library to dispatch events across components.

You can use it mitt library. https://github.com/developit/mitt

For situations like this, I use simple event emitter / pubsub library called mitt. It's small and lightweight, however there are many similar libraries that would work.

In this article I want to show you how I have implemented this pattern in my Nuxt 3 applications using Mitt which already provides full TypeScript support. To fully understand what's happening under the hood I recommend to have a quick read of Mitt documentation before continue reading.

Secondly, Go is incredibly easy to learn and in my opinion, maintain. This means that if you're a growing company and expect to onboard new teams and team members, having Go as a basis for your systems should mean that new engineers can get up to speed quickly.  Below is a small sample application that can connect to Google PubSub, subscribe to a topic, send an event and then clean up. In total, its 82 lines of code including liberal line breaks. Even if you have never written or read a line of Go before, I hope you'll agree that it's quite clear and readable:

Pub/Sub

Google Cloud Pub/Sub is a fully-managed, globally scalable and secure queue provided by Google Cloud for asynchronous processing messages. Cloud Pub/Sub has many of the same advantages and disadvantages as SQS due to also being cloud hosted. It has a free and paid tier.

Cloud Pub/Sub: A global messaging service for event-driven architectures

Google Cloud Pub/Sub (*https://cloud.google.com/pubsub*)

Google Cloud Functions is a FaaS offering from Google Cloud Platform (GCP). It allows developers to run their code in response to events, such as changes in a database or the arrival of a message in a Pub/Sub topic. Like AWS Lambda, Google Cloud Functions can be used to build a variety of applications, including serverless websites, data processing pipelines, and real-time data streams.

that gets triggered when a Pub/Sub topic is fired (from the webhook function)

Maybe Pub/Sub from GCP?

I'm curious - given your limited knowledge, is there a reason you're looking to self host this in your own cluster rather than using a managed service like https://cloud.google.com/find-a-partner/partner/confluent-inc?redirect= or just native Google PubSub https://cloud.google.com/pubsub/ ?

Pub/Sub, the GCP managed service for message queuing, has two levels of services on standard and one Lite. Standard is the high availability version of it and Lite could be a zonal or regional service with infrastructure managed by the client. Obviously, the model pricing will be very different with a x10 between Standard and zonal Lite. However, the model pricing is the same is based on throughput for message publishing, message storage costs and egress for message distribution. Here, we totally break the similarity with a VM model (except on storage). Everything is drived on volumetry and performance of inbound and outbound messages.