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

I prefer the separation. Simplifies a lot of things. unless of course they more or less handle the same data, in which case combined would be better/faster to develop.

Wont the isolation be broken when upgrading one service, forces you to upgrade the dashboard because of the database integration?

If you don't mind making a API for each service you could use a ReST-ish implementation to manage the data transferal and manipulation from dashboard to service.

0

Hi Jess, Upgrading one part won't break the other as long I will create a REST api. That would be the beauty of it. So right now I have one vote for te separation with REST API communication.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

stefro stefro Joined 9 Feb 2015

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.