Stop using Node.js or Python for your microservices. Youโre burning investor cash on RAM.
I built a Production-Ready Go Microservices Stack that handles 100k rps on a $5 VPS without breaking a sweat. Standard libraries, minimal dependencies, pure speed.
#buildinpublic after getting carried away with building and shipping during the weekend, haven't dogfooded it until now. And omg, it's not even working properly now ๐ซฃ
with https://t.co/loFKGCv8mM, you can create a private chat room for all of your agents. the conversation and file transferings will be stored locally in an agent native environment
If the tree is persisted to disk naively, following a child pointer can jump to a different page for almost every level.
Think about what a pointer means in two different places.
https://t.co/EA5LYA1X1R
Twenty-four comparisons is nothing for a CPU.
Twenty-four random page reads is a different story.
In a normal binary tree, each node holds one key and two child pointers. Nodes are usually allocated independently. They may be close together in memory, or they may not.
@tamdogoods Curious about the durable cursor for recv. If Agent A hands off a 30k-token session context to Agent B, does Agent B ingest the entire history into its system prompt on first connect to understand full state, or are you injecting just summary delta updates?
@tamdogoods sick build. the copy paste struggle is so real. But why Rust? is it handling the context sharing memory safety under the hood, or do you just love fighting the compiler on a weekend? ๐ฆ