22. âA software design based on discrete software
components, "services", that collectively
provide the functionalities of the larger
software applicationâ
â A.Nadalin (@_odino_)
23. FULL STACK IS DEAD!
âMicroservice Architecture" [âŠ] a particular way
of designing software applications
as suites of independently deployable servicesâŠâ
â M.Fowler
28. HTTP
A protocol that is almost 25 years old
and is here to stay!
29. GET vs POST
âThe difference is that in
a GET request you have the parameters in the url ,
with
a POST the parameters are in the requestâs bodyâ
answered by 80% of candidates during the interview
36. Rabbitmq
Language and protocol format agnostic
You can easily create an event driven
architecture
Messages stay in the queue if a service
goes down
Too many messages? add more consumers!
38. PHP
It follows standards (PSR-*)
Decoupled components
Huge and active opensource community
Easy to plug in your domain code
Not just a framework, but a projectâŠ
Designed starting from the HTTP protocol
74. redis
Key types: lists, hashes, sets, sorted sets
Persistent to disk
Up to 512MB per key
Pub/sub
Transactions with optimistic locking
Lua scripting embedded