- Lessons from Giant-Scale Services – Eric Brewer, UC Berkeley & Google
- Designs, Lessons and Advice from Building Large Distributed Systems – Jeff Dean, Google
- How to Design a Good API & Why it Matters – Joshua Bloch, CMU & Google
- On Efficiency, Reliability, Scaling – James Hamilton, VP at AWS
- Things to Keep in Mind When Building a Platform for the Enterprise – Heidi Williams, VP Platform at Box
- Principles of Chaos Engineering
- Finding the Order in Chaos
- The Twelve-Factor App
- Clean Architecture
- High Cohesion and Low Coupling
- Monoliths and Microservices
- Design Skema Database MongoDB Part 1
- Design Skema Database MongoDB Part 2
- Apa itu CAP Theorem
- System Design-TRD Cheatsheet
- CQRS : Command Query Responsibility Segregation
- CAP Theorem and Trade-offs
- CP Databases and AP Databases
- Stateless vs Stateful Scalability
- Scale Up vs Scale Out
- Scale Up vs Scale Out: Hidden Costs
- Best Practices for Scaling Out
- Best Practices for Continuous Delivery
- ACID and BASE
- Blocking/Non-Blocking and Sync/Async
- Performance and Scalability of Databases
- Database Isolation Levels and Effects on Performance and Scalability
- The Probability of Data Loss in Large Clusters
- Data Access for Highly-Scalable Solutions: Using SQL, NoSQL, and Polyglot Persistence
- SQL vs NoSQL
- SQL vs NoSQL – Lesson Learned at Salesforce
- NoSQL Databases: Survey and Decision Guidance
- How Sharding Works
- Consistent Hashing
- Consistent Hashing: Algorithmic Tradeoffs
- Don’t be tricked by the Hashing Trick
- Uniform Consistent Hashing at Netflix
- Eventually Consistent – Werner Vogels, CTO at Amazon
- Cache is King
- Anti-Caching
- Understand Latency
- Latency Numbers Every Programmer Should Know
- The Calculus of Service Availability
- Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
- Common Bottlenecks
- Life Beyond Distributed Transactions
- Relying on Software to Redirect Traffic Reliably at Various Layers
- Breaking Things on Purpose
- Avoid Over Engineering
- Scalability Worst Practices
- Use Solid Technologies – Don’t Re-invent the Wheel – Keep It Simple!
- Simplicity by Distributing Complexity
- Why Over-Reusing is Bad
- Performance is a Feature
- Make Performance Part of Your Workflow
- The Benefits of Server Side Rendering over Client Side Rendering
- Automate and Abstract: Lessons at Facebook
- AWS Do’s and Don’ts
- (UI) Design Doesn’t Scale – Stanley Wood, Design Director at Spotify
- Linux Performance
- Building Fast and Resilient Web Applications – Ilya Grigorik
- Accept Partial Failures, Minimize Service Loss
- Design for Resiliency
- Design for Self-healing
- Design for Scaling Out
- Design for Evolution
- Learn from Mistakes
Ikuti Blog Saya
Dapatkan konten baru yang dikirim langsung ke kotak masuk Anda.
Microservice 