Apache Derby- Great for localized Risk Modeling
June 13, 2018
Apache Derby- Great for localized Risk Modeling
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Apache Derby
In the Project I was using Apache Derby, we were shadowing larger databases (MS SQL + Cygnet), and providing some failover for those platforms. Most of the Use case was research-oriented, but it allowed the Risk Modelers to grab a subsection of data from these two data sources, and then combine them inside an apache derby instance. Given its size, it was a good fit.
- Apache Derby is SMALL. Compared to an enterprise scale system such as MSSQL, it's footprint is very tiny, and it works well as a local database.
- The SPEED. I have found that Apache Derby is very fast, given the environment I was developing in.
- Based in JAVA (I know that's an obvious thing to say), but Java allows you to write some elegant Object Oriented structures, thus allowing for fast, Agile test cases against the database.
- Derby is EASY to implement and can be accessed from a console with little difficulty. Making it appropriate for everything from small embedded systems (i.e. just a bash shell and a little bit of supporting libraries) to massive workstations.
- Not as well positioned in the market as the "big dogs" (Oracle, MSSQL)
- Been around awhile, and not a lot of exposure. This I believe is primarily due to it's relation to the Apache Project (which is not bad, but they don't force big, lumbering corporate volume licensing on you), and thus people are a bit gun-shy about NOT throwing money at something
- Java is still "slow" compared to C/C++, thus making Derby a bit slow too
- Being Open source, the resources spent on the purchase of the product are ZERO.
- Contrary to popular belief, open source software CAN provide support, provided that the developers/contributors are willing to answer your emails.
- Overall, the ROI was positive: being able to experiment with an open source technology that could perform on par with the corporate products was promising, and gave us much information about how to proceed in the future.
For our particular use case, Apache was selected for its ease of use, in its ability to be installed, configured and embedded in our in-house application.