Download as PDF, PPTX
Uploaded byMarek Sokół
Reactive Architecture (PHPCon PL 2015)
The document discusses reactive architecture principles for building responsive, scalable, and resilient applications. It covers moving from monolithic to microservice architectures using a service-oriented approach with asynchronous communication between loosely coupled services. Key principles for reactive systems are discussed, including being event-driven, responsive with asynchronous non-blocking requests, scalable through isolation and replication, and resilient by avoiding cascading failures. The goals are to develop software that can react to events, users, load, and failures.
More Related Content
Similar to Reactive Architecture (PHPCon PL 2015)
Reactive Architecture (PHPCon PL 2015)
- 1. Reactive Architecture Marek Sokół ITArchitect
- 2. The demands andexpectations for web applications have changed in recent years... 2Marek Sokół – Reactive Architecture
- 3. • React toevents – Event-driven 3 • React to users – Responsive • React to load – Scalable • React to failure – Resilient We need to build software that... Marek Sokół – Reactive Architecture
- 4. But there ismore... 4 robustness flexibility resilience Marek Sokół – Reactive Architecture
- 5. 5 So we havegot an application Marek Sokół – Reactive Architecture
- 6. Why the codebase ofyour company is all in one repository? 6Marek Sokół – Reactive Architecture
- 7. Numerous developers work on thesame repository at the same time... 7Marek Sokół – Reactive Architecture
- 8. Daily stand-up meeting istoo long... and boring... 8Marek Sokół – Reactive Architecture
- 9. Why are there somany tables in this database? 9Marek Sokół – Reactive Architecture
- 10. Database backup cannot bedone within 24h... 10Marek Sokół – Reactive Architecture
- 11. ...and what ifthe administrator has never tested a backup file? 11Marek Sokół – Reactive Architecture
- 12. The choice of architecture ismore important than any framework 12Marek Sokół – Reactive Architecture
- 13. Monolith 113Marek Sokół –Reactive Architecture
- 14. SOA 14Marek Sokół –Reactive Architecture
- 15. 15Marek Sokół –Reactive Architecture Now we can create the code faster and it’s easier to maintain
- 16. Developers can bedivided into smaller teams to build microservices of our SOA system 16Marek Sokół – Reactive Architecture
- 17. Each microservice can beimplemented with the most suitable methods and technologies 17Marek Sokół – Reactive Architecture
- 18. Scaling microservices instead ofthe whole system is now possible 18Marek Sokół – Reactive Architecture
- 19. Reactive Manifesto Principles 19Marek Sokół– Reactive Architecture
- 20. • Drop synchronousHTTP requests • Communicate services via asynchronous events • RESTful messages consumers operate only on data in message 20Marek Sokół – Reactive Architecture Event Driven
- 21. 21Marek Sokół –Reactive Architecture
- 22. 22Marek Sokół –Reactive Architecture
- 23. • Websockets 23 Responsive Marek Sokół– Reactive Architecture • Asynchronous and non-blocking requests • Back-pressure
- 24. 24 Scalable Marek Sokół –Reactive Architecture
- 25. 25 Resilient • Avoid cascadingfailures • Isolate failures Marek Sokół – Reactive Architecture • Loose coupling • Replicate data
- 27. 25Marek Sokół –Reactive Architecture
- 28. Robustness 27Marek Sokół –Reactive Architecture
- 29. 28Marek Sokół –Reactive Architecture Flexibility
- 30. Resilience 29Marek Sokół –Reactive Architecture
- 31.