Next time you're at the beach, look for the excess microservices littered in the sand. This is a haunting reminder of the devastating impact they have on our ecosystem.
THE DANGERS OF MICROSERVICES: A THREAD.
Microservices are tiny services, as the name implies. The problem with microservices is that they do not break down into harmless modules. They can take hundreds or thousands of years to decompose. 1/n
MICROSERVICES ARE DANGEROUS!
When you divide your architecture into microservices, it blocks the natural flow of energy through your system. TOXINS build up with nowhere to go! Stick to healthy and natural monolith design.
When you put tests around your code, it stops TOXINS from naturally leaving it during development! This is one of the leading causes of system failures.
I never use rigorously tested software with heavy production monitoring. It's so bad for you. Instead I just deploy fresh, untested software straight from the developer's machine.
Did you know that instead of buying proprietary software full of harmful chemicals, you can make your own at home using all natural ingredients like punch cards?
Our new software consultancy produces what we call "raw code", guaranteed NOT to have passed through CI or any kind of onerous "testing". The result is a palpably richer and more authentic software experience
Remember when we didn't have all of this over-processed code in our software? Remember the good old days when it was just raw ones and zeroes? All Natural Code remembers.