[FX.php List] Are there any FMCakeMix war stories?

[Tim 'Webko' Booth]

Dear Malcolm,
>
> The clients existing applications are all Filemaker, so it is easier  
> to keep all the slop in one bucket. We have several successful sites  
> using the official php api and more recently, FX.  These sites  
> attract low traffic. The new project may generate significant traffic.
>
> Any stories, experience or suggestions for mid-sized web apps with  
> fmp back ends?

IMO, it doesn't really matter how the php code is generated / looked  
after - the bottleneck is the single-threaded (and 'wordy') nature of  
either the XML interface or the PHP API.

Put simply, even small requests will bog down if there are a lot of  
them. Or if there aren't that many, but there are some large ones  
thrown in.

They all try to fir through the same pipe into the database, one after  
the other. All well and good if the pipe doesn't get too full, but an  
issue thereafter.

I wrote something about this a little while back:

"Some real world examples:
System A is an online registration system including payments for a  
University - it handles about 1,000 requests a day and performs  
flawlessly using FX.

System B is an online academic paper search tool - it handles up to  
1,000 simple requests an hour at peak and performs flawlessly using  
FX. It is a very simple though - flat file effectively.

System C is an online survey tool that can make up to 100 requests in  
a single page load, either creating  or editing records using FX. The  
admin section can make up to 400 requests in a single page load. This  
one works, but struggles every now and again under the load. I would  
probably do this one in mySQL if I'd known what was involved when we  
started.

System D is an online registration tool for a University that has  
specific registration dates for some *very* popular programs. It has a  
reasonable amount of complexity, as it is for academic programs and  
there are a lot of business rules. For about 360 days of the year, FX  
and FileMaker could handle the load without any issue. Those other 5  
days, however, see up to 10,000 requests an hour - needless to say, it  
is built on a mySQL backend and the users in the office use FileMaker  
to see that data via ESS.

So, you need to examine how complex your queries are, how often they  
occur, and how much data will be passed in order to determine which  
tool is the best to use."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20120313/2b5c754c/attachment.html