I don't know, whether spread out over several installations or in one (or
several) installations utilizing plugins, the various components are going
to need to talk to each other and share data anyway...
Developing in separate applications is the ultimate in separation of code, I
suppose, but
#1 Share nothing architecture
:-)
Tarique
On Sun, Aug 28, 2011 at 7:17 PM, Ben McClure wrote:
> Certainly a valid approach, but why do you need the overhead of multiple
> applications when you could simply have one application with several
> plugins?
--
===
Certainly a valid approach, but why do you need the overhead of multiple
applications when you could simply have one application with several
plugins?
The plugin concept also allows you to run it in as many different apps as
you'd like, but doesn't require that they remain as separate applicati
I would still like to stick with my original stance of splitting the
code into applications rather than plugins irrespective of whatever
caching solution you use. Varnish is a good choice.
Cheers
Tarique
On Sun, Aug 28, 2011 at 2:48 AM, Ben McClure wrote:
> I would agree that splitting the code
I would agree that splitting the code into plugins would make the most sense
as far as extensibility goes--each developer you outsource to gets the code
for the plugin(s) they are working on, and they shouldn't need anything
else.
For scalability regarding the number of users you can support an
Splitting the code got nothing to do with application scalability.
As you mentioned split the code to plug-ins and make some of them open
source to gain community contribution.
Then scale the application with common solutions like clusters, database
replications etc.
On Thu, Aug 25, 2011 at 8:30
Varnish Cache server may be a good solution for this; in ways potentially. I
haven't tried this yet.
http://goo.gl/NYpPY
On Sat, Aug 27, 2011 at 12:14 AM, Dr. Tarique Sani wrote:
> I would split out the app into mini apps which share sessions(if needed)
>
> to start with I would split
>
> User p
I would split out the app into mini apps which share sessions(if needed)
to start with I would split
User portfolio (users can be spread across as many servers as you want
because they do not share anything with others)
User Admin area (this is where they upload photos etc)
Super Admin
Also I
Hi everybody,
we have a photo selling/sharing web project. Our customers get a
personal portfolio page and can sell their photography.
Because of an increasing amount of users, we are planning to add some
more web servers.
Right now we have one big cake application with the tasks split into
diffe
