8 ms·
Very nice discussion and slides, the videos added a lot. My favorite approach is somewhat in the middle. You might call it an "MSPA" - Multiple Single Page App
by eranation 13y ago
Very nice discussion and slides, the videos added a lot.
My favorite approach is somewhat in the middle. You might call it an "MSPA" - Multiple Single Page Apps, each major section in the app is it's own standalone SPA. (public searchable pages are plain HTML e.g. using Jekyll).
For example, if I have an admin section with master detail scenario, this would consist of a single SPA, And an "account" section with settings + and profile sections will be also it's own SPA. I only keep it "SPA" where it makes sense to keep the same context, and where there are frequent transitions between section's pages.
p.s. I like your stack (Backbone, Django, Play). my specific stack of choice is not that far though I eventually moved from backbone to AngularJS and never looked back. With Scala I use it just as Servlets / JAX-RS on steroids instead of Play, I found performance to be better.
- AdrianRossouw 13y agoi like this approach a lot too. it takes a fair amount of discipline to do properly though. ideally you want to be able to, on some level, iterate on different apps at different rates, and also share apps between various different stacks.
- pamelafox 13y ago(Post author) Good point, we actually do take that approach - we have about 8 different Backbone apps currently, for different aspects of the admin and student experience. We don't have a hard and fast rule for when we break into a new app, but it usually becomes obvious at some point. And it's not too hard to refactor that sort of thing, since it's mostly just changing a routes file around.