|
| 1 | +--- |
| 2 | +title: "Monolithic Ecommerce App: A Cohesive Application Model" |
| 3 | +shortTitle: Monolithic Ecommerce |
| 4 | +description: "Explore the Monolithic Ecommerce application structure, its design intent, benefits, limitations, and real-world applications. Understand its simplicity and practical use cases." |
| 5 | +category: Architectural |
| 6 | +language: en |
| 7 | +tag: |
| 8 | + - Cohesion |
| 9 | + - Simplicity |
| 10 | + - Scalability |
| 11 | + - Deployment |
| 12 | + - Maintainability |
| 13 | +--- |
| 14 | + |
| 15 | +## Monolithic-Ecommerce App |
| 16 | +* A Monolithic Ecommerce example to showcase Monolithic Architecture |
| 17 | + |
| 18 | +## The Intent of Monolithic Design pattern |
| 19 | +> the Monolithic Design Pattern structures an application as a single, cohesive unit where all components—such as business logic, user interface, and data access are tightly integrated and operate as part of a single executable. |
| 20 | +
|
| 21 | +## Detailed Explanation of the Monolithic Architecture |
| 22 | +Real-world Example |
| 23 | +> A traditional E-commerce website is the most straightforward example for a monolithic application as it is comprised of a catalogue of products, orders to be made, shopping carts, and payment processes that are all inseperable of each other. |
| 24 | +
|
| 25 | +In Plain words |
| 26 | +>The monolithic design pattern structures an application as a single unified unit, where all components are tightly coupled and run within a single process. |
| 27 | +
|
| 28 | +GeeksforGeeks states |
| 29 | +> Monolithic architecture, a traditional approach in system design, which contains all application components into a single codebase. This unified structure simplifies development and deployment processes, offering ease of management and tight integration. However, because of its rigidity, it is difficult to scale and maintain, which makes it difficult to adjust to changing needs. |
| 30 | +
|
| 31 | +Why use MVC for a Monolithic Application ? |
| 32 | +>The Model-View-Controller (MVC) pattern is not inherently tied to microservices or distributed systems. It's a software design pattern that organizes the codebase by separating concerns into three distinct layers: |
| 33 | +>* Model |
| 34 | +>* View |
| 35 | +>* Controller |
| 36 | +> |
| 37 | +> this also helps maintain the principles of a Monolithic Architecture which are: |
| 38 | +> |
| 39 | +> Simple to |
| 40 | +>* Develop |
| 41 | +>* Test |
| 42 | +>* Deploy |
| 43 | +>* Scale |
| 44 | +> |
| 45 | +## We can clearly see that this is a Monolithic application through the main class |
| 46 | +This is a simplified version of the main application that shows the main interaction point with the CLI and how a user is registered |
| 47 | +```java |
| 48 | +@SpringBootApplication |
| 49 | +public class EcommerceApp implements CommandLineRunner { |
| 50 | + |
| 51 | + private static final Logger log = LogManager.getLogger(EcommerceApp.class); |
| 52 | + private final UserCon userService; |
| 53 | + private final ProductCon productService; |
| 54 | + private final OrderCon orderService; |
| 55 | + public EcommerceApp(UserCon userService, ProductCon productService, OrderCon orderService) { |
| 56 | + this.userService = userService; |
| 57 | + this.productService = productService; |
| 58 | + this.orderService = orderService; |
| 59 | + } |
| 60 | + public static void main(String... args) { |
| 61 | + SpringApplication.run(EcommerceApp.class, args); |
| 62 | + } |
| 63 | + @Override |
| 64 | + public void run(String... args) { |
| 65 | + Scanner scanner = new Scanner(System.in, StandardCharsets.UTF_8); |
| 66 | + |
| 67 | + log.info("Welcome to the Monolithic E-commerce CLI!"); |
| 68 | + while (true) { |
| 69 | + log.info("\nChoose an option:"); |
| 70 | + log.info("1. Register User"); |
| 71 | + log.info("2. Add Product"); |
| 72 | + log.info("3. Place Order"); |
| 73 | + log.info("4. Exit"); |
| 74 | + log.info("Enter your choice: "); |
| 75 | + |
| 76 | + int userInput = scanner.nextInt(); |
| 77 | + scanner.nextLine(); |
| 78 | + |
| 79 | + switch (userInput) { |
| 80 | + case 1 -> registerUser(scanner); |
| 81 | + case 2 -> addProduct(scanner); |
| 82 | + case 3 -> placeOrder(scanner); |
| 83 | + case 4 -> { |
| 84 | + log.info("Exiting the application. Goodbye!"); |
| 85 | + return; |
| 86 | + } |
| 87 | + default -> log.info("Invalid choice! Please try again."); |
| 88 | + } |
| 89 | + } |
| 90 | + } |
| 91 | + protected void registerUser(Scanner scanner) { |
| 92 | + log.info("Enter user details:"); |
| 93 | + log.info("Name: "); |
| 94 | + String name = scanner.nextLine(); |
| 95 | + log.info("Email: "); |
| 96 | + String email = scanner.nextLine(); |
| 97 | + log.info("Password: "); |
| 98 | + String password = scanner.nextLine(); |
| 99 | + |
| 100 | + User user = new User(null, name, email, password); |
| 101 | + userService.registerUser(user); |
| 102 | + log.info("User registered successfully!"); |
| 103 | + } |
| 104 | + |
| 105 | +} |
| 106 | +``` |
| 107 | +### We can clearly reach the conclusion that all of these classes reside under the same module and are essential for each other's functionality, this is supported by the presence of all relevant classes as parts of the main application class. |
| 108 | + |
| 109 | +## When should you resort to a Monolithic Architecture ? |
| 110 | +>* An enterprise Starting off with a relatively small team |
| 111 | +>* Simplicity is the most important factor of the project |
| 112 | +>* Maintaining less entry points to the system is cruical |
| 113 | +>* Prototyping ideas |
| 114 | +> |
| 115 | +## Pros & Cons of using Monolithic Architecture |
| 116 | +>### Pros: |
| 117 | +>* Simple Development: Easy to develop and deploy. |
| 118 | +>* Unified Codebase: All code in one place, simplifying debugging. |
| 119 | +>* Better Performance: No inter-service communication overhead. |
| 120 | +>* Lower Costs: Minimal infrastructure and tooling requirements. |
| 121 | +>* Ease of Testing: Single application makes end-to-end testing straightforward. |
| 122 | +> * This is also assisted by the MVC structure employed in this example. |
| 123 | +>### Cons: |
| 124 | +>* Scalability Issues: Cannot scale individual components. |
| 125 | +>* Tight Coupling: Changes in one area may impact the whole system. |
| 126 | +>* Deployment Risks: A single failure can crash the entire application. |
| 127 | +>* Complex Maintenance: Harder to manage as the codebase grows. |
| 128 | +>* Limited Flexibility: Difficult to adopt new technologies for specific parts. |
| 129 | +
|
| 130 | +## Real-World Applications of Monolithic architecture Pattern in Java |
| 131 | +>* E-Commerce Platforms |
| 132 | +>* Content Management Systems (CMS) |
| 133 | +>* Banking and Financial Systems |
| 134 | +>* Enterprise Resource Planning (ERP) Systems |
| 135 | +>* Retail Point of Sale (POS) Systems |
| 136 | +
|
| 137 | +## References |
| 138 | +>* [GeeksforGeeks](https://www.geeksforgeeks.org/monolithic-architecture-system-design/) |
| 139 | +>* [Wikipedia](https://en.wikipedia.org/wiki/Monolithic_application) |
| 140 | +>* [vFunction](https://vfunction.com/blog/what-is-monolithic-application/#:~:text=A%20traditional%20e%2Dcommerce%20platform,inseparable%20components%20of%20the%20system.) Blog post |
| 141 | +>* [Microservices.io](https://microservices.io/patterns/monolithic.html) |
| 142 | +>* [IBM](https://www.ibm.com/think/topics/monolithic-architecture) |
| 143 | +>#### References used to create the code |
| 144 | +>* [Mockito](https://site.mockito.org/) -Testing |
| 145 | +>* [Junit](https://junit.org/junit5/docs/current/user-guide/) -Testing |
| 146 | +>* [Springboot](https://docs.spring.io/spring-boot/index.html) -Web Application Initiation (implemented but not utilized in this example) |
| 147 | +>* [Sprint Data Jpa](https://docs.spring.io/spring-data/jpa/reference/index.html) -Database connection |
| 148 | +>* [Lombok](https://projectlombok.org/) -Simplifying Classes |
| 149 | +>* [Log4j](https://logging.apache.org/log4j/2.x/index.html) -Capturing Logs |
| 150 | +>* [H2 Databse](https://www.h2database.com/html/tutorial.html) -Efficient, Simple, Dynamic Databse |
0 commit comments