3 ms·
Simple is a changing target. In a one person team merging your server with your client and using HTMX can be simpler (depending on if the value is in your UX o
by bnchrch 3y ago
Simple is a changing target.
In a one person team merging your server with your client and using HTMX can be simpler (depending on if the value is in your UX or in your logic/data).
However as the team gets larger then I find having a clear separation between your API(s) and your Client(s) is much more simple and maintainable. Also it can unblock product decisions like offline mode or PWA's.
Finally its worth stating that being in an SPA community like React can give you access to "economies of scale" in terms of the libraries available to save you time (Tables, animations, UI kits, Video players, etc.) allowing you to do more with less people.
- brtkdotse 3y ago> clear separation between your API(s) and your Client(s) The problem is that the SPA way of thinking has infiltrated every nook and cranny in this industry. The ratio of APIs vs clients consuming those APIs come scarily close to 1, at least with the customers I work with. Now you have to maintain two projects, two CI/CD pipelines, two hosting solutions, potentially two sets of languages and tooling…
- Danjoe4 3y agoYes. You should probably start with a monolith. If you really scale then toss the htmx FE, expose an API, and slap a react project on top. Django lends itself to this growth pattern very well.