Endless, we offer SemQL to query in high-dim space using distance, direction and contrast predicates. It enables anyone to retrieve events that align with a predicate in global vector space.
The fundamental assumptions of distributed systems is having multiple machines that fail independently, communicate over unreliable networks and have no shared clock has the consequence of needing to solve consensus, byzantine faults, ordering, consistency vs. availability and exactly-once delivery.
However, AI agents don't share these problems in the classical sense. Building agents is about context attention, relevance, and information density inside a single ordered buffer. The distributed part is creating an orchestrator that manages these things. At noetive.io we currently work on the context relevance part with our contextual broker Semantik.
Lesson learned: If your recovery plan requires calling any API in the dead region — to detach an IP, describe a route table, launch an instance, read an S3 object, or decrypt a volume — it will fail when you need it most.
Every dependency on the primary region is a dependency on the thing that just broke.
This is great! But what if the US invests 1% of GDP in GPU datacenters and then those are not needed becaues someone created a much more efficient architecture?
I share the view that nobody avoids an exit or migration because of egress fees. In fact, for online migrations the period of replicating data between providers might go on for months.
But all cloud providers leverage The Principle of data locality or data gravity, which states that compute benefits from being close to the stored data. If a customer moves the data elsewhere it follows that the compute will soon leave too.
The elephant in the room: Will Spotify survive the coming wave of generative AI audio content? Wasn't any mentioning on that in the letter.
Seems to me like they would need to ditch a lot of silly investments like original content, platform engineering on Kubernetes and scaled agile which together carry costs in the range of $100s millions, to free up resources to battle new disruptive technologies.
Correct. It's also the case that human generated requests will lose their relevance within seconds, a quick retry is all it's worth. As for machine generated requests a dead letter queue would make more sense, poor engineered backend services would OOM and well-engineered would load shed, if the requests are queued on the application servers they are doomed to be lost anyway.