Subject | RE: [IB-Architect] Interbase Culture and Open Source |
---|---|
Author | Andy Gibson |
Post date | 2000-03-28T18:59:19Z |
> -----Original Message-----I don't suggest that developers 'blindly' recommend Interbase without a
> From: Markus Kemper [mailto:mkemper@...]
> Sent: Tuesday, March 28, 2000 12:03 PM
> To: IB-Architect@onelist.com
> Subject: Re: [IB-Architect] Interbase Culture and Open Source
>
>
> From: "Markus Kemper" <mkemper@...>
>
>
> > I think also that this could become Interbase's niche market. For
> > those that don't want a mammoth application using Oracle or SQL
> > Server, with half a dozen support staff for it. Not that Interbase
> > can't support mammoth applications
>
> There are going to be applications that InterBase may not be
> best suited for. I have and will continue to suggest an alternate
> vendor in these cases rather than see a customer fail with our
> product. These are opportunities however, for InterBase to
> consider 'features' and/or changes to enable it to perform the
> task at hand. Sometimes I have deferred business based on
> customer design requirements (meaning IB was a solution option
> but, based on application implementation not available to the
> developer).
thought to the actual issues. What I am suggesting is that rather than
'downgrade' the solution from Oracle or SQL server (i.e. an app that
requires features / functionality from these DB's), 'Upgrade' an application
that would use Paradox, or Access or some other network DB to Interbase. I
suspect these are mostly used because they are available for free (once the
developer has the tools to generate the DB). Also, customers find out they
get scalability for almost nothing.
Regards,
Andy Gibson