news.volyx.in

Show HN: Drop-in SQS replacement based on SQLite (github.com)

656 points by memset · 772 days ago · 156 comments on HN

Article summary

The article presents SmoothMQ, a drop-in replacement for Amazon Simple Queue Service (SQS) based on SQLite, offering a functional UI, observability, tracing, message scheduling, and rate-limiting. It can be used by any existing SQS client and deploys as a single Go binary. The project aims to provide a smoother developer experience and potentially offer a cheaper alternative to SQS without sacrificing performance. The developer is seeking feedback on the project's direction.

Main themes

  • SQS alternative
  • Message queue systems
  • Open source development
  • Monetization strategies
  • Licensing and AGPL
  • Distributed systems

What commenters say

  • The use of AGPL as the license for SmoothMQ may deter some users due to its restrictive nature, potentially limiting its adoption.
  • Some argue that not every open-source project needs to be monetized, and that projects created to scratch an itch tend to fare better than those built to make money.
  • Others believe that the AGPL license is the best choice for ensuring project continuity as open source, as it allows the project to benefit from improvements made by any forks.
  • There are differing opinions on the complexity of making SmoothMQ distributed, with some suggesting the use of existing libraries or protocols like Raft, while others think it may be better to roll out a custom solution.
  • Some commenters think that the project's focus on being a drop-in replacement for SQS may not be the most valuable contribution, given the existence of other message queue systems.
  • The choice of SQLite as the underlying database may limit the scalability and performance of SmoothMQ, potentially making it less suitable for large-scale applications.
  • The developer's decision to use AGPL may be seen as a way to attract collaborators who are willing to contribute to the project while ensuring that any modifications are made public.
  • Some argue that the project's potential for monetization is limited, given the saturated market for message queue systems and the availability of other open-source alternatives.