In part 4, I detailed the way I went about creating application services for my expense tracking application. In this final post, I will talk about the ASP.NET Core MVC application that I built with HTML5/Razor front end views on top of the application services. Remember the application services consumption model sketch from the last […]
Application services can be loosely compared with the business logic layer of the yesteryear with one key difference, application services don’t actually contain any business logic neither they enforce any business logic.
In this post, I will be going over the domain modeling in a bit more detail in terms of its design and show my thought process and the decisions I made and why I made them.
Having read Vaugh Vernon’s book on DDD implementation, I decided to portgrade (port+upgrade) my old clunky Windows based N-tier desktop expense tracking application to ASP.NET Core MVC application using some of the Domain Driven Design concepts I studied in the book.
If you are not sure who this API is going to benefit and how, chances are You Ain’t Gonna Need It
Its often assumed that legacy code should not be refactored because no one knows what worms are hidden in that can and what kind of monstrous bugs will be unleashed upon the users if that code is refactored. In some cases, it does seem to hold however, done in smaller chunks to the code that […]