I'm finding quite a few problems with the content this post and I couldn't help nitpicking because of the first problem. This caught my interest at first, > 6

I'm finding quite a few problems with the content this post and I couldn't help nitpicking because of the first problem. This caught my interest at first, > 68% of IT professionals increased their Kubernetes use due to the pandemic. It turns out the original statement was about it being _during_ the pandemic, not _due_ to the pandemic. Please use the right words as 'due to' implies there was a causality to it. The author then describes > module A calls B and module B calls C. > ... However, you’re also running these processes across the network But in the same paragraph is equating modules with microservices. Modules are a code artefact within the application, microservices are applications. Next there's a comparison between the latency and asynchronous services, and loosely coupling such services; these are different use cases, but neither have anything to do with k8s. > Unfortunately, many developers using Kubernetes are working just the opposite. So... then they've made the wrong platform choice? Not everything needs to go on a k8s cluster. And not every team can make a database system autonomous for various reasons; for those teams, staying monolithic should be the best choice. Changing your development workflow to fit a tooling's paradigms will cause more problems than the problems they solve. > In reality, best practices today are completely counterintuitive to how legacy monolithic applications were built. 'Best practices' are the new (anti)'anti-pattern'. Everyone loves to throw around the phrase best-practices to describe methodologies that they are promoting, just like everyone calls things they don't like an anti-pattern.