BrianT
AEAsh Elixir
•Created by BrianT on 6/18/2023 in #support
Is Ash well suited to Domain Driven Design
Hi everyone. First up, I'm new to Elixir and Ash and expect a steepish though enjoyable learning curve. 🤞 (I have lots of experience in other languages: Java, Go, Python, C#, VB :D, SQL etc.)
I'm redesigning a complex solution that has ~8 "micro" services (mostly Go and Java), uses Drools (with dynamic code generation) for complex business rules, Apache Pulsar for messaging, Postgres databases, Angular SPA...
In fact, it's TOO complex and unmanageable for a very small team, (1-2 ppl) and for various reasons the solution was never completed and released!
I've been following DDD principles and have a good handle on the domains, actors, bounded contexts, messages/events etc.
During my Elixir research I came across Ash and thought it might be a good fit for my current problem domain and team size of 2.
In the Ash Get Started tutorial there is a quote
"It might be helpful to think of an Ash API as a Bounded Context (in the Domain Driven Design sense)"
Does this indicate that Ash is particularly well suited to solutions following DDD patterns? If so, does anyone have any pointers on material I can read to help? Many thanks guys, in advance. 🙂9 replies