Blog Archives

Building Domain Driven Architecture in .NET – Part 3 (Repository Design)

In part 2, I talked about my domain modeling thought process so this post is about trying to persist those objects for long term storage. Although the avenue for different data storage provider is always open with the kind of

Tagged with: , , , , , , , , , , , , , , , ,
Posted in API, architecture, design, best practices, domain driven design, refactoring, software architecture, SOLID, SOLID principles, Uncategorized

Building Domain Driven Architecture in .NET – Part 5 (ASP.NET Core App)

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

Tagged with: , , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in API, architecture, design, ASP.NET Core, domain driven design, Microsoft Azure, refactoring, software architecture, SOLID principles, Uncategorized

Building Domain Driven Architecture in .NET – Part 1 (Overview)

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.

Tagged with: , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in architecture, design, domain driven design, refactoring, software architecture, SOLID principles, Uncategorized

Implementing Generic Repositories in Quasi-DDD Applications

Over the last several weeks I have been working to build a basic re-usable CRUD type repository interface useful for anemic CRUD domain models but that allows for extensions that can potentially be used with richer domain models like the

Tagged with: , , , , , , , , , , , , , , , , , , , ,
Posted in API, architecture, design, ASP.NET Core, best practices, domain driven design, Over Engineering, refactoring, software architecture, SOLID, SOLID principles, Uncategorized

You Ain’t Gonna Need That API

Exhibit B: Simpler (& useful) design

If you are not sure who this API is going to benefit and how, chances are You Ain’t Gonna Need It

Tagged with: , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in API, architecture, design, Azure Storage SDK, Microsoft Azure, Over Engineering, refactoring, RESTful, SOLID, SOLID principles, Uncategorized

Making Legacy Code More S.O.L.I.D

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

Tagged with: , , , , , , , , , , , , , , , , , , , , , , , , , ,
Posted in architecture, design, best practices, refactoring, SOLID, SOLID principles

Generating Drive Time Polygons using Mapbox Directions API

I have been working on a project at work to build a mapping application to support the out of home advertising business which as you can imagine relies heavily on the geographical locations of assets, stores, audience etc. Its very important

Tagged with: , , , , , , , , , , , , , , , , ,
Posted in Algorithms, Geo-spatial, GIS, Mapping
Categories
Follow Artineering on WordPress.com
Links