Domain Driven Design with Scala

Table of contents
Reading Time: < 1 minute

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.

Part One

Part Two

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.


Written by 

Vikas is the CEO and Co-Founder of Knoldus Inc. Knoldus does niche Reactive and Big Data product development on Scala, Spark, and Functional Java. Knoldus has a strong focus on software craftsmanship which ensures high-quality software development. It partners with the best in the industry like Lightbend (Scala Ecosystem), Databricks (Spark Ecosystem), Confluent (Kafka) and Datastax (Cassandra). Vikas has been working in the cutting edge tech industry for 20+ years. He was an ardent fan of Java with multiple high load enterprise systems to boast of till he met Scala. His current passions include utilizing the power of Scala, Akka and Play to make Reactive and Big Data systems for niche startups and enterprises who would like to change the way software is developed. To know more, send a mail to or visit

2 thoughts on “Domain Driven Design with Scala1 min read

Comments are closed.