Reactive Architecture (PHPCon PL 2015)
•
1 like•1,065 views
Couple words about what is Reactive Architecture and how it influence on modern IT organization.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Reactive Architecture (PHPCon PL 2015)
Similar to Reactive Architecture (PHPCon PL 2015) (20)
Recently uploaded
Recently uploaded (20)
Reactive Architecture (PHPCon PL 2015)
- 1. Reactive Architecture Marek Sokół IT Architect
- 2. The demands and expectations for web applications have changed in recent years... 2Marek Sokół – Reactive Architecture
- 3. • React to events – 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 is more... 4 robustness flexibility resilience Marek Sokół – Reactive Architecture
- 5. 5 So we have got an application Marek Sokół – Reactive Architecture
- 6. Why the codebase of your company is all in one repository? 6Marek Sokół – Reactive Architecture
- 7. Numerous developers work on the same repository at the same time... 7Marek Sokół – Reactive Architecture
- 8. Daily stand-up meeting is too long... and boring... 8Marek Sokół – Reactive Architecture
- 9. Why are there so many tables in this database? 9Marek Sokół – Reactive Architecture
- 10. Database backup cannot be done within 24h... 10Marek Sokół – Reactive Architecture
- 11. ...and what if the administrator has never tested a backup file? 11Marek Sokół – Reactive Architecture
- 12. The choice of architecture is more 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 be divided into smaller teams to build microservices of our SOA system 16Marek Sokół – Reactive Architecture
- 17. Each microservice can be implemented with the most suitable methods and technologies 17Marek Sokół – Reactive Architecture
- 18. Scaling microservices instead of the whole system is now possible 18Marek Sokół – Reactive Architecture
- 19. Reactive Manifesto Principles 19Marek Sokół – Reactive Architecture
- 20. • Drop synchronous HTTP 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 cascading failures • 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