Implementing reliable PHP-based microservices

@junior_grossi IMPLEMENTING RELIABLE PHP-BASED MICROSERVICES or at least, how they
should be ;-) PHP Dublin, May/2020

@junior_grossi Hi, I'm Junior Grossi twitter.com/junior_grossi github.com/jgrossi

@junior_grossi ⚠ Stutterer alert!

@junior_grossi https://github.com/corcel/corcel

@junior_grossi PHPMG Conference 2019 21/09/2019 - Belo Horizonte, Brazil https://conf.phpmg.com

@junior_grossi I ❤ #elePHPants https://elephpant.me/herd/junior_grossi

@junior_grossi https://glofox.com/careers

@junior_grossi ◽ 2004 php ◽ 2016 ◽ 2019 ◽ ✈

@junior_grossi Ahhh the weather! I live in Galway, that's a
bit worse

@junior_grossi Let's talk about microservices

@junior_grossi I WILL BE: Sharing what I've learned ~1 year
Sharing what I'm learning

@junior_grossi THE TITLE Implementing reliable PHP-based microservices

@junior_grossi Implementing reliable PHP-based microservices

@junior_grossi PART 1 Implementing reliable PHP-based microservices

@junior_grossi Microservices? Again? 1-minute tutorial

@junior_grossi "Microservices" is an architectural style It's not gonna solve
problems you don't have yet! (You may never have those problems)

@junior_grossi What's a Monolith?

@junior_grossi

@junior_grossi What's Microservice architecture?

@junior_grossi USING MICROSERVICES Need clear implementations Share implementation issues from
monoliths

@junior_grossi "Don't use microservices if you don't need them"

@junior_grossi RELIABILITY Communication Logging Responsibility Productivity

@junior_grossi COMMUNICATION Sync (HTTP, gRPC) Async (event-oriented)

@junior_grossi SYNC COMMUNICATION

@junior_grossi ASYNC COMMUNICATION Frontend API Gateway Queue Service A Service
B Service C book for a class BOOKING_REQUEST 204 (listening to B_R event) GET /v2/bar {"bar":"123"} BOOKING_CONFIRMED results via websockets if required (listening to B_C event) Send notification

@junior_grossi ASYNC COMMUNICATION A service subscribes to an event Use
the data (payload) to do something // event identifier "BOOKING_REQUEST" // event payload { "userId": "1234567890", "classId": "2345", "classStartDate": "20200514T15:19:21+00:00" }

@junior_grossi BUG INVESTIGATION Frontend API Gateway Queue Service A Service
B Service C book for a class BOOKING_REQUEST 204 (listening to B_R event) GET /v2/bar {"bar":"123"} BOOKING_CONFIRMED results via websockets if required (listening to B_C event) Send notification

@junior_grossi DON'T SKIMP ON LOGS Log all requests sent and
received Log all responses sent and received Log all data from fired events Log all data from received events Log all important decisions "With microservices, logging is like a very close friend."

@junior_grossi

@junior_grossi RESPONSIBILITY Each service needs a reason to exists It's
allowed to duplicate code, but not data Don't you have some data? Ask another service! Think twice before synchronizing/copying data

@junior_grossi WHAT TO AVOID: 2 or more services sharing the
same DB (which service changed the data?) partial domain implementations (when you have related logic splitted in 2+ services)

@junior_grossi PRODUCTIVITY Avoid the "language soup" (pick 2 or 3
max) 1. You hired John. He's good in PHP 2. He starts a new service in Scala 3. He keeps maintaining that service 4. John leaves the company 5. You need now PHP + Scala engineers

@junior_grossi PRODUCTIVITY Use similar so ware architecture and patterns Easier
to move between projects Easier to move between languages Easier to maintain Easier to integrate

@junior_grossi PRODUCTIVITY Share processes along services Share Git/VCS conventions/flows Docker
conventions Share CI/CD practices Share deployment processes

@junior_grossi TOPICS So ware Architecture Design Patterns Execution

@junior_grossi SOFTWARE ARCHITECTURE We need something flexible We need something
organized We need quality We need power

@junior_grossi Robert C. Martin "The goal of so ware architecture
is to minimize the human resources required to build and maintain the required system."

@junior_grossi Changing the architecture is very expensive!

@junior_grossi LAYERED ARCHITECTURE "Leave options opened" (believe me, they do
change) Independent layers Independent use cases Independent commands

@junior_grossi DOMAIN-DRIVEN DESIGN Implementing Domain-Driven Design Vaughn Vernon

@junior_grossi HEXAGONAL ARCHITECTURE "Hexagonal Architecture - Message-Oriented So ware Design"
Matthias Noback - @matthiasnoback https://youtu.be/K1EJBmwg9EQ

@junior_grossi ABOUT YOUR ARCHITECTURE: Framework independent (framework-as-a-tool) Testable without any
external element UI independent (Web / Console) Database independent Independent of any external agent

@junior_grossi CLEAN ARCHITECTURE

@junior_grossi Clean Architecture Robert C. Martin (Uncle Bob)

