I just wanted to add that the way Ash does this isn’t too different than how you might say Phoenix’s context are “supposed” (very heavy quotes) to be used, it just abstracts a lot away (with many additional benefits, of course). Ash resources bundled in an Ash domain exposed by an Ash code interface is very generally the idea behind the DDD concept of Bounded Contexts which is where Phoenix contexts get their name. If you aren’t already familiar, reading up on them can help a lot in vanilla Phoenix and Ash (especially if you get a job where you have to use vanilla Phoenix). A very short intro is available here.
I’m just finally getting into Ash myself and can already tell I will not be looking back—except for every day at work when I’m forced to 
So ya, I have nothing to add to what @barnabasJ has said other than to reinforce that the target audience of Ash is everyone 
And welcome to the forum!
