Symfony 4 | Creating a Microservice (Part 5)

Symfony 4 | Creating a Microservice (Part 5)



Part 5: Doctrine

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)

Feel free to follow me on twitch so you get a notification when I am streaming:

Also: Im up for any question/feedback in the comments, let me know what you think!

6 thoughts on “Symfony 4 | Creating a Microservice (Part 5)

  1. Hi, I am trying to code along with you and I am getting the following error when I try to run the migrations: The metadata storage is not up to date, please run the sync-metadata-storage command to fix this issue. However, running doctrine:migrations:sync-metadata-storage does not seem to do anything, it just repeats the error. Do you know how to fix this?

  2. Why don't you just use another database link in your tests config and reside that database at the tempfs storage? Database manipulations during the tests will be done entirely in RAM not affecting hard drive so when test case count grows it gives solid performance advantage. Also using another database for tests allows you to keep your dev database untouched, sometimes it is very handy.

  3. although I generally liked the content of this miniseries, it should not be called <<<Symfony 4 | Creating a Microservice>>> but more like <<<TDD development with Symfony 4>>> .. the microservice in the title is misleading.

Leave a Reply

Your email address will not be published. Required fields are marked *