Hi, Diogo.
If your aim is to separate the models from the controllers, views, etc.,
then Cake can handle that. I haven't tried this yet, but I was looking at
the possibility of splitting off the back-end functions of my app to a
separate app on a sub-domain. From there I can either link to
Hello Diogo,
So, it seems to me that you need to create a Service Oriented Architecture
(SOA) in order to facilitate seamless communication for these three
different
modules (User and Permission management, Projects, and Financing) kind of
like what Amazon did and I would also be looking into
Hello
In my company, we develop software with cakephp for internal usage. The
software is getting big for managing it as a single project (46
controllers, 94 models), and we've been thinking about splitting it in two
or three different software, each to manage one different domain of the big
I might suggest usage of plugins, and perhaps composer.
I'm not sure if you're talking about physical domains, when it comes to the
split (as in there's one URL for users and permissions, another for
projects and another for financing). Lets assume you do, and address the
alternative later
