Next2011 Architecture for the 10^x

721 views

Published on

This is @KnisterPeter and my talk we held at next2011 conference in Berlin.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Next2011 Architecture for the 10^x

  1. 1. Architecture for 10^X 3d-scaling for real world problemsDonnerstag, 26. Mai 2011
  2. 2. Who we are Markus Wolf, @KnisterPeter Meno Abels, @fastandfearless Senior Developer, SinnerSchrader Director, SinnerSchrader 2Donnerstag, 26. Mai 2011
  3. 3. Architecture is important Choosing an architecture has impact in several dimensionsDonnerstag, 26. Mai 2011
  4. 4. DevelopmentDonnerstag, 26. Mai 2011
  5. 5. OperationDonnerstag, 26. Mai 2011
  6. 6. Maintaince MaintenanceDonnerstag, 26. Mai 2011
  7. 7. Our Briefing from We want to sell our store-specific range of goods to our customers online Customers should be able to collect these items within a appointed timeframe In other words: “Click & Collect” Sounds easy.Donnerstag, 26. Mai 2011
  8. 8. Wait: store-specific?Donnerstag, 26. Mai 2011
  9. 9. What else? 2*10^4 products 4*10^2 shops (potential for up to 3*10^3) ... and adding: _unique prices and product-attributes per shop _subset catalogs for specific product lines (e.g. Bio/Rewe-Feine-Welt/Angebote) _personalized catalog We need to have as much webshops as real shops providing this service.     Donnerstag, 26. Mai 2011
  10. 10. Personalized Catalog for each customer?Donnerstag, 26. Mai 2011
  11. 11. The Establishment will fail No standard shop software will meet these requirementsDonnerstag, 26. Mai 2011
  12. 12. We have a mission Accept the challenge and think yourselfDonnerstag, 26. Mai 2011
  13. 13. Scaling in 1D Hardware Use memory extensively => around 10^6 faster than disksDonnerstag, 26. Mai 2011
  14. 14. Scaling in 1D Hardware Use parallel algorithms => leverage multicore cpuDonnerstag, 26. Mai 2011
  15. 15. Scaling in 1D Hardware Use stateless components => less error prone multithreadingDonnerstag, 26. Mai 2011
  16. 16. Scaling in 1D Hardware Use view optimized Business Objects => no transformation for view renderingDonnerstag, 26. Mai 2011
  17. 17. Scaling in 1D Hardware => more requests per Server Instance (approx. 100 per second)Donnerstag, 26. Mai 2011
  18. 18. Scaling in 2D Server InstancesDonnerstag, 26. Mai 2011
  19. 19. Scaling in 2D Server Instances “Stateless Statefullness” _No server-side state _All state on clientDonnerstag, 26. Mai 2011
  20. 20. Scaling in 2D Server Instances Shared Nothing „Kind of“ SOA This means easy load-balancing => weʼre cloud-ready!Donnerstag, 26. Mai 2011
  21. 21. Scaling in 3D Client ComputerDonnerstag, 26. Mai 2011
  22. 22. Scaling in 3D Client Computer Use client storage _Persist private data into browser _Caching of product dataDonnerstag, 26. Mai 2011
  23. 23. Scaling in 3D Client ComputerDonnerstag, 26. Mai 2011
  24. 24. Scaling in 3D Client Computer Less server cycles _Gaining performance independent from server side _Green-ITDonnerstag, 26. Mai 2011
  25. 25. Scaling in 3D Client Computer => Less requests, faster user experience, happy users!Donnerstag, 26. Mai 2011
  26. 26. Scaling in Reality Simple CaseDonnerstag, 26. Mai 2011
  27. 27. Enterprise toolchainDonnerstag, 26. Mai 2011
  28. 28. Future ProofDonnerstag, 26. Mai 2011
  29. 29. The Result Server-Software lines of code <2*10^4 (common > 5*10^4) Client-Software lines of code < 10^4 (no one should need more) Development Effort approx. (5*10^1) % (compared to traditional approach) Deployment 3 Systems* *Cost of operations per year is C.H.E.A.P. Cost per user/year is roughly about:Donnerstag, 26. Mai 2011
  30. 30. The ResultDonnerstag, 26. Mai 2011
  31. 31. Be careful! Thank you.Donnerstag, 26. Mai 2011

×