Too Long; Didn't Read
Couple of months back, I was listening to Eric Evan’s pod cast on Software <a href="https://hackernoon.com/tagged/engineering" target="_blank">engineering</a> radio where he mentioned that actor model is a great fit for modeling aggregate root in domain driven <a href="https://hackernoon.com/tagged/design" target="_blank">design</a>, I was like what, wait? ain’t OO languages the only way to model concepts like aggregate, sagas, domain service, repositories or bounded Contexts in Domain driven design ?