Re: DDD on DSL Platform
Tom Eugelink <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <[email protected]> |
Interesting and confusing. I'm not sure I agree with the definition of aggregate that is being used. Aggregate roots have to do with transactional boundaries, and may or may not consist of multiple entities and value objects. The DSL-platform however describes them as "containers for entities and value objects" and "aggregate root = view starting from an entity". Aggregates are not views. What is interesting and confusing is that I'm not sure about the value of the DSL. I mean, it is readable, yes, but where does the logic go? What I'm seeing being generated are anemic models. Also, code generation usually results in some kind of worst-of-all-worlds solutions, and prevents the flexibility and limits the options that using a specific programming language has. Code generation usually only works on simple (CRUD) applications, on more complex systems it at best can only help by generate scaffolding. My compliments on the effort, but right now I'm not intrigued. Tom On 2013-07-17 11:39, Rikard Pavelic wrote: > Hi everyone! > > Recently we've opened a free beta of our Invasive software composition platform based on DDD. We would appreciate any feedback and constructive criticism ;) > > In short it's a way to describe you domain models in DSL based on DDD building blocks. From that formal specification our compilers will migrate a Postgres/Oracle database and prepare server and client libraries in supported languages. > > You can take a look at it on https://learn.dsl-platform.com using our try-it-online sandbox. > Currently there are only small examples there, but we plan on adding more complex apps in time. > > We are currently open sourcing (on Github) our client and server libraries. > > Since a lot of libraries (code) are maintained by the compiler there were a few DDD design (sic.) issues and we will gladly discuss them here. > > Regards, > Rikard >