Kubernetes allows you to mount block storage volumes for storing files. But each volume can only be mounted to a single server instance (pod). So if you want multiple pods to access your volume, you need to configure and deploy an NFS service. In which world is this simple, convenient, or straightforward?
While I am far from a microservice evangelist, when you adopt a framework you have to adjust your architecture to that platform to be as successful as possible.
Microservices are intended to be _bounded contexts_ and if you violate that concept you retain the complexity and lose the benefits of the tradeoff analysis that should have been done to decide on your chosen framework.
Adding crosscutting concerns like a NFS server violates the context boundary and leads you down the path of building a brittle distributed monolith.
The concept of independent deployability in microservices is a guide to help avoid architectural erosion.
The real answer to this problem is to quit making random golf course architecture decisions and make pragmatic choices.
Architecture is about finding the least worst option and is context specific with lots of nuance.
If you simply quit focusing on silver bullet myths and focus on what you needs are and adapt how you build your systems to work with the frameworks you have chosen things will work better.
Good Architecture is hard, but not nearly as hard as repeatedly building balls of mud and blaming the tools that you have chosen due to hype, habits, resume building and/or complacency.
Comments
While I am far from a microservice evangelist, when you adopt a framework you have to adjust your architecture to that platform to be as successful as possible.
Microservices are intended to be _bounded contexts_ and if you violate that concept you retain the complexity and lose the benefits of the tradeoff analysis that should have been done to decide on your chosen framework.
Adding crosscutting concerns like a NFS server violates the context boundary and leads you down the path of building a brittle distributed monolith.
The concept of independent deployability in microservices is a guide to help avoid architectural erosion.
The real answer to this problem is to quit making random golf course architecture decisions and make pragmatic choices.
Architecture is about finding the least worst option and is context specific with lots of nuance.
If you simply quit focusing on silver bullet myths and focus on what you needs are and adapt how you build your systems to work with the frameworks you have chosen things will work better.
Good Architecture is hard, but not nearly as hard as repeatedly building balls of mud and blaming the tools that you have chosen due to hype, habits, resume building and/or complacency.