Domain Driven Design with Scala

The benefits of DDD have been elucidated multiple times. For us, at Knoldus, we want to make sure that quality of software developed goes a long way. More than 70% of the cost of the software is spent in the maintenance of the software and hence it becomes absolutely essential that a good amount of time is spent in making the right software right. The following slide deck and video was a part of our KnolX session which is held every week on Wednesday. The Knoldus Next series of sessions is an attempt to keep the quality of deliverable’s high by introducing new Knolders to the quality practices at Knoldus and reiterate the values to existing Knolders.

[slideshare id=56263922&doc=domaindrivendesign-151218054216]

Part One

[youtube=https://www.youtube.com/watch?v=I7cIqFTylv8]

Part Two

[youtube=https://www.youtube.com/watch?v=4dvqWhPwpVA]

Ok, we cheated a little ;) It does not contain a lot of Scala but then the values of DDD are domain agnostic. We try hard to do DDD on all our products and make sure that the cost of software remains as low as possible.

While we digest all of that information, here is wishing all of you a very Merry Christmas from everyone at Knoldus.