TreeQ - Message Queue
Message Queue systems is very popular in multiserver based environments, mostly when your application is written with Microservices principle.
The main idea is to put data/message
Inside Queue Storage and read that data from other services, and when your service is done with it, just delete data from storage automatically.
It seems simple right?
But it is surprisingly complex when you are getting in to use Queue softwares like
Kafka, they have good performance and functionality, but in most cases you don't need that match of functionality, you need just a place to keep and delete queue data nothing more than that.
That's why we decided to build super simple
REST API based Queue service with super scalable backend using TreeScale technology.
Our focus is simplicity and for authentication we also keeping it.
Before making any API request/call you need to have
API Token generated from our admin panel at API Tokens.
You will get token with
40 character length, and using that token now you can make an API requests by passing that token in
Authorization HTTP Header.
~# curl -X POST -H 'Authorization: 1273cc79fd23d717fd7777f92c1ec6e7d63279fb' https://dash.treescale.com/q/[api name]
Using this token we will authenticate you and will do requested action if they applicable for that token.
You can also generate new token, and share it with other people so that they also can access to your Queue Storages. When you want to close their access, just delete their tokens. This is mostly useful when you are running on multi-application environment and want to have full control for each application.
Storage Tips and Limits
As of now we are not limiting Queue message count or API calls count. But we are limiting single message size up to
50MB, which is actually quite large compared to other Queue services. If you need more large messages just let us know and we can discuss possibilities.
In free version of Queue service we are using
Shared Storage Systsem, so that your data will stay isolated from others, but physically it would be on same machines pool. But for specific usecases we have also possibility for attaching your private storage or moving our system to your private infrastructure.