Building a highly-available web service without a database
Posted by self@reddit | programming | View on Reddit | 5 comments
Posted by self@reddit | programming | View on Reddit | 5 comments
egodeathtrip@reddit
Fyi, highly available - means to return some response, which can be stale or plain wrong is fine. So, as long as some machine is running & can response to your requests, it's considered highly available.
AvoidSpirit@reddit
This is “availability from CAP”, not “high availability”
yourfriendlyreminder@reddit
This honestly sounds like the opposite of simple.
GergelyKiss@reddit
Maybe a better word is "flat", as in this architecture really doesn't have any kind of infra or stack (besides the SDK of the programming language of choice, CPU, RAM and an SSD).
So I agree, this leads to another kind of complexity eventually, where there's no clear separation of duties. Will be fun to explain all this hot code reloading magic on an audit...
But I do get the appeal and performance wins of a flat structure like this. Interesting experiment!
Miserable_Ad7246@reddit
Good old CAP theorem.