Thank you for the info...
any major considerations between the database options I mentioned
(mysql,postgres, amazon aws, google bigtable, etc) as it relates to
using logic on the db level?
Thank you.
On Jul 22, 2009, at 12:36 PM, Joseph Scott wrote:
On Jul 22, 2009, at 11:32 AM, CarSign wrote:
allows more logic to be performed on the DB which can reduce load
on PHP.
I'd suggest that this can be both a good thing and bad thing
depending on the needs of the project.
If the project requirements are such that it has to scale to large
number of simultaneous users and page views then this would be a bad
thing. It's much easier to spread the load at the web server/PHP
level than at the database level.
On the other side, if this app is targeted for most controlled
environments like internal business deployments, then pushing more
logic into the DB can be very helpful. You're often less concerned
about scale since you generally have an upper bound on the number of
concurrent users (number of employees). And having more logic in
the DB can make it easy for other applications to speak to the DB
without breaking things (that might be a non-issue if provide a
really good API that other apps can use).
My current job demands using the first approach, my previous job we
did apps that used the second. It varies depending on the needs,
requirements, expectations and limits of your project.
--
Joseph Scott
[email protected]
http://josephscott.org/
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
