SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
Tips and Tricks for your Service Oriented Architecture @ CakeFest 2013 in San Francisco
14.
A software design based on discrete software
components, "services", that collectively
provide the functionalities of the larger
software application
15.
You typically start with the
infamous web application
which does everything on its own
16.
Then you realize that to provide
a chat system to your users
PHP might not be the best...
17.
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
22.
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
76.
JOSE
http://www.thread-safe.com/2012/03/json-object-signing-and-encryption-jose.html
77.
1. The user enters the
credentials once in your
frontend
JS APP
AUTH
SERVICE
2. The JS app will forward them
to your Auth webservice
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
78.
1. The user enters the credentials
once in your frontend
JS APP
79.
AUTH
SERVICE
2. The JS app will forward them
to your Auth webservice
JS APP
80.
AUTH
SERVICE
3. The Auth webservice will then generate the
encrypted JWS and set a cookie with its value
81.
JS APP
AUTH
SERVICE
4. The JS app can now just execute
calls using that cookie
82.
1. The user enters the
credentials once in your
frontend
JS APP
AUTH
SERVICE
2. The JS app will forward them
to your Auth webservice
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
146.
SoC happens at architectural, not application, level and you can perform large-scale
refactorings without the fear of destroying the entire system