mySQL: PHP or direct access?

Peter Haworth pete at lcsql.com
Fri Aug 14 14:34:38 EDT 2015


Sure, I can certainly see a networked db would be necessary in that
scenario but seems like for a simple, in-house system with a small number
of users, could be useful just because of it's simplicity.

On Fri, Aug 14, 2015 at 11:16 AM Peter TB Brett <peter.brett at livecode.com>
wrote:

> On 2015-08-14 19:31, Peter Haworth wrote:
>
> > Next decision - php or lc server.  lc server is attractive since I
> > already
> > know the language but suffers from the drawback that not many web hosts
> > support it.
>
> Yes, that's exactly the trade-off that needs to be made!  I don't think
> there's any hard and fast rule to help you decide here, I'm afraid!
>
> > Now that I'm seeing the benefits of middleware for db access, my next
> > thought is why bother with an SQL implementation that supports direct
> > network access when we're not using direct network access?  For
> > example,
> > wouldn't SQLite do just as good a job?  I've read that SQLite is used
> > for
> > many web sites supporting fairly high db access rates, maybe in the
> > range
> > of several hundred thousand a day.
>
> A common datacentre setup would involve middleware running on multiple
> front-end servers, connecting across the internal network to a database
> running on a single, dedicated, extremely high-power server.  The
> front-end servers do the caching, validation, authentication,
> encryption, etc.; the database server only manages data.
>
>                                  Peter
>
> --
> Dr Peter Brett <peter.brett at livecode.com>
> LiveCode Engine Development Team
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the Use-livecode mailing list