Symfony2 is one of the de-facto standards for developing enterprise-ready applications in PHP: being a very structured & decoupled framework, it becomes very handy and suitable for building Service Oriented architectures, which require loose coupling and a clean and tested structure: we will see hot to create a Service Oriented Architecture in Symfony2, taking advantage of messaging systems like RabbitMQ, HTTP APIs and Sf2's internals.
11. A software design based on discrete software
components, "services", that collectively
provide the functionalities of the larger
software application
12. You typically start with the infamous PHP
app, hopefully built with Symfony2
which does everything on its own
13.
14. Then you realize that to provide
a chat system to your users
PHP might not be the best...
15.
16. And soon you also decide,
to improve performances,
that your frontend should have its own
in-memory persistence, to be faster
and you put it into another service
24. In human-understandable words, SOA is a software design which
embraces splitting a monolithic, totalitarian software
architecture into smaller pieces, thus making them independent,
loosely coupled and more maintainable
114. 1. The user enters the
credentials once in your
frontend
2. The JS app will forward them
to your Auth webservice
JS APP
AUTH
SERVICE
3. The Auth webservice will
then generate the encrypted
JWS and set a cookie with
its value
JS APP
4. The JS app can now just
execute calls using
that cookie
115. 1. The user enters the credentials
once in your frontend
JS APP
116. 2. The JS app will forward them
to your Auth webservice
JS APP
AUTH
SERVICE
117. AUTH
SERVICE
3. The Auth webservice will then generate the
encrypted JWS and set a cookie with its value
119. 1. The user enters the
credentials once in your
frontend
2. The JS app will forward them
to your Auth webservice
JS APP
AUTH
SERVICE
3. The Auth webservice will
then generate the encrypted
JWS and set a cookie with
its value
JS APP
4. The JS app can now just
execute calls using
that cookie
204. SoC happens at architectural, not application, level and you can perform large-scale
refactorings without the fear of destroying the entire system