4 ms·
Use case #1: You have a problem table (e.g. a high-volume events table) that grows non-linearly as your business starts to scale up. A queue + columnar store pa
by dfltr 2y ago
Use case #1: You have a problem table (e.g. a high-volume events table) that grows non-linearly as your business starts to scale up. A queue + columnar store package like Trench moves the problem table out to a system better equipped to deal with it and lets your DB server handle its relational business in relative peace and quiet.
- Attummm 2y agoMaybe I wasn't clear enough but my questions have been rhetorical. They were not for me. If one starts stating technologies, it is akin to describing the individual ingredients of a sandwich. The question remains: Why choose Trench over just using Kafka and Clickhouse or any other message queue and columnar database / big data base? If the goal of the post and the landing website is to entice people to use the tool, then answering these questions is important. If what is being discussed seems obvious, then who is the target demographic? Because they already know the space, use alternatives or have built their own.
- teleforce 2y agoProbably it's just me, but your comment is very similar to the famous one on Dropbox: My YC app: Dropbox - Throw away your USB drive https://news.ycombinator.com/item?id=9224 https://news.ycombinator.com/item?id=9224
- Attummm 2y agoThese two comments are worlds apart. My comment is feedback to better pitch the project with the goal of attracting more users. The Dropbox comment, in contrast, is a mean-spirited criticism that just lists alternatives.