After coming across a question on Stack Overflow that was similar to mine, I realized I have a lot to learn about Object-Oriented Programming (OOP). Up until now, my coding experience has been mainly procedural. Before diving into my question, let me provide some context by sharing the technology stack I am working with:
Server: Debian Linux
Server-Side-Language: NodeJS with the Express Framework
DB: Firebase (indirectly connected to MongoDB).
Due to utilizing Backend as a Service (BAAS), our NodeJS server simply serves files without any template engine installed. The front end is built with Angular, creating a real-time Single Page Application (SPA) using Angular routing.
My curiosity lies in how to implement OOP within an MVC framework lacking explicit support for classes and instances. According to the insights from the linked question, Angular factories can serve as pseudo classes in this scenario.
In my understanding, each Angular module acts as a comprehensive object housing its own MVC architecture. The query remains: what should be the ideal thickness of controllers?
Contrastingly, Ruby On Rails advocates for fat models and thin controllers approach. In translating this philosophy, here's the outline I contemplate:
1) Develop a model integrated with factories emulating classes.
2) Write controllers responsible for handling these factory instances, executing methods, and preparing data for the view.
3) Design a view exhibiting data curated by controllers through bidirectional data binding.
Yet, the challenge arises when prominent advice emphasizes keeping controllers lean. As a newcomer to OOP and MVC methodologies, I acknowledge potential errors in applying these principles correctly.
Is my current strategy aligned with both OOP and MVC guidelines? If not, where do you perceive misconceptions and what adjustments are necessary for optimizing these concepts in my project?