Does it make sense to create a separate backend database to reduce the load on the primary database?

Laravel on the backend, the frontend on vue2.js
It so happened that at the present time as a backend, there are two project in Laravel, each with its own database. One project on the machine reads the data from other resources via the api and stores in its database, and the frontend just if necessary, takes a sample according to the filters.
Another beeing responsible for the program logic - user roles, offices, the creation of internal requisitions, correspondence, etc.

Now is the time to merge two project Laravel one, but the question is not whether it will a problem? The database load will increase. Because in addition to endlessly background jobs to the database will be added, requests from the client side. Can be do not join the project? Or are there weaknesses to this approach?
March 19th 20 at 08:59
1 answer
March 19th 20 at 09:01
1. Why merge?
2. Is there any connection between the two database ?
just this question - why to merge.

well, the argument to merge is. even so a single project.
but the connection between the bases yet. - Terrill67 commented on March 19th 20 at 09:04

Find more questions by tags Designing software