I just came across this post and I have a similar problem.
Let's say we have a web app that has 2 components :
My question is how do you run this setup locally and in production? If I separate socket servers from web servers, I have to maintain a different repo and deploy code from that repo to a VM. And also l have to run a separate socket server locally. Isn't it counter productive? How would you architect such a system?
Looking forward to some suggestions! :)
Marco Romero
Front-end Engineer
I know the pain of having to install and configure almost the complete system in your local machine to be able to test e2e and develop just 1 part of it. I'm still looking for a pragmatic solution to this problem.
What I have done in the past is to use mocking libraries to intercept and replace responses to third party services(Databse, Rest, WebSockets)in order to keep development isolated and prevent the "it works on my machine" syndrome. The downside of this is that, initially, it will take time to create al the mocked responses, and secondly, you will need to maintain the mocks as the thirdparty API's change.
Another alternative is to have a dedicated development server where all clients connect.