Powered MVC — Software Design Pattern for Go

You may have heard of MVC as design pattern in software engineering, but have you heard of Powered MVC? you haven’t because I’ve invented this term.

Let’s look at how MVC is being used in the 2 major applications of this design patterns. Monolith Applications tend to follow MVC design patterns in most of the web app applications. Micro-services also use individual MVC for each micro-service. The current underdog in design patterns is Modular Monolith. Modular Monolith divides the services and the domain models within a monolith application such that such that the application works is a monolith but, each and every Entity that has the potential to function as a micro-service is defined as an MVC.

With all Modular monolith the problem of single point of failure remains. However when If you embraced modular monolith for your monolith application, shifting to Micro-services becomes less hassle. Powered MVC is a way of structuring the project in such a way that each and every.

What’s the catch here, It’s just separating code for better readability? well I would argue about the dependencies of a to be micro-service on the another. How do we cater that? Interfaces

Languages that offers interfaces can truly experience the beauty of what I’ve discovered. I’m go developer and go embraces the concept of interfaces. We implement interfaces such that between each model there is a defined interface for each relation such that one can only interact through the interface only.

I’ll be writing more on this as I uncover the concept of better software design for powered MVC. Till then, Peace be unto you.