Support the ongoing development of Laravel.io →
Laravel Architecture Eloquent
Last updated 2 years ago.
0

Why do you need two applications? In my opinion, you only have 1 application, namely the REST api.

The backoffice client as you refer to, can then consume the REST api. I am very much against two seperate applications talking to the same database; for me 1 database = 1 application, which is responsible for maintaining the data integrity, and should validate all permissions and restrictions.

If you create two completely seperate applications, which one is responsible for what? It makes no sense to me.

0

I agree with you. I will propose this change.

0

Yes, in practice you choose one repository to do your migrations.

We've more than 3 code repositories accessing the same database; only one has the proper migration information (the others usually have shallow copies or similar for unit test).

0

Sign in to participate in this thread!

Eventy

Your banner here too?

FELPONE felpone Joined 2 Jun 2017

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.