Re:Thinking in Actors – Challenging your software modelling ...
by ibgeek on Sunday December 01, 2024 @09:02PM
(#42292405)
It's not clear from the article whether actors offer significant benefits (or disadvantages) for data modeling versus the traditional OO paradigm. The article reads more like an introduction that describes the problem and teases a solution rather a complete article that offers a solution and evaluation of it.
Re:Thinking in Actors – Challenging your software modelling ...
by jeremycarter on Sunday December 01, 2024 @09:09PM
(#42292439)
That's fair feedback. I wanted to post it in 3 parts, but I see now I probably should have just made one large post.
What you should end up with are plain OOPy objects that mirror the real world. They're not skewed or constrained by their database model. They shouldn't have any dependencies on your infrastructure layer. The object should encapsulate state, behaviour, validity and consistency.
An example (which is probably overkill) would be https://learn.microsoft.com/en-us/dotnet/architecture/micros...
The next post is about modelling an actor and it might provide more insight for you.