3 ms·

> Databases that are built into the application by default are the future. That’s a bit overzealous. SQLite is great, but it’s not a replacement for a hosted d

> Databases that are built into the application by default are the future. That’s a bit overzealous. SQLite is great, but it’s not a replacement for a hosted database. Not all data can live on the client. Use SQLite when you have the right use case for it (offline desktop app, etc.)

gwbas1c 2y ago
There are ways to use a hosted SQL, or from a cloud application. I personally haven't used it. What I am curious about is if "Many Small Queries Are Efficient in SQLite" when using the various hosted flavors of SQLite.
- claytongulick 2y ago
  Nope. You get back to the roundtrip problem.
  - infamia 2y ago
    The SQLite db can easily live on the same machine as the app server.
    - deleted 2y ago
      [deleted]
    - danielheath 2y ago
      > using the various hosted flavors of SQLite
      - closeparen 2y ago
        I think the "hosted flavors of SQLite" would be doing the type of trick Litestream does: streaming the WAL to other copies of the database. The copy you interact with is still local.
bob1029 2y ago
> Not all data can live on the client When you say "client" are you referring to the end user's machine, or the server hosting the application they are talking to?
- corytheboyd 2y ago
  End user machine.
  - bob1029 2y ago
    Ok yeah - I wouldn't recommend storing any state on the user's machine unless it's absolutely required. I only advocate for using SQLite on the server, integrated with the hosting application (i.e. your back-end systems).
- taneq 2y ago
  It’s clients all the way down. ;)
matthewaveryusa 2y ago
If you have a database server and an application server, then move your application on the same machine as your database. That's basically the use case of sqlite server-side. You can easily fit 250TB on rack (or 64tb on an ec2.) That's a lot for non-blob storage: 750KB per us citizen
- closeparen 2y ago
  Who has "an" application server though? Those of us who came up through PHP/Rails/Flask and even much of the modern microservices world were taught to do stateless, probably load-balanced application tiers with shared DB, maybe cache, maybe message queue. Both for scalability and redundancy. Redundant SQLite is not impossible [0] but it is definitely less mature and well-known than replicated MySQL or Postgres. [0] https://litestream.io/ https://litestream.io/

gwbas1c 2y ago

There are ways to use a hosted SQL, or from a cloud application. I personally haven't used it. What I am curious about is if "Many Small Queries Are Efficient in SQLite" when using the various hosted flavors of SQLite.

claytongulick 2y ago
Nope. You get back to the roundtrip problem.
- infamia 2y ago
  The SQLite db can easily live on the same machine as the app server.
  - deleted 2y ago
    [deleted]
  - danielheath 2y ago
    > using the various hosted flavors of SQLite
    - closeparen 2y ago
      I think the "hosted flavors of SQLite" would be doing the type of trick Litestream does: streaming the WAL to other copies of the database. The copy you interact with is still local.

bob1029 2y ago

> Not all data can live on the client When you say "client" are you referring to the end user's machine, or the server hosting the application they are talking to?

corytheboyd 2y ago
End user machine.
- bob1029 2y ago
  Ok yeah - I wouldn't recommend storing any state on the user's machine unless it's absolutely required. I only advocate for using SQLite on the server, integrated with the hosting application (i.e. your back-end systems).
taneq 2y ago
It’s clients all the way down. ;)

matthewaveryusa 2y ago

If you have a database server and an application server, then move your application on the same machine as your database. That's basically the use case of sqlite server-side. You can easily fit 250TB on rack (or 64tb on an ec2.) That's a lot for non-blob storage: 750KB per us citizen

closeparen 2y ago
Who has "an" application server though? Those of us who came up through PHP/Rails/Flask and even much of the modern microservices world were taught to do stateless, probably load-balanced application tiers with shared DB, maybe cache, maybe message queue. Both for scalability and redundancy. Redundant SQLite is not impossible [0] but it is definitely less mature and well-known than replicated MySQL or Postgres. [0] https://litestream.io/ https://litestream.io/