Design Microservices Architecture with Patterns and Principles - Problem: Agility of New Features, Split Agile Teams-1

The video discusses the challenges faced with the current clean architecture, particularly in terms of agility and team splitting as the ecommerce business grows. It highlights the issues of context switching and vertical slices, which complicate feature development across multiple layers. The proposed solution is to adopt a modular monotic architecture to better manage the codebase and accommodate new features efficiently.

What is the main problem identified with the current architecture?

• Poor user interface

• Difficulty in adding new features

• Lack of scalability

• High maintenance cost

How are the business teams organized in the e-commerce company?

• By department

• By product type

• By project size

• By geographical location

What issue arises when adding or changing features in the current architecture?

• It causes server downtime

• It leads to data loss

• It requires changes in almost all layers of the application

• It increases the cost of development

What is the proposed solution to the problem with the current architecture?

• Microservices architecture

• Event-driven architecture

• Layered architecture

• Modular monolithic architecture

What benefit does the modular monolithic architecture provide?

• Improved scalability

• Easier management of codebase

• Better user experience

• Reduced server costs