Update: Just got home and it turns out my little power metering adapter between the rack and the wall is what died. This sucks but is good because I can just plug in directly and bypass it and don't need to replace anything. I'm catching up on the firehose but will miss a week of data sorry.

Congrats, Cameron!!!!

my new record is out on lauren records. it’s called grimdark. i’m really proud of it. the album art was made by sebastian kim bateman. jack shirley mixed & mastered it. cleo mckenzie directed it. lauren records put it out. neat stuff ^_^

Congrats to you and the team, Bryan!!! 💜💜

Sign in with Google is probably outside of what I want to offer at the moment.

Upgrade should be smooth but you may lose a registered TOTP from a one-time migration, you should be able to sort it out in the operator dash if something goes wrong. Rolling back isn't safe at this point if you do go with the upgrade, there were some backward-incompatible user metadata changes.

What commit are you on now in your deployed version? i would potentially be open to issues but things are definitely still in flux as you can see in the repo. i would update to latest first and see if i’ve already addressed them. I can test an upgrade from your version if you want just in case

I truly believe that Object Storage is the only real datastore and everything else should be cache and compute on top of it. Databases are fake, Object Storage is the last database. All your systems should be built on top of it and use NVME and RAM as caches and local compute.

If you need low latency, simply support shard replicas and accept writes as durable when a quorum of replicas have written the write into memory and let them slowly flush to object storage in efficient batches that amortize operation costs. That's durable enough for pretty much anything.

Of course for ^ to be durable you want your replicas to be on different physical nodes and maybe different racks but yeah. Horizontally scalable DBs use RAM as a cache and NVME as durable storage with writes durable at R=2 nodes reporting in-memory writes. Now we have RAM -> NVME -> Object Storage.

This is nice because it allows single node operation and also allows recovery and seamless handoff by pulling from object storage instead of having to do heavy node-to-node reads to catch up or onboard a new node. Your durability is also a lot higher and you can run your local NVME hot.

This is nice because it allows single node operation and also allows recovery and seamless handoff by pulling from object storage instead of having to do heavy node-to-node reads to catch up or onboard a new node. Your durability is also a lot higher and you can run your local NVME hot.

Of course for ^ to be durable you want your replicas to be on different physical nodes and maybe different racks but yeah. Horizontally scalable DBs use RAM as a cache and NVME as durable storage with writes durable at R=2 nodes reporting in-memory writes. Now we have RAM -> NVME -> Object Storage.

If you need low latency, simply support shard replicas and accept writes as durable when a quorum of replicas have written the write into memory and let them slowly flush to object storage in efficient batches that amortize operation costs. That's durable enough for pretty much anything.

I truly believe that Object Storage is the only real datastore and everything else should be cache and compute on top of it. Databases are fake, Object Storage is the last database. All your systems should be built on top of it and use NVME and RAM as caches and local compute.

Yes it's on the list!

💜

it is horizontally scalable, but each node increases the baseline load on object store operations so cost-wise it generally scales better vertically.

There are numerous elevators