Revitalizing Walmart's Aging Architecture for Web Scale
- 2. Typesafe Reactive Platform » Play - RESTful API framework » Akka - Distributed computing framework » Spark - General purpose in- memory compute engine » ConductR, Monitoring, and commercial features
- 8. Theworld by2020 » 4 billion connected people » 25+ million apps » 25+ billion embedded systems » 40 zettabytes (40 trillion gigabytes) » 5,200 GB of data for every person on Earth
- 10. Business Impact
- 11. The goal » ~100% availability ("nine nines")
- 12. The goal » ~100% availability ("nine nines") » Consistent responsiveness under varying load conditions
- 13. The goal » ~100% availability ("nine nines") » Consistent responsiveness under varying load conditions » Predictable spikes of traffic, e.g, Black Friday » Less predictable spikes of traffic, e.g, marketing campaign driving traffic
- 14. The goal » ~100% availability ("nine nines") » Consistent responsiveness under varying load conditions » Predictable spikes of traffic, e.g, Black Friday » Less predictable spikes of traffic, e.g, marketing campaign driving traffic » Enable LOBs to rapidly adapt to market conditions
- 16. Walmart's Business Uplift » Conversions up 20% » Mobile orders up 98% » No downtime Black Friday or Boxing Day
- 17. Walmart's OperationalSavings » Moved off expensive hardware » On cheap virtual x86 servers » 20% - 50% cost savings » ~ 40% compute cycles
- 18. Whereto begin?
- 23. asynchronous, non-blocking, real-time, highly- available, loosely coupled, scalable, fault-tolerant, concurrent, reactive, event-driven, push instead of pull, distributed, low latency, high throughput...
- 24. asynchronous, non-blocking, real-time, highly- available, loosely coupled, scalable, fault-tolerant, concurrent, reactive, event-driven, push instead of pull, distributed, low latency, high throughput... Too complicated. We need a simple vocabulary.
- 25. Reactive The ultimate maturity model for microservices. » Responsive » Resilient » Elastic » Message-driven
- 26. Why,What, How Reactive (principles) » responsive, resilient, elastic, message-driven
- 27. Why,What, How Reactive (principles) » responsive, resilient, elastic, message-driven Microservices (strategy) » bounded contexts (DDD), event sourcing, CQRS, eventual consistency
- 28. Why,What, How Reactive (principles) » responsive, resilient, elastic, message-driven Microservices (strategy) » bounded contexts (DDD), event sourcing, CQRS, eventual consistency Tools (implementation) » Typesafe Reactive Platform (Play, Akka, Spark)
- 29. Heritage system
- 30. Future system
- 32. Ecosystem plus: » service registry » service discovery » architecture visualization » security
- 33. Implementation?
- 35. Message-driven » distribution » location transparency » isolation
- 37. Resilient » dedicated separate error channel
- 38. Elastic » scale up » async » non-blocking » scale out » immutable data » share nothing
- 39. Responsive » responsive to events, load, failure, users » embrace new concepts and patterns » cluster computing » distribution of data » new patterns like circuit breakers
- 41. Whatwe offer
- 42. Commercialfeatures » Akka Split Brain Resolver » Akka 2.3 Cluster Support for Docker » Play User Quotas » Play SOAP
- 43. ProjectSuccess Subscription » Certified build » Compatibility verifications » Security alerts » Binary updates » Long-term support » Legal protection
- 44. Typesafe ConductR ManageTypesafe Reactive Platformapplicationsacrossacluster
- 45. Typesafe Monitoring Knowexactlywhatyour Reactive system is doing
- 46. Thankyou! Visit https://www.typesafe.com/products/typesafe- reactive-platform to get started Contactinfo » Twitter: @kvnwbbr » Email: [email protected]