Is This a Good Way to Reduce Operational Costs?

I'm implementing a publisher-subscriber mechanism for a feature in our product, LiveAPI.

LiveAPI is an auto API documentation tool that generates API docs simply by connecting to a repository.

To enhance security and build trust, we've designed it so that interactions and operations with the repository happen directly on the client’s machine—for instance, their own AWS EC2 instance.

For communication between the client’s machine and the LiveAPI backend, we’ve been evaluating a few approaches:

AWS SNS: While this works, it requires additional setup from the customer's side, like opening ports on their machine to enable HTTP endpoint connections, which adds complexity.

SNS + SQS: This reduces some of the complexity but comes with higher infrastructure costs and a more complicated setup process.

Redis Pub/Sub: This seems to be a promising option for our use case. It offers low latency, minimal maintenance, and is relatively simple to implement.

We’re currently diving deeper into Redis Pub/Sub to ensure it meets all our requirements. If you’re curious, here’s a Redis Pub/Sub documentation link for reference.

I’ll share more insights and updates on this as we progress. Stay tuned!