I'm part of a team that develops a front-end Web application that relies on many back-end services. Historically, these services were written in different languages and run on different platforms.
Previously, we had a standalone version of our application in which we replaced the real requests to the back-end by the predefined simulations. It was useful because we could develop the front of our application in isolation, without counting on the availability of deliverables from other teams and their logic.
It was expensive to keep the dummy data in parallel with the logic of the real services, and the standalone version was out of sync. We are now developing with the help of a web debug proxy that rewrites some of the requests to a transfer environment to locally built assets, and the overall solution seems fragile and inflexible. We still need to maintain the proxy configuration, and there are also other places where this could break.
Even if we imagine that we have a backend for the frontend of some sort, we still have the problem of fictitious data out of sync, but pushed to a lower level.
Ideally, I do not want to be dependent on the environment with all the services deployed, and I want to be able to decouple the parts of our application. Maybe there are obvious solutions to the problem, or literature that I missed?