MVC：一种模式，多种应用

Question

I am starting a project based on multiple webapplications (Website, ControlPanel, RestAPI) each based on the same Data[bases] and an MVC framework.

To avoid parallel code maintenance I thought of having the same model-files for each app. But when thinking deeper all possible approaches have some pro's and con's. I thought I'd ask some experts.

Possible ways to go (I know of) :

---

1. Plugin ~one4all

The very core of logic encapsuled as a plugin which is deployed in each app.

++ Only one model per table for all apps

-- One bug can crash 4 apps

-- lots of unused code per app

---

2. Duplicated code ~all4one

Double maintenance of duplicated model files.

++ Bugs affect only one app

++ Models does not contain unused code

-- Inefficient development

---

3. Api between apps ~lonewolves

Apps get its data from an api.

++ one code serves all apps

-- uncommon approach

-- massive overhead

---

4. Models symlinked ~lazy1

One application holds the model files, the other apps will symlink/include it.

++ almost no extra work to do

+- seems hilarious

-- one bug affects all apps

-- could restrict debugging

---

Are there more possible approaches? Which one is common/recommended? I don't want to combine the functionality of all apps into one to avoid crashing the whole thing with one pull.

More approaches and ideas are very welcome. Thank you in advance.

Answer 1

Implement SOLID in proyect. Valid all framework.

Answer 2

One option you missed is to keep the projects as one. Instead of splitting the model, and thus maintaining it across three or more separate projects, you could make only one project, and just divide the portions with controllers. Although this method can create a monster of a project, it can also be kept in one place, and many controllers can divide the project down into easily managed pieces.

If it were me, and I wanted to keep the projects as separate cakephp projects, I would probably end up duplicating code. It's not that bad to copy and paste. That's what I do on a website that I work on, in order to separate testing and production.

Although, I would also probably try including separate files, which contain the same code. Even though you are using cakephp, you can also use php code. What if you require() files that contain cakephp logic. Not sure if this works, but I would at least give it a try.