We have a heritage app that does two things: Provide dynamic content and do transactions with registered users, all one The same domain from thedomain.com .
We want to update / change the CMS (the part of the legacy server that works on dynamic content), but keep the existing server for the Transactional Part. And we want to serve it to everyone from the same domain.
So if we have today thedomain.com/cms/page1.html and thedomain.com/business/ Step1 coming from the same server, In the future, we want them to come from different servers (kept in various data centers and operated by different providers).
What's the best way to set this up? It should use a reverse proxy, yes? But it is best that how to set it up and how? Is the reverse proxy closer to the legacy server or "new", or is this all right? Are there specific warnings regarding the session sharing in setting up a reverse proxy for this usage?
Your proxy server should contain more traffic, so the biggest part of the data is through 2 servers Do not go by, but why do not you use a subdomain, for example example.msample.com/ instead of example.msample.com/?
Comments
Post a Comment