Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Rahebr's avatar

Best practice for microservice setup

Hey!

I am currently starting a project where the objective is to turn a monolith into multiple different microservices in separate docker containers. These are my first ventures into containerization and docker, so excuse my lack of knowledge on the topic.

After playing around with both laravel sail and laradock.io, I've had most success with laradock.io. Its just super easy to setup the environment and add new laravel projects to it. However, I would like to prepare for the future deployment when the microservices are going into the wild..

  1. When getting to the deployment stage, I'm aware that I should do "something else" then using laradock. Is there anything I could benefit from doing now to prepare for that stage, or is it ok to just use laradock for now and get into the deployment when I get there.

  2. My plan was to setup all my different microservices in separate dockers in my local setup. But that seems like a pain to do with laradock since I would need to change all the different servicenames, ports, etc. It also seems a little overkill. I still intend to deploy the microservices in different containers though.

Will I complicate things in the deployment stage by running all my microservices in a single docker locally, but deploy them as separate dockers to production?

0 likes
1 reply

Please or to participate in this conversation.