The MVC concept doesn't imply monolith. Eventually the tooling will catch up to the PaaS change. There are already some frameworks like serverless that try to do this, they are just bad at it for now. This is not all the fault of the frameworks either, scalable cloud components are PITA to build and configure.
For example: Lambda forces a specific AWS Linux build of each language it supports, and all default libraries that can be stripped out have been. The build package for each Lambda is small, so all libraries and data have to be zipped down to 50MB or less which completely rules out tons of common libraries.
The concept is really cool, often usable, and incredibly cheap. The platform and tools will get better, and eventually MVC will work on PaaS someday, but for now it is a pain to ride the bleeding edge.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The MVC concept doesn't imply monolith. Eventually the tooling will catch up to the PaaS change. There are already some frameworks like serverless that try to do this, they are just bad at it for now. This is not all the fault of the frameworks either, scalable cloud components are PITA to build and configure.
For example: Lambda forces a specific AWS Linux build of each language it supports, and all default libraries that can be stripped out have been. The build package for each Lambda is small, so all libraries and data have to be zipped down to 50MB or less which completely rules out tons of common libraries.
The concept is really cool, often usable, and incredibly cheap. The platform and tools will get better, and eventually MVC will work on PaaS someday, but for now it is a pain to ride the bleeding edge.