Wow what an emotional and biased take. Architecture isn’t like Lord of the Rings where one ring rules them all. What if the dev team doesn’t know Java? Are y

Wow what an emotional and biased take. Architecture isn’t like Lord of the Rings where one ring rules them all. What if the dev team doesn’t know Java? Are you suggesting they be forced to learn it? What if the company has 20 applications with complex interactions? Are you suggesting they all be baked into k8s and then have someone manage containers full-time? What if no one in the company understands containers? I’ve been at this for 40 years and will tell you there is no common architecture environment. There can be any mix of business logic, services, data storage, containers, events, queues, redundancy, reports, analytics, external systems, 3rd party black boxes, skill sets and levels, budget, tech stack, and leadership. Trying to pigeonhole any architecture into that mix is the very definition of amateur.