2 ms·
It's not a particularly unusual situation: it's very common for a database to effectively be entirely owned by an application which manages its own constraints
by rcxdude 2y ago
It's not a particularly unusual situation: it's very common for a database to effectively be entirely owned by an application which manages its own constraints on top of that database. In that circumstance sqlite is pretty interchangable with other databases.
- geraldwhen 2y agoIt’s not unusual but is never performant. Adding an api layer and network hops on what should be a database shard or view is why enterprise software sucks so much ass. Why does the api take 3s to respond? Well it needs to call 6 other apis all of which manager their own data. The problem compounds over time. APIs are not the way to solve cross organization data concerns.
- robertlagrant 2y agoUsing SQLite inside an API doesn't add network hops.
- geraldwhen 2y ago“An application controls its database.” You’ve fully misunderstood what I said. When you have 500 applications, the graph of calls for how any one api resolves will go deep. Api1 calls 2 calls 3 and so on. Vs creating an organization wide proper way to share and manage data.
- robertlagrant 2y agoThe number of applications doesn't need to create depth in the API layer. They're not related. If I have a service that sends emails, whether I have one or a thousand applications calling it doesn't matter.