News for hackers. Stuff that matters.

Combine clean architecture with entity-component-system

My idea is to separate my code into data, domain, and presentation layers and use entity-component-system only in presentation layer. So data and domain layers will follow DDD principles and will mostly deal with reading/writing data. And in presentation layer, the domain models will be converted to components and systems.

Did anyone try it? Looking for opinions/tips/examples.

( 1 comment | on HN )
Re:Combine clean architecture with entity-component-system by daleholborow on Monday May 18, 2020 @11:27AM (#23223543)
What's the system? Do the absolute bare minimum required for success, and if you don't need the additional overhead, avoid it. Find Jimmy bogard on vertical slice architecture in YouTube for some good talk on pragmatic , simple designs winning over theoretically sound but heavy and unnecessary architectures, well worth a look