I love sqlite backed system, one less component to worry about. But when using Tansu with sqlite storage, what are my options for horizonal scaling and keeping Tansu HA?
Also, are there any benchmark on how Tansu with S3 storage would perform in comparison to Kafka or something like WarpStream?
You could use the proxy to spread topics over a number of brokers. The broker and proxy share a number of services and layers, that could be used to route:
My itch for SQLite was smaller scale (and reproducible) environments, e.g., development, test/integration (with a single file to reset the environment). PostgreSQL was intended for "larger scale", with (database level) partitioning of Kafka records on each topic/partition, and replication for leader/follower setups, which might work better for HA. S3 for environments where latency is less of any issue (though with the SlateDB/S3 engine that might change).
S3: Not yet. I've been working through tuning each engine, S3 is next on the list.
Spring Boot allows you write application configuration in `application.properties` file and pull any variables used from environment. This replicates the same in Go, except it uses a yaml format and you can leave the value empty which you expect to be present in env.
Thanks for feedback. I'll update it to make it more clear.
When I was reading on these terms, a single line description did not help much. A simple dictionary would've been kind of similar. Any specific suggestion, you would like to make?
This is great, I wanted to able to edit hastebin/pastebin without login and it solves this exact problem. Since the link is not that easily guessable, content integrity should not be a problem.
Thanks. If you really want to keep things to yourself you can log into a domain - anything you do in a domain is not public, by default (though you can toggle this).
Also, are there any benchmark on how Tansu with S3 storage would perform in comparison to Kafka or something like WarpStream?
reply