Before reading this article, I strongly recommend reading my previous two articles.
Despite all of these inputs, I am still saying platform architecture depends upon various needs of the platform, hence there is nothing like one standard way, it will be always evolving. Hence let us look into some of the references for Highly Scalable Platform Architectures to understand even better
- Linked in Architecture – Reference – Click Here
Observe here, a separate replica set for Database ?
- Uber Architecture – Reference Click Here
Uber has a micro-service architecture.
- Netflix Architecture – Reference Click Here
Netflix architecture looks very complex and it is micro-service architecture
Some highlights of Netflix Architecture, Hundred’s of microservices and one giant service. thousand’s of servers spread across the world, thousand’s of Content Delivery Networks, Netflix uses their own CDN called Open Connect
- 100s of microservices
- 1000s of daily production changes
- 10,000s of instances running in AWS cloud
- 10, 000, 000, 000 hours of streamed
This is how it looks 🙂
Reference: How Netflix works: the (hugely simplified) complex stuff that happens every time you hit Play
- Ebay Architecture