I have an application that is growing a lot, and it’s becoming very difficult to manage everything on the same backend framework (Symfony). I was considering separating concerns, so have two different backend architectures connected to the same database.
We are adding a new "product" to the line up, but it interacts a bit with the rest of our main applications. So basically, one will be kept as the main system but we would add the other one as a REST API. The main backend system would sometimes call the other one thought HTTP requests when wanting to interact with it.
The question is, is it a good idea? Or are there other alternatives? I imagine big companies have multiple backend projects and they all interact with each other, right?
Thanks a million,
Source: Symfony Questions
Was this helpful?
0 / 0