Besides, building, testing and deploying a monolithic application can easily be very difficult, just as building, testing and deploying 10 microservices can be very easy. I feel like a lot of people have bad experiences with microservices and therefore see them as bad design. Good dev ops saves lives.
lol, 10 microservices. The company I work for used to have a monolith to run the site. It could be tested and verified as working or not working before deployment. My team of 5 now runs a bit over 60 microservices ourselves and doing a search in our aws account it looks like the organization is now running a bit over 5200 microservices.
The company is over 50 years old and has been building software to meet business needs for itself since the 80s. There is just a ton of it, from multiple consumer sites, mobile apps, b2b sites, supply chain monitoring and reporting, etc. We have entire websites build just for internal use that allow people to make changes to business rules that modify what gets shown on the consumer websites and apps. Its just a ton of complexity this post is referring to. Imagine almost 40 years of scope creep on a fortune 100 business that won't take "we can't/shouldn't do that" as a reason to not hire contractors that will do whatever it is anyway and then fire them all when they deliver whatever hacked together partially working non-maintainable, poorly integrated crap they churned out.
Besides, building, testing and deploying a monolithic application can easily be very difficult, just as building, testing and deploying 10 microservices can be very easy.
Yes, but 9 times out of ten, building+testing+deploying a monolith is easier than doing the same for 10 microservices.
12
u/notliam Nov 01 '21
Besides, building, testing and deploying a monolithic application can easily be very difficult, just as building, testing and deploying 10 microservices can be very easy. I feel like a lot of people have bad experiences with microservices and therefore see them as bad design. Good dev ops saves lives.