How would one architect an app so that you can test the core functionality without worrying about the templating noise?
My guess would be to separate your ‘web’ (routing etc) service from your ‘api’? If that’s correct, what’s a recommended way of doing so?
Sorry I know this is broad and it probably depends, so if it helps, a bit of context:
I’ve been working in Phoenix for the last 2 years and am really enjoying it so far. Having said that, I don’t have much other experience building web-apps so my conceptual thinking & confidence are probably below where they should be.
Over the last 2 years I’ve built a monolith application that is entirely SSR relying heavily on phoenix (postgres/redis). I’m starting to run into some problems due to some poor implementations, poor design decisions and changing requirements. Therefore I’m looking at how we could change things if we were to rebuild.