Flexible messaging model
Message queues and Publish/Subscribe both are well-established, complementary communication pattern, used in serverless and microservices architectures.
TurtleQueue can be used as a publish-subscribe system or a message queue. It can also be used on both the back-end and front-end.
This means you do not have to choose between the two models.
Hit the ground running
Tap into a ready-made infrastructure layer. No need to deploy your own messaging infrastructure, which can be tedious. Things that have to be done when running your own messaging layer includes:
- app servers
- load balancers
- health, monitoring and alerting
- authentication, handling secrets
- Continuous integration, continuous delivery
- backup and restore
- protect yourself against spam, phishing, cross-site scripting, and denial of service attacks, all while keeping up with the security updates
Notice there is nothing in the list about "crafting something for your users" just yet. TurtleQueue lets you skip this and focus on product-building. In short, we think message queues are great, and Apache Pulsar, on top if which TurtleQueue is built, one of the best yet. TurtleQueue lets you use Apache Pulsar while simplifying it's deployment and use.
Common use case
- messaging layer for a lambda architecture, thanks to it's simple HTTP interface (not included in standard pulsar)
- event and log storage for even-driven architectures/microservices