Advice on Phoenix Project Architecture for Divided Applications

142
clicks
Advice on Phoenix Project Architecture for Divided Applications
debarchito is working on a Phoenix project split into three main applications: API Server, Vendor Dashboards, and a web-based Customer Ordering App. They need to ensure synchronized sessions across vendors and customers using a room model for communication, involving Phoenix Channels and Pub/Sub. They are seeking advice on using an umbrella project, defining channels and Pub/Sub, and whether to use LiveView or a JavaScript framework like Svelte/SvelteKit for the front-end.

© HashMerge 2024