korrents

SQLite

An embedded SQL database engine that runs inside the application rather than as a separate server.

sqlite.org ↗

FilterEveryone, all time6 from 5 people
Group All Technologists 1Scientists 1
Who Everyone PSPeter Steinberger 2 DCDavid Crawshaw 1 JEJulia Evans 1 KDKent C. Dodds 1 TLTobias Lütke 1
When All time Past 1 yearPast 3 yearsPast 5 years
  1. PS

    Peter Steinberger quoted

    Founded PSPDFKit in 2011 and ran it for a decade

    Our readingbtrfs copy-on-write feature is great for worktrees but bad for sqlite

    Their wordsTurns out, brtfs cow-feature is GREAT for worktrees and terrible for sqlite

    ↗@steipete on Xx.com

  2. 5 days earlier
  3. PS

    Peter Steinberger quoted

    Our readingUsing synchronous database access when moving OC to SQLite became limiting once one agent might run 50 parallel sessions used by a whole team.

    design

    Their wordsThe biggest design mistake I made when we moved OC to sqlite: using sync db access. When it was just an agent that reports to you on Slack or iMessage this was fine; now that one agent might do 50 sessions in parallel and the whole team works on it, it is limiting.

    ↗@steipete on Xx.com

  4. 5 days earlier
  5. TL

    Tobias Lütke quoted

    Co-founder and CEO of Shopify

    Our readingSomeone may soon build (or already has built) an embeddable, sqlite-style execution environment that parses bash, TypeScript, or tool calls into a security-checkable IL plan.

    TypeScriptdesign

    Their wordsMy bet? Sometime soon someone will (or has already?) create a embeddable, sqlite style mini execution environment that parses bash, typescript, or tool calls into a common IL execution plan that's easy to security check before executing. And design this specifically for durable execution environments.

    ↗@tobi on Xx.com

  6. 2 months earlier
  7. JE

    Julia Evans quoted

    Writes jvns.ca, a blog explaining networking

    Our readingSQLite is a fine production database for a small site, but running it well is more complicated than the "SQLite in production is totally fine" blog posts make it sound.

    Their wordsI read a bunch of blog posts about how it is totally fine to use SQLite in production for a small site and I think it is totally fine, but what I did not fully appreciate is that SQLite is still a database, databases are complicated, and I do not know a lot about operating databases.

    ↗Learning a few things about running SQLitejvns.ca

  8. 4 months earlier
  9. KD

    Kent C. Dodds quoted

    Software engineer and educator

    Our readingDerived data such as a search index should be kept up to date as background work, never inside a foreground user request.

    Their wordsRequest-path ownership matters. Don't let derived-index maintenance happen inside a foreground user request. Whether you use SQLite, a managed service, or something else, keeping a search index fresh is background work and should stay off the user-facing path.

    ↗Implementing Hybrid Semantic + Lexical Searchkentcdodds.com 1st of 2 in this piece

  10. 2 years earlier
  11. DC

    David Crawshaw quoted

    Software engineer; co-founder and former CTO of Tailscale

    Our readingThe right moment to migrate from an ad hoc data store to SQL is the moment you first need an index.

    Their wordsI suspect, considering the process retrospect, a great deal of that pain can be avoided by committing to migrating directly to an SQL system the moment you need an index.

    ↗jsonfile: a quick hack for tinkeringcrawshaw.io 1st of 3 in this piece