Title 03 - How Do You Know You Have Built A Good System.pdf ✅

How do you know that you have builta good system? Every system is "infinitely"buildable and hence knowing when to stop the evolution is important Here are some pointers thatwill help you 2.You broke your system into components Feed Generator 12 >Webserver Aggregator A Y > S ↓atabase ->exclusive 2. Every componenthas a clear setofresponsibilities Feed webserver -> selves feed over HTTP ~ posts, friends, recommend Feed generator - pulls data from multiple services and putsthem in DB ↳ candidate feed items Feed Aggregator -> combines candidate items fetch be generator, filters out redundant, ranks and creates a final consumable feed
3.For each component, you've slighttechnical details figured out 2. Database and Caching 2. Scaling a Faulttolerance 3. Async processing (Delegation) 4. Communication 4. Each component (in isolation) is scalable - horizontally scalable ->mostly data* faulttolerant - plan for recovery in case of a failure ↳ to a stable state available -> componentfunctions even when some component "fails" This is precisely how we would tackle every single system. structured and detailed