3 ms·
If a customer has 1000 employees all using your app, it is.
by rguillebert 5y ago
If a customer has 1000 employees all using your app, it is.
- chasil 5y agoIf the app is designed correctly, then the thousand employees would write to their own temporary databases, and a background job would pull their changes into the main database sequentially. If the app is not specifically designed to do this, then SQLite would not be an option.
- pc86 5y agoSerious question, is this just a "how do I get SQLite to work in this scenario?" thing, or is there actually some other benefit to having this sort of data architecture?
- chasil 5y agoThis can actually relate to SMTP servers using mbox or maildir formats. Maildir is more resistant to corruption, and doesn't rely (as much) on file locks. https://serverfault.com/questions/564456/what-are-the-practical-differences-between-maildir-and-mbox https://serverfault.com/questions/564456/what-are-the-practi...
- rguillebert 5y agoWhat's the benefit over just using the main database?
- zbentley 5y agoNot always. In fact, I'd strengthen that and say that this is not a problem in general/in most cases with thousands of concurrent users. See my other comment one level up.