>The things on the left that are simple and proven, while the things on the right are hyped and volatile. >3-tier applications vs. micro services As yes, the

>The things on the left that are simple and proven, while the things on the right are hyped and volatile. >3-tier applications vs. micro services As yes, the volatile and unknown territory of the architecture formerly known as "Service Oriented Architecture" that has been in use since at least the early 2000's. I get what this guy is trying to say, but examples like this don't help. Ultimately, I don't subscribe to his manifesto any more than I subscribe to manifestos about SQL being dead or monoliths being poison in all cases. These things are all tools in the toolbox. You'll use some of them more than others during your career. You might use a given tool a lot because you like it, or you might use it a lot because it's a really useful tool even if you hate it. Both are fine. In addition, you'll find that sometimes you really /do/ need a triwing screwdriver, so it's nice to have that in your toolbox as well. Don't be that guy who throws out either SQL /or/ NoSQL just because he likes the other thing or thinks it's more widely applicable. Both technologies suit some use cases the other doesn't. Use the tool that's right for the job, don't get culty about trying to wrangle an ill-fitting tool to a job it was never designed for just because you've tied your ego to it.