Many people think that microservices architectural design pattern is the answer to software complexity. For others, it’s simply a correct evolution of service-oriented architectural design. But microservices come with a price — operational complexity. Creating monolith or microservices requires a good judgement on softare architectural design. The modularity of software applies to both monolith and microservices to ensure long-term maintainability. If you can’t make a well-structured monolith app, you will probably fail to build a well-structured microservices. In this talk, you will learn how to employ the domain-driven design approach to build highly maintainable software.
Designing Software using Domain-driven Design
Published by Allan Mangune
I hold the esteemed qualification of a Certified Public Accountant and have earned a Master's degree in Science with a specialization in Computer Information Systems. Since entering the realm of software development in 2000, my focus has been on adopting secure coding practices, an endeavour I have intensified after receiving my Certified Ethical Hacker v5 certification in 2008. My professional journey includes guiding clients through their digital transformation journey, particularly emphasizing digital security issues. For more than ten years, I have provided Agile Project Management training to well-known companies. I am a Certified ScrumMaster and have completed the Prince2 Agile Foundation certification. I had the privilege of being recognized as a Microsoft MVP for ASP.NET for ten consecutive years. Previously, I also served as a Microsoft Certified Trainer. As a hobby, I enjoy assembling personal unmanned aerial vehicles during my downtime. View more posts
Allan Mangune 