Applying DDD To Architect a Digital Bank Part 1: Analyzing domain using Subdomains

I have started work on a new project where we are architecting and building a new digital retail bank from scratch. To architect a bank from scratch is a huge undertaking. There are many systems and partners involved. I have only started working in the banking domain from the last one year and I can surely say the banking domain is full of interesting technical challenges. Both incumbent and challenger banks are building systems using cloud native architecture and technologies. It is an interesting time to be working in the BFSI and FinTech space. Digital banks open up a possibility of making banking possible and accessible to millions of people across the world.

Shameless plug: I am hiring. If you are a software engineer or an architect looking for interesting technical work then contact me using the contact form.

DDD stands for Domain-driven design. This term was coined and popularized by Eric Evans when he wrote the seminal DDD blue book[1] in 2003. I read the blue book 5 years back. It made me understand why it is important to have a good understanding of the domain when building complex software. At that time I couldn’t relate much with the strategic design patterns talked about in the DDD book. These strategic patterns felt very meta to me and I failed to apply them. A month back I read the Learning Domain Driven Design book[2] by Vlad Khononov that helped me finally understand(at least I think so) DDD strategic patterns.

Continue reading “Applying DDD To Architect a Digital Bank Part 1: Analyzing domain using Subdomains”