Budget, time, skill set, deployment hardware,...
Provide details about what your client is trying to do. Every project will have different answers to your questions. There really isn't a generic guideline like you're asking for. Each has their strengths, weaknesses and considerations that must be applied on a per-project level.
PHP has a higher development cost and longer development period, but also has higher performance in some areas and cheaper licensing. Remember with PHP you'll have to code all of the query/load/save actions with your data, and doing things like changing field names in filemaker can break PHP whereas it would not in WD.
WD has a very rapid development capability for using a FileMaker backend, and also comes with some very advanced features (eg container/file handling, record locking, layout refresh) built in that would require hundreds of hours to duplicate in PHP. There are some tradeoffs with performance depending on what the app does, and there is the concurrent seat license cost as well.
Thank you Mike,
These are some of the client's needs - this will give clearer picture
- The client has will need around 50 user access ( 30 concurrent max )
- Budget is not very high , they will have a few Filemaker Pro licenses around 3-5
- They want a moderately complex solution in 2-3 months
- Most users will be on WAN with low bandwidth 750KBps - 1Mbps Download speed
- Some users will connect to the server on institutional LAN
- Most users will be on windows 7/8
- Mobile device access is not required at present
Ouch - under the old saying:
"speed - quality - price: pick two". Seems like that they already set two of those: price and speed. That means that quality will suffer. Make sure the client is ok to budge on either budget or the timeline to make sure you can deliver something that you are happy with.
Make sure you review the tech specs for a 30-concurrent WebD load on the server:
That bandwidth on the client side is really really low, for that reason alone I would seriously consider going with a CWP solution (PHP, .NET, Ruby,...)
My recommendation is also towards CWP, but I also agree with Wim that you’ll probably need more budget to get it done in that short of a time. WebDirect systems requiring a large concurrent user count need to be developed very carefully, and I’m not sure you have the time or budget for that.
I would recommend using Soliant’s zend framework for CWP, you can build some pretty complex apps with Zend with a marginal learning curve if you already know PHP.
Thank you all for the suggestions , I am also more towards CWP .
Just want to ask one more thing . What about REST fm and the whole REST Idea is that also something that is a recommended way to build CWP ?
Sent from my iPhone
what about it? RESTfm only turns your server into a web service responder, it has nothing to do with interface or functionality. It also costs $699, which I’m sure your client wouldn’t like.
If you already has a site that is setup to us RESTful web services, then you could integrate it that way. But you’re building from the ground up, so it’s not any easier to use RESTfm than it is to code the CWP site yourself.
Thank you, I wasn't sure how rest fm really works and whether it would help me in this situation . I am still learning PHP but I have a person who is well versed with PHP who is willing to take up the project for us ... I was just trying to look at all the options