I came across this blog post: https://iacobson.medium.com/piping-phoenix-contexts-3d54dbba8df9

I really like the idea and was wondering if anyone else in the community had thoughts and/or experience with this sort of implementation?

For context ( ) I have a Phoenix app with 10 contexts (each with variable numbers of models/schemas 2-10 each). I think the contexts are correct as it feels very intuitive and the terminology makes sense (at least for me) but I’m coming across issues where more and more features require multiple contexts to be called. Easiest example I think to understand would be the New User Onboarding requires:

Account.create_user
Organizaton.join
Analytics.track_create_user
Notifications.send_pending_membership_email
Notifications.send_admin_approval_email
+ a few more

I think this blog post describes a process that may make sense as the application grows but I’d like some feedback from people who have experience in this area.

Thank you