5 ms·

Cellular architecture? They've just rediscovered the art of redundancy systems

by madduci 3y ago

skullone 3y ago
But if they call it cellular architecture, it sounds much more exotic than a shared-nothing active/active service!
politelemon 3y ago
It's a common pattern in tech. Everything old will be new again.
- donutshop 3y ago
  But kubernetes
deleted 3y ago
[deleted]
- deleted 3y ago
  [deleted]
deleted 3y ago
[deleted]
gumballindie 3y ago
Oh hey they now have a new buzzword to sell!
Terretta 3y ago
Indeed, for 20+ years of distributed data centers (remember AZs are generally separate DCs near a city but on different grids, regions are geographically disparate cities) we called it "shared nothing" architecture pattern. Here's AWS's 2019 guide for financial services in AWS, where the isolated stack concept is referenced under parallel resiliency section and called "shared nothing": https://d1.awsstatic.com/Financial%20Services/Resilient%20Applications%20on%20AWS%20for%20Financial%20Services.pdf https://d1.awsstatic.com/Financial%20Services/Resilient%20Ap...
- hliyan 3y ago
  I wish modern architecture writing could go back to being this straightforward: "There are three dominent themes in building high transaction rate multiprocessor systems, namely shared memory (e.g. Synapse, IBM/AP configurations), shared disk (e.g. VAX/cluster, any multi-ported disk system), and shared nothing (e.g. Tandem, Tolerant). This paper argues that shared nothing is the pre- ferred approach." https://dsf.berkeley.edu/papers/hpts85-nothing.pdf https://dsf.berkeley.edu/papers/hpts85-nothing.pdf
benatkin 3y ago
To me it seems without the art. The costs will be passed on to the customers. I think there must be good ways to do redundancy without having all services running at full blast in each Availability Zone. It's a blunt tool, much like PHP. PHP does seem to be a good choice for them, but I wouldn't want to work there. It's all right, there are different ways to do stuff.

Cellular architecture? They've just rediscovered the art of redundancy systems

skullone 3y ago

But if they call it cellular architecture, it sounds much more exotic than a shared-nothing active/active service!

politelemon 3y ago

It's a common pattern in tech. Everything old will be new again.

donutshop 3y ago
But kubernetes

deleted 3y ago

[deleted]

deleted 3y ago
[deleted]

deleted 3y ago

[deleted]

gumballindie 3y ago

Oh hey they now have a new buzzword to sell!

Terretta 3y ago

Indeed, for 20+ years of distributed data centers (remember AZs are generally separate DCs near a city but on different grids, regions are geographically disparate cities) we called it "shared nothing" architecture pattern. Here's AWS's 2019 guide for financial services in AWS, where the isolated stack concept is referenced under parallel resiliency section and called "shared nothing": https://d1.awsstatic.com/Financial%20Services/Resilient%20Applications%20on%20AWS%20for%20Financial%20Services.pdf https://d1.awsstatic.com/Financial%20Services/Resilient%20Ap...

hliyan 3y ago
I wish modern architecture writing could go back to being this straightforward: "There are three dominent themes in building high transaction rate multiprocessor systems, namely shared memory (e.g. Synapse, IBM/AP configurations), shared disk (e.g. VAX/cluster, any multi-ported disk system), and shared nothing (e.g. Tandem, Tolerant). This paper argues that shared nothing is the pre- ferred approach." https://dsf.berkeley.edu/papers/hpts85-nothing.pdf https://dsf.berkeley.edu/papers/hpts85-nothing.pdf

benatkin 3y ago

To me it seems without the art. The costs will be passed on to the customers. I think there must be good ways to do redundancy without having all services running at full blast in each Availability Zone. It's a blunt tool, much like PHP. PHP does seem to be a good choice for them, but I wouldn't want to work there. It's all right, there are different ways to do stuff.