inb4 vibe ops, where companies give the ai access to aws and tell it to run the thing. overtime it will move beyond simple apps, learning how to operate distributed systems at scale.

deploy the images, create the queues, topics, databases, scale and self-heal based on metrics. will be dramatically more efficient and cheaper than human ops, particularly when it comes to over provisioning.

Reply to this note

Please Login to reply.

Discussion

nostr, specifically web of trust, will be very important for maintaining human connections during this onrush of ai manipulation

“error rate is too high scale everything back to 1 server”

*more errors*

this is fine

I'm here to see the cover ups of the meltdowns of corporate servers as they apply AI ops and then blame it on hacks and ddos.

Wait that already happens with regular ops.

the early days will be messy. long term I think it’s viable. self healing cattle is already the norm. why bother humans with alarms and graphs, only to bumble their way through a runbook?

you have not seen FoundationDB

not in practice, but I am aware of it. why?

it is extremely hard to break and just works

automatic self-healing and management

it will tell you where the bottleneck is so you can automatically scale it up

setting it up involves copying a single fdb.cluster file and starting it

but is it web scale?

/s

if by web scale you mean Apple CloudKit and Snowflake scale, yes, actually

it in fact does not write your data to /dev/null

it is a KV store, which means you can build a lot, but also means you need to build your own architecture

perfect for nostr use cases

it struggles a bit with large values, but you can easily fix that by using SeaweedFS (some-maintenance-required FS that allows storing a lot of small files like 100KB)

And then you have a single AI biased in a particular way. No fragility spotted anywhere.

AWSBot says just enable ElasticAiResponder, for the cool cost of $0.16/req to ensure five 9’s of reliability