5 ms·
I think few reasons that made me go with this new (for me, at the time) approach were: - Backend/API that can be consumed by anything, are frontend-agnostic -
by lnxg33k1 4y ago
I think few reasons that made me go with this new (for me, at the time) approach were:
- Backend/API that can be consumed by anything, are frontend-agnostic
- Frontend that depends on JSON/source-agnostic data so that can have functionality tested faster (no "proper"/"dynamic" backend involved, just give it some ApiBlueprint/swagger mock server
- The frontend rendering isn't a concern of the backend removing some load
- Existenceblinks 4y agoBusiness-wise, I cut the JS only part as a free plan (local use only), so it's zero dollar cost. The paid plan has the Phoenix Channel integrated.