|
|
|
|
|
by phtrivier
1387 days ago
|
|
"But what if _the_ machine goes down ? What if it goes down _during quarter earnings legally requested reporting consolidation period_ ? We need _redundancy_ !!" Also, philosophically, I guess, a "distributed" systems starts at "two machines". (And you actually get most of the "fun" of distributed systems with "two processes on the same machine".) We're taught how to deal with "N=1" in school, and "N=all fans of Taylor Swift in the same seconds" in FAANGS. Yet I suspect most people will be working on "N=12, 5 hours a day during office hours, except twice a year." And I'm not sure what's the reference techniques for that. |
|
People opening a page in a browser that sends requests to a server is already a distributed system.
A monolith sending requests to a database instance is already a distributed system.
Having a metrics sidecar running along your monolith is already a distributed system.