Re: [cobalt-developers] Interbase vs. MySQL

["Nick Temple" <ntemple@xxxxxxx>]

See below.

*********** REPLY SEPARATOR  ***********

On 11/1/00 at 2:51 PM Sean Pecor wrote:
[snip]

>1. Is a RAQ deployed with Apache statically linked, or does it use DSO?

On RaQ3 / 4, it uses DSO.  On the 4, it is compiled with the Extended API. (EAPI) - this can cause problems for some modules unless anticipated.

>2. Presently, we support Linux / Apache / PHP /  MySQL. Now, I understand RAQ 
>is hot on Interbase, for whatever reason. Has anyone else worked with a MySQL 
>-> Interbase port? Are there pitfalls to avoid before I begin? 

Haven't tried it yet, but plan to.  If you are selling a product, MySQL is a no-brainer to install in a .pkg / rpm. The recent addition of transaction functionality removes one of my two main concerns (the other is subselects).  But Interbase looks pretty good and I'd like to try it.

>3. Are RAQs PHP capable out of the box? PHP is a no-brainer to install 

RaQ4 is.

>4. We're preparing to offer a subscription-based license for our technology 
>(to be paid monthly, quarterly or annually at the discretion of the 
>subscriber). Has anyone else begun experimenting with this model? Success? 
>Failure? I think it gels perfectly with our technology, but I'd love your 
>input. 

We're considering it for our CommerceLink Application Server.  Since we connect to multiple backend payment gateways (and other services) that update their protocal frequently (so we have to make software updates frequently), we will either do a quarterly / yearly license or a mandatory yearly maitnenance fee to keep the software current.  A transaction processing system that stops working when CyberCash/Verisign/CyberSource/AuthorizeNet etc updates their protocal does no one any good, as it happens frequently.

I think the success / failure will depend on your target market.  Ours is the ISP/ASP/CSP market  (those already maintaining RaQ's or writing applications for them).  Some larger ones (read: funded) seem to prefer to purchase outright, while the smaller ones like the flexibility of a "pay as they go".

Nick