Last weekend, I was thinking about managing my finances in terms of total expenses per month and some sort of reporting for analysis so that I can monitor and make some decisions. I started looking for online available apps which can do this for me. Before coming to the main discussion, let me tell you, as a software engineer, this happens with me every time, as soon as a software is needed, the very next thought that comes to my mind is, why not let's create one? If I were the creator, I know the problem, I can develop as per my needs, and have complete control.
With over 13 years of industry experience, I have come to realize that as your career progresses, it's the discussions and communication around a problem that truly matter. These interactions become a powerful source of learning and critical thinking. While writing code is very important for implementing solutions, the real growth often comes from how we explore and understand problems together. I believe you’ll come to appreciate that over time as well. Now, let’s return to the main topic. Up to this point, I had decided to develop an ASP.NET Core web application using .NET 9. The next crucial decision was choosing an architecture that allows building features in isolation, as self-contained modules, without needing to redeploy the entire application every time. Take a moment to pause and reflect on the title of this post: Dynamic Modular Monolith."
That was all for this introductory post about my Dynamic Modular Monolith Architecture-based ASP.NET Core app, this is a series of posts, i.e., ASP.NET Core app with Dynamic Modular Monolith Architecture, which I thought I should share with the wider audience as well.
Top comments (0)