3 ms·
This is interesting, however I'd say most of the software on this list not relevant for 99% of software architects / engineers ( ie all of us working on web / s
by sytringy05 7y ago
This is interesting, however I'd say most of the software on this list not relevant for 99% of software architects / engineers ( ie all of us working on web / server side applications for BigCorp).
It's not the fault of the authors of course, in my experience there's not many organisations interested in explaining stuff like this out in the open.
It would be great to see the architecture of:
- a large scale distributed system
- a typical web app with UI, web tier, data tier maybe thrown in some eventing for good measure.
- maybe anything else that needs to talk across a network all the time.
Nick Craver from Stackoverflow does a great job of explaining this for how SO do it, any other good examples would be great.
- rahimnathwani 7y agoIn case anyone else is curious: https://nickcraver.com/blog/2016/02/03/stack-overflow-a-technical-deconstruction/ https://nickcraver.com/blog/2016/02/03/stack-overflow-a-tech...
- kostarelo 7y agoI have found StackShare to be excellent to get a birds' eye view of the stack of all the big companies. They also write on their blog in more details usually in coordination with the companies. https://stackshare.io/ https://stackshare.io/ https://stackshare.io/uber-technologies/uber https://stackshare.io/uber-technologies/uber https://stackshare.io/stack-history-timeline-unicorns-ipos-of-2019-tech-stack-evolution https://stackshare.io/stack-history-timeline-unicorns-ipos-o... https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month https://stackshare.io/circleci/how-circleci-processes-4-5-mi...
- therealdrag0 7y agoI would particularly like examples of Archs that are not 1000 reads per 1 write. A lot of business software is interaction heavy. So designing to support loads that can't be waved away with caching would be good to observe.