@junior_grossi SCREAMING ARCHITECTURE "The architecture says by itself" What is
your service about? (Answer by reading the code!) Payments? Bookings? Authentication? Or an app written in Laravel, Slim or Symfony?

@junior_grossi "A good so ware architecture allows decisions about frameworks,
databases, web-servers, and other environmental issues and tools, to be deferred and delayed." Uncle Bob

@junior_grossi https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html

@junior_grossi THE DEPENDENCY RULE "source code dependencies must point only
inward, toward higher-level policies" Nothing from "inside" should know anything concrete about "outside".

@junior_grossi Fine, but how do I do that? Using Interfaces/Abstractions!

@junior_grossi "Code is not reusable. Abstractions are." Marco Pivetta (@Ocramius)

@junior_grossi

@junior_grossi USE CASE: CREATE USER Command Handler Pattern (UseCase)

@junior_grossi 1. CONTROLLER ACTION POST /users UsersController::create() (SRP!!!) CreateUserController

@junior_grossi final class CreateUserController { private CreateUserHandler $handler; public function
__construct(CreateUserHandler $handler) { $this>handler = $handler; } public function __invoke(RequestInterface $request): ResponseInterface { $userId = $this>handler>handle( new CreateUserCommand( $request>getAttribute('email'), $request>getAttribute('firstName'), $request>getAttribute('lastName'), $request>getAttribute('password'), ) ); return new JsonResponse(compact('userId'), 201); } }

@junior_grossi 2. COMMAND Class that stores the data to execute
the action (handler). Immutable class!

@junior_grossi final class CreateUserCommand { private string $email; private string
$firstName; private string $lastName; private string $password; public function __construct( string $email, string $firstName, string $lastName, string $password ) { $this>email = $email; $this>firstName = $firstName; $this>lastName = $lastName; $this>password = $password; } // Getters: getEmail(), getFirstName(), getLastName(), getPassword() }

@junior_grossi 3. HANDLER It's the logic of our use case
Receives the data as a Command class

@junior_grossi final class CreateUserHandler implements HandlerInterface { private UserRepositoryInterface $userRepository;
private PasswordEncrypterInterface $passwordEncrypter; public function __construct( UserRepositoryInterface $userRepository, PasswordEncrypterInterface $passwordEncrypter ) { $this>userRepository = $userRepository; $this>passwordEncrypter = $passwordEncrypter; } public function handle(CreateUserCommand $command): Uuid { return $this>userRepository>add( new User( Uuid::uuid4(), $command>getEmail(), $command>getFirstName(), $command>getLastName(), $this>passwordEncrypter>encrypt( $command>getPassword() ),

@junior_grossi "UI independent (Web / Console)" 1. A er creating
a new studio 2. Create a new admin user Event-oriented (async) running in CLI

@junior_grossi STUDIO_CREATED Command Bus Event A Event B StudioCreatedEvent.php Listener
1 Listener 2 Listener 3 CreateAdminUserListener.php Listener 4

@junior_grossi final class CreateAdminUserListener implements ListenerInterface { private CreateUserHandler $handler;
public function __construct(CreateUserHandler $handler) { $this>handler = $handler; } public function execute(StudioCreatedEvent $event): void { $this>handler>handle( new CreateUserCommand( // use the payload from $event ) ); } }

@junior_grossi EXECUTION Leaving the comfort zone

@junior_grossi "NodeJS is better for microservices"

@junior_grossi Coroutine based Async PHP programming framework Build high-performance, scalable,
concurrent TCP, UDP, Unix Socket, HTTP, WebSocket services with PHP and fluent Coroutine API. > It extends some use cases for PHP https://www.swoole.co.uk/

@junior_grossi How PHP naturally works phpfpm | "blocking I/O" CPU
I/O

@junior_grossi How Swoole & Node.js works "non-blocking I/O" | async
CPU I/O

@junior_grossi > pecl install swoole built-in async, coroutine support, multiple
threads I/O modules async/await yield

@junior_grossi

@junior_grossi Master Reactor Reactor Reactor Timer Manager TaskWorker TaskWorker TaskWorker
Worker Worker Worker

@junior_grossi

@junior_grossi Initialisation Execute Task Clean up PHP-FPM Execute Task Swoole

@junior_grossi ADVICE ⚠ Use it for new services only (it's
not a good idea for that legacy API you have)

@junior_grossi COMMON PITFALLS ☢ Variable scope / DI container (Singleton)
Exception handling Static content

@junior_grossi https://docs.mezzio.dev/mezzio-swoole/ https://github.com/mezzio/mezzio-swoole

@junior_grossi http://swo .io/

@junior_grossi Coroutine Based Concurrency with PHP and Swoole Bruce Dou
| @doubaokun Feb 2020 PHPUK2020 https://speakerdeck.com/doubaokun/coroutine-based-concurrency-with-php-and-swoole

@junior_grossi THANK YOU! http://twitter.com/junior_grossi http://speakerdeck.com/jgrossi

Implementing reliable PHP-based microservices

Implementing reliable PHP-based microservices

More Decks by Junior Grossi

Other Decks in Programming

Featured

Transcript