SE-Radio-Episode-261:-David-Heinemeier-Hansson-on-the-State-of-Rails,-Monoliths,-and-More

Monolithic Benefits

David Heinemeier Hansson advocates for monolithic architectures, emphasizing their simplicity and efficiency compared to microservices. He argues that monolithic systems allow developers to maintain a comprehensive understanding of the entire application, reducing complexity and potential failure points 1. David highlights that companies like Google and Facebook also utilize monolithic patterns, suggesting that this approach is intentional and not accidental 2.

Picking the monolithic pattern with pride, intention, not stumbling into it, not accidentally falling into its pits, but putting down the drawbridge and walking in with your head held high.

--- David Heinemeier Hansson

He believes that microservices often introduce unnecessary complications, especially for smaller teams, and should only be considered when absolutely necessary 2.

   

Microservices Complexity

The challenges of microservices are evident in the increased complexity they introduce to software design. David Heinemeier Hansson criticizes the trend of building sophisticated client-side applications, arguing that they often complicate matters unnecessarily 3. He suggests that many applications do not require the complexity of client-side MVC frameworks and that simpler solutions are often more effective 3.

If you take as a given that the user interface has to be this quote unquote sophisticated monstrosity, yes. Perhaps you could make the argument that it is simple to build the monstrosity this way, but you would also just say, hey, let's not build a monstrosity.

--- David Heinemeier Hansson

David also addresses the criticism of Rails' complexity, explaining that while Rails has grown, it remains efficient for solving specific use cases 4.