A lot of people seems to think that monoliths are a bad thing and microservives a good thing. That isn't the case. There is nothing wrong with monoliths. Tryin

A lot of people seems to think that monoliths are a bad thing and microservives a good thing. That isn't the case. There is nothing wrong with monoliths. Trying to make everything work as microservives just for the sake of it, or because it sounds cool is just a terrible idea. Start out with a monolith, and if you later see a need to create a microservive, then do it, when you have more knowledge about the bounderies of the service. I love creating high performance services and playing with containers. It sure is cool with microservives that can scale linearly over a lot of machines. I also enjoy using the latest frameworks. But guess what, my first ever service is just using a cheap dedicated server, serves an average of ~250 highly dynamic webpages each second while still using less than 7 % CPU, on PHP and MariaDB. Last 12 years have resulted in about 6 hours of downtime. A couple of hours planned, a couple as a result of denial of service attacks and a couple when there was a power issue at the datacenter. So what I'm trying to say is that more complicated doesn't mean that it's better.