20 Jan 2020
No architecture deep dive
- Part 1 - Introduction
- Part 2 - Getting Started
- Part 3 - Creating a basic design
- Part 4 - Upgrade to .NET Core 3.1
- Part 5 - Database test
- Part 6 - Create the database
- Part 7 - This Article
- Part 8 - First API mockup
- Part 9 - A new start
- Part 10 - Create the database scripts
- Part 11 - Create the group controller and service
- Part 12 - Running SQL Server in Docker
- Part 13 - Being able to use two database engines
In my last post I wrote that I wanted to start writing a API endpoint. But that was a bit premature, at the time.
I first had to investigate about stuff like Domain Driven Design, Test Driven Design and Clean Architecture. To put it mildly my knowledge of these architectures and best practices is a bit rusty.
Over the last period I watched a couple of YouTube clips and read various articles about those subjects. Turns out it is quite a journey to learn these topics, and not necessarily that useful for this project. Domain Driven Design is recommended for complex systems, but I don’t consider the website I am going to build complex. I definitely need to learn more about these things, but I’m not gonna combine that with this project. I don’t want to dive too deep. The basics of a Web API and an Angular frontend will keep me busy for the coming period.