Have you ever felt that the enterprise code you write is mostly procedural? Would it be possible to apply true Object-Oriented modeling techniques to your domain logic? Join this talk and learn how to write elegant code using patterns from a very mature software design style: Domain-Driven Design.

It is very common to create rich domain applications in your enterprise, but how do you handle all the code in order not to become complete chaos?

Domain-Driven Design is a very mature software development approach which helps you think more about the most important part of an application: your domain model. It also helps in getting closer to the business experts by writing expressive code.

During the last 3 years, the speakers worked on improving our Domain-Driven Design skills by developing applications using this approach.

We would like to share with you the lessons learned and the common patterns which we believe could be helpful in any rich-domain application, even if you don’t use the Domain-Driven Design approach.

🎓 What you will learn

In this webcast, the developers will learn about the following patterns:

Developers and experts interested in IT, application development and a different architectural approach.

I’m a Full Stack developer at IBM for 5 years. My main focus is developing Domain-Driven Design projects with Java and Angular, using microservices architecture. I’m also experimenting new technologies and I’m never afraid to design simple code and sense patterns.
For the last 3 years I’ve been involved in designing and developing Domain-Driven Design applications for the banking sector. It is a challenging environment and it helped in consolidating my DDD knowledge.  Countless refactorings after, me and my colleague Cristian Zamfir organized a meetup in Bucharest to share our Domain-Driven Design knowledge to fellow passionate developers. The meetup was sponsored by IBM and Incremental Community and the feedback was impressive.

I work as an application developer at IBM for almost 5 years.  I am a Domain-Driven Design practitioner, advocate of Clean Code and Test Driven Development, trying always to think in an Object-Oriented way and enriching the domain model with business meaning whenever I get the possibility. In my spare time I like to check out new technologies (especially ones related to cloud, microservices) and test new patterns and ways of coding so I can improve my programming prowess even further.  During my time at IBM I worked for more than 2 years in a full fledged Domain Driven Design Agile project. It is on this project that I learned the importance of Domain oriented model and how the Ubiquitous Language can help both business experts and application developers understand the core domain problem better and find the optimal solution for it.

Domain-Driven Design: Lessons Learned & Useful Patterns