Subject | RE: [firebird-support] Need Feedback on Using Firebird for Element Management Software |
---|---|
Author | David Johnson |
Post date | 2005-03-22T00:21:38Z |
On Mon, 2005-03-21 at 16:06 -0800, Nina Grooms wrote:
How much concurrency does you app support (i.e. how many concurrent
transactions can be expected)?
Is a two-phase commit necessary (Conversely, does it matter if you lose
data under some circumstances)? MySQL, for example, does not support
two phase commit, whereas Firebird does. This gives MySQL a performance
edge in the benchmarks, but results in data loss in some circumstances.
Firebird is a full-featured database comparable to any commercial
offering in terms of features and performance.
>...
>
>
>
>
> ________________________________
>
> From: Helen Borrie [mailto:helebor@...]
> Sent: Monday, March 21, 2005 3:21 PM
> To: firebird-support@yahoogroups.com
> Subject: Re: [firebird-support] Need Feedback on Using Firebird for
> Element Management Software
>
>
>
> At 09:51 PM 21/03/2005 +0000, you wrote:
>
>
>
> >Were planning on using Firebird v1.5.2 as the database for an
> >Element Management Software (EMS) product for a wireless LAN
> >product. We're trying to find out if anyone out there has used
> >Firebird successfully in this type of application. Specifically, we
> >will be managing many network elements that will require processing
> >a large amount of transactions and want to know if Firebird is well
> >suited for this. Does anyone out there have feedback for us on this?
>
> If you provide some specifics about the kinds of "elements" you want to
> store and retrieve and what you consider a "transaction" to be, I'm sure
>
> there will be some answers for you. Some general specifications
> regarding
> system architecture would enlighten. If you know the environment in
> which
> the software will be developed, that might throw up some leads for you,
> too.
>
> ./heLen
>
>
>
>
>
> We're developing a network management product that will eventually
> manage in excess of 1000 network elements (routers, switches, etc.).
> We'll use the database to store configuration criteria, polling
> thresholds, alarms, events, etc. for each of the network elements.
>
>
>
> We consider a transaction to be a specific action on the database
> (retrieve, write, update and delete) that can be rolled back. We expect
> that we will need to be able to accommodate in excess of 1000
> transactions/second.
>
> The software is being developed in a Linux development environment.What class of hardware are you running the app on?
>
>
How much concurrency does you app support (i.e. how many concurrent
transactions can be expected)?
Is a two-phase commit necessary (Conversely, does it matter if you lose
data under some circumstances)? MySQL, for example, does not support
two phase commit, whereas Firebird does. This gives MySQL a performance
edge in the benchmarks, but results in data loss in some circumstances.
> General database related specs: JDBC distributable, retrieval databaseYou will want the jaybird class 4 driver for firebird.
> architecture.
Firebird is a full-featured database comparable to any commercial
offering in terms of features and performance.