4 ms·
Another commenter mentioned automatic sharding to which you replied "no". But short of that what do you think about use cases where the database is "naturally"
by infogulch 5y ago
Another commenter mentioned automatic sharding to which you replied "no". But short of that what do you think about use cases where the database is "naturally" very sharded, say where every user has a separate database? With such a design the operator might want to scale rqlite down to zero instances when a db is unused for a while and start it back up quickly on demand.
Have you thought about how rqlite could fit into this design space?
- zeckalpha 5y agoThat seems better solved outside of rqlite in the application layer and inetd or k8s.
- deleted 5y ago[deleted]
- otoolep 5y agoI have considered it, but it would introduce a very large amount of complexity -- and make rqlite much more complicated to operate. Adding this type of functionality would push mean rqlite would no longer be a worthwhile system to use. It would do something (sharding) probably no better than other systems, but no longer be trivial to operate. rqlite does something somewhat narrow, but does that very well (though I would say that :-) )
- stavros 5y agoI have to say, I like your product thinking. I agree with you.