ZgPHP #97
Luka Vavetić and Frano Šašvari:
Microservice architecture in Laravel
www.typeqast.com

ZgPHP #97
Luka Vavetić and Frano Šašvari:
Microservice architecture in Laravel

ABOUT US
• Luka, PHP developer
• Frano, PHP developer

ABOUT PROJECTS
• Backend: PHP (Laravel framework, Doctrine ORM)
• Database: MySQL
• Other: SOAP, RabbitMQ, Docker, Postman…
• Testing: Unit, Integration

TOPICS
RPC STYLE
API
RABBITMQ VALIDATION
HISTORY TESTS

RPC STYLE API
• RPC - Remote Procedure Call
• JSON body
• Why RPC?
• Not for everything (CRUDs?)
• Depends on business logic

RPC STYLE API
REST RPC
• users (GET)
• users/1 (GET)
• users (POST)
• users/1 (PUT/PATCH)
• users/1 (DELETE)
• users.list (GET)
• users.info (GET)
• users.create (POST)
• users.update (POST)
• users.delete (POST)

RPC STYLE API
REST RPC
• users/registration (POST) OR
• users (POST) OR
• registration (POST)
• users.registration (POST)
• users/1/teams/2 (POST)
• users/1/channels/2 (DELETE)
• teams.addUser (POST)
• channels.leave (POST)

RABBITMQ
• Message broker
• Glue in microservice arhitecture
• Publisher/Subscriber

RABBITMQ

RABBITMQ SENDER

RABBITMQ CONSUMER

VALIDATION
• Laravel’s Validation was not enough
• Why not use Laravel’s FormRequest?
• Custom Validation with error codes needed
• How to handle Validation exceptions?
• Better and more strict communication between
other APIs and frontend APPs

HISTORY
• Watch changes on important Entities
• Package? Doctrine Loggable
• Rollback option with versioning

TESTS
• Unit Tests
• Integration Tests

THANK YOU
Drop us a line:
• frano.sasvari@typeqast.com
• luka.vavetic@typeqast.com
Questions?