Jerome Gravel-Niquet @[email protected]

Co-founder at @flydotio (he/him)

[martin_casado @martin_casado]

Finally. A developer focused S3 alternative (built on @flydotio). I've been waiting for something like this for ages. (wohoo!!)

https://t.co/FGzvVo3Apz

[Matt @tantaman]

Working on a post but I present a React table of 2 million rows, dynamically filtered in real time.

tldr: the data structure backing the table is maintained via differential dataflow so we only need to process the single row that changed rather than the entire set when filtering

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@chris_mccord @mrkurt @simonw Since the release, I've made yet-to-be-released changes to the subscriptions API and improved the docs greatly if any of you want to take another look! https://t.co/Z32iQAyMXJ

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@louispilfold @bcjordan @mrkurt *single source of truth per unique primary keys constraint

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@louispilfold @bcjordan @mrkurt It could be changed to use the node ID as the tie breaker, but that would mean a specific node might win all conflicts.

To avoid these situations, it's best to have a single source of truth or data that changes slower than the cluster can synchronize.

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@mrkurt @simonw @chris_mccord It's also what the templating feature uses to update produced files.

More docs to come!

The first integer per row / change is an internal rowid for the query result row. It's meant for updating state based on that number (e.g. for reactivity) without a making a new query.

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@bcjordan @mrkurt We already are :) you can put any kind of data that fits in SQLite.

[kurtle 🐢 @mrkurt]

We open sourced Corrosion, the tool we built to replace Consul. It started as gossip based service discovery.

If you want to win buzzword bingo: Corrosion is built with Rust, CRDTs, and sqlite.

https://t.co/pOzuwoTLVR

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@dovunderscore @tantaman @ccorcos Those numbers were for "v1" of what's current in production at Fly. cr-sqlite will be used for v2 which we intend on releasing open source in the coming months. It should be able to handle the same workload no problem!

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@dilrajio @strzibnyj @flydotio We do yes. You can disable it when you deploy iirc. I think they’re called auto start and auto stop or something like that. If you fly deploy -h it should list them. I assume this is a new v2 app and not a v1 migrated to v2 (which should have that turned off by default)

[Jerome Gravel-Niquet @[email protected] @jeromegn]

New router settings are too advanced for me

[Fly.io @flydotio]

https://t.co/pIqdNVDEnU

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@fasterthanlime I need to read that whole series. I have NixOS going but barely understand what I’m doing.

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@MichaelSharer @jacobmparis @kentcdodds Are you starting your app with `npm start`? If so, using `node` directly might work better. `npm start` itself uses ~50MB for the lifetime of the app.

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@benbjohnson I’ve watched one like that before and I loved it! I don’t remember who the streamer was 🤔

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@benbjohnson This got me wondering about what go does differently here. Cgo uses different threads to avoid blocking the runtime which is pretty much what we have to do too. There’s probably a more ergonomic way to do it, in our project, that doesn’t require manually sending a closure.

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@joshmo_dev Such secure! We do tell you to note it down somewhere iirc.

[Ben Johnson @benbjohnson]

Great detailed post from @benhoytnz on getting Go + SQLite running on https://t.co/28xo6QZlM8. Even includes load testing on our tiny 256MB VMs! 500+ req/sec is pretty good! 👌 https://t.co/89yTdWxDOE

[Jerome Gravel-Niquet @[email protected] @jeromegn]

@marbiano3 @flydotio What are you seeing? The current status page incident is considered resolved (we are monitoring) since yesterday.