nodejs-pubsub VS deepstream.io

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.

Deepstream is an open-source library for real-time web application development. The library, which is built with Node.js and Engine.io, helps developers build frontend web applications that perform real-time updates while requiring minimal backend code.

I'm working on a few projects, from one/two days to platforms.

The first is OS and is a simple nodeJS environment to deploy applications via lambda and express quickly. Sort of like nestJS except less decorators and more functional (https://vramework.io/). I already know of a few other colleagues that rolled their own propriety versions of this to support enterprise and cloud deployments so decided to OS it.

The other OS project is a strongly typed postgres/mysql driver. The idea is to generate typescript definitions directly from postgres (https://github.com/vramework/schemats) and then have a think layer ontop of pg-node that gives you strongly typed queries (https://github.com/vramework/postgres-typed).

An open-source project I spent a few years on the core team is https://deepstream.io/, a realtime-server that allows you to mix and match multiple streaming protocols (mqtt/websocket/others) and allow those clients to talk to each other using pub-sub and records. I'm not longer working for it but wanted to give it a shout out!

On a non OS project, I have been working on an immersive audio platform for a while now. The main goal is to allow users to pick and choose how audio books progress, and also have a live session mode which allows users to record their pulse / answer questions and a few other metrics and associate it with sentences. I pretty much built and deployed all of it but require some advice/brainstorming on how to proceed now. I built it to satisfy an itch when I was practicing shamanism during the first lockdown when I was in-between contracts / taking time off.

I also want to build a simple web-pages strategy game based around eco-education, but don't have the bandwidth . If anyone is interested in mixing together gamification and eco-village building might be a fun conversion to bounce ideas!

All the OS projects above were used to support my personal/a couple professional projects over the last few years.

Email in profile

I'm currently looking for a contract that is part-time that is focused on consultancy or smaller projects (such as setting up containerized AWS environments)

I am looking for part-time contract or freelance/consulting opportunities at the moment (up to 20 hours/week).

GitHub: https://github.com/yasserf

OS projects I am/was core maintainer of: https://vramework.io/ and https://deepstream.io/

LinkedIn: https://uk.linkedin.com/in/yasserfadl

Email: [email protected]

https://deepstream.io is the closest and has a richer feature set (including a replicating document store), however it seems to have a small ecosystem / community / limited support options, and permissions do not seem as advanced.

https://nats.io is close but lower level. Has a large community and rich ecosystem however.

Then you can also mix and match lowever level technologies to achieve the particular set of tradeoffs you need. MQTT, AMQP as the protocol, mosquitto / rabbitmq/zeromq, then json-rpc on top ...

I can find socket.io, faye, deepstream.io , autobahn-js and nchan, centrifugo. Can you also explain why you chose it and if you had troubles with some other solution?