Russell Harrison's List: Scalability

• reduce I/O overhead
• Adding a caching layer
• Moving from a database-centric approach to partitioning
• away from the classic two-phase commit and XA
• LAMP provides a cost-effective solution
• Java is still used, but not as the primary language

4 more annotations...

• hard to scale-out the overall business
• If you use a middleware package you get lock-in around the software patterns they have chosen. You'll only be able to use their software.
• You're stuck
• gave them the isolation
• many software components rapidly and independently
• hundreds of services
• aggregate the information from the services
• use only servlets
• framework and not a tool
• you get lock-in
• software patterns they have chosen
• only be able to use their software
• 70% use REST
• Organized Around Services
• Teams are Small
• two pizza teams
• anyway they see fit
• design that is as minimal as possible
• deliver infinite storage
• can't see everyone
• divide nodes into small groups
• either high consistency or high availability
• parallel and isolated development
• create an ecosystem around your application
• simple as possible
• expose real customers to a choice and see which one works best
• getting rid of the influence of the HiPPO's
• get the most value and innovation

26 more annotations...