2 ms·
It may not be computationally challenging. But if you are integrating with dozens of legacy systems then getting that right is hardly trivial. Look at Netflix a
by threeseed 12y ago
It may not be computationally challenging. But if you are integrating with dozens of legacy systems then getting that right is hardly trivial. Look at Netflix and Twitter and the work they did around resilience between their micro services.
Getting that to work every time with all failure paths handled correctly is definitely architecturally challenging.
- wyager 12y ago>Getting that to work every time with all failure paths handled correctly is definitely architecturally challenging. You're right. Good thing they completely failed to handle all failure paths correctly. This is extensively documented at http://en.wikipedia.org/wiki/HealthCare.gov#Launch_and_technical_problems http://en.wikipedia.org/wiki/HealthCare.gov#Launch_and_techn...
- threeseed 12y agoI'm not saying that they did a perfect job of it. We all know they didn't. I am just disputing anyone who thinks projects like this aren't technically challenging.