Hi Michael,
Your opinion was very encouraging - I also built a
prototype based on Derby.
I am happy to say, that our management has almost
decided on Derby, subject to legal approval for the licensing
aspects.
We plan to use Derby as an embedded RDBMS in our
Network Management Application. The data stored in Derby will be typical network
management data pertaining to the inventory, fault and performance aspects of
network elements.
With this mind, I would like a
clarification:
If an external application would like to extract this
data for correlation with the typical customer data, the general way will be to
use ij and proceed. The double booting issue will prevent this.
What are all the possible workarounds for the double
booting issue? Can you please give me the required
pointers?
Is there any potential issue when multiple copies of
Derby runs in the same PC (Within the same application or within different
applications)?
I appreciate your
inputs.
Thanks
Raji
From: Raji Sridar [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 13, 2005 11:17 AM
To: raji Sridar
Subject: [Fwd: Re: Are you happy with Derby?]
-------- Original Message --------
| Subject: | Re: Are you happy with Derby? |
|---|---|
| Date: | Fri, 9 Sep 2005 13:20:17 -0500 |
| From: | "Michael J. Segel" <[EMAIL PROTECTED]> |
| Reply-To: | "Derby Discussion" <derby-user@db.apache.org> |
| To: | derby-user@db.apache.org |
| CC: | Raji Sridar <[EMAIL PROTECTED]> |
| References: | <[EMAIL PROTECTED]> |
On Friday 09 September 2005 12:49, Raji Sridar wrote: First take what I say with a grain of Salt.... You're asking a Derby list so you're going to get a positive and biased response. The short answer is yes. > Hello Derby Users, > > I recently subscribed to this group. > We are evaluating a open source database for a windows based network > management product for the commercial market. > The criteria is to have zero cost, zero admin, small footprint, with max > reliability and good support availability. Derby is really your only option. With respect to other alternatives, I don't believe MySQL is "free" if you're going to embed it in an app for resale. Of all of the "free" RDBMSs, Derby has the smallest footprint, and since its a derivative of Cloudscape, its already been used and proven in the type of application that you're attempting to build. You could use PostGress, but again, you're getting a lot of additional features that you really don't need or want. The only caveat is your "good support" criteria. "Good Support" is relative. You get what you pay for... > We are looking the ability to prototype and develop fast - hence > planning to use Hibernate in conjunction with Derby. > We are not looking for database features like client-server, redundancy, > replication, high availability, 2-phase commit..... > For these criteria, do you agree that Derby is the best choice? > Please give your opinions and suggestions - I appreciate and value your > opinions. > > Sincerely, > Raji As I said, you're going to get a biased response. I like others are looking at Derby from a similar perspective. The only drawback is that Derby is under GPL. So as long as you follow GPL's rules, you're ok. -- Michael Segel Principal MSCC (312) 952-8175
