Why is software architecture so important? What is it, anyway? How can "clean" software architecture actually make software development easier, faster, and less-painful?
"Uncle" Bob Martin has attempted to take the most robust and battle-tested architectural patterns and boil them down into "one architecture to rule them all"--in a matter of speaking...
We'll briefly look at what "Clean Architecture" is and what problems it attempts to solve. Then we'll focus on how we might implement it in a .NET Core application with practical tips from real-world experience sprinkled throughout.
James Hickey is currently the senior software developer at IronFlow Technologies. He focuses on improving software development processes, automation and architecture. His current technical interests include .NET Core, Event Sourcing, Microservices, etc.