Symfony 4 | Creating a Microservice (part 3)

preview_player
Показать описание
Part 3: Deserializing the Event

In this series of video's, I will show you a way of creating a Microservice using Symfony 4. We will use the following techniques in these video's:

- Symfony 4
- Docker
- PHPUnit
- Liip functional test bundle
- JMS Serializer
- Doctrine
- Domain Driven Design (DDD)
- Test Driven Development
- SOLID design Principles
- Hexagonal Architecture

The video's are editted from a livestream where I build this microservice live. The usecase for this microservice is a fully functional Commenting system (backend-only)

Also: Im up for any question/feedback in the comments, let me know what you think!
Рекомендации по теме
Комментарии
Автор

My Sincere apologies for all the visual artifacts & glitches. I found out this was happening a bit later (in the next part) and it is because of a combination between Ubuntu and OBS (my streaming software). I will make sure this won't happen when I am doing my next stream.

QbrainTV
Автор

Hi! Excellent series! Please keep them coming!

ynslife
Автор

Why don't ask the handler as a service (already configured from DI). instead of the serializer?

antonkarpov
Автор

20:00 couldn't you just grab the event instance from the container (no need for new and no need to pass the serializer)?

angelogrieco
Автор

Hi. Congrats for this awesome series. One question though: it's ok to have things related to infrastructure, like jms serializer, injected into business logic(application layer), or we should keep application framework agnostic? Wouldn't be better to do the deserialization within the controller action and then go further with an command/query object or something similar?

Paul-rjhx