Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Floyd Marinescu on May 25, 2006
| Feature | H2 | HSQLDB | Derby | Daffodil | MySQL | PostgreSQL |
|---|---|---|---|---|---|---|
| Embedded Mode (Java) | Yes | Yes | Yes | Yes | No | No |
| Performance (Embedded) | Fast | Fast | Slow | Slow | N/A | N/A |
| Performance (Server) | Fast | Fast | Slow | Slow | Slow | Slow |
| Transaction Isolation | Yes | No | Yes | Yes | Yes | Yes |
| Cost Based Optimizer | Yes | No | Yes | Yes | Yes | Yes |
| Clustering | Yes | No | No | No | Yes | Yes |
| Encrypted Database | Yes | No | Yes | No | No | No |
| Files per Database | Few | Few | Many | Few | Many | Many |
| Footprint (jar/dll size) | ~ 1 MB | ~ 600 KB | ~ 2 MB | ~ 3 MB | ~ 4 MB | ~ 6 MB |

RDBMS to NoSQL: Managing the Transition
Banking Case Study: Scaling with Low Latency using NewSQL
App Server Evolution: REST, Cloud, and DevOps Support in Resin 4
Introduction to WebSphere Liberty Profile
Introducing SQLFire: a memory-optimized, high performance SQL database
VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface
It's also important to know that it is "Written Java; also available as native executable".
Any comparisons between those versions?
Read carefully the "Locking, Lock-Timeout, Deadlocks" section from www.h2database.com/html/frame.html
IMHO the table level locking for managing concurent access is quite a problem for multiple users scenarios. May be DB2 is slower but IBM uses row based locking, a policy that can give you more throughput in multiple users usecases.
Read carefully the "Locking, Lock-Timeout, Deadlocks" section from www.h2database.com/html/frame.html IMHO the table level locking for managing concurent access is quite a problem for multiple users scenarios. May be DB2 is slower but IBM uses row based locking, a policy that can give you more throughput in multiple users usecases.
True, but as mentioned in the article, Thomas' first priority is making the DB work best "on the low end (single user, Access, Embedded)". I think this is the largest use scenario for HSQLDB and H2. Here at InfoQ we used HSQLDB on developer dev machines (single user, embedded) to simplify the environment instead of the production DB.
It's free, but it's not technically open source.
(I'm not an open source zealot, but I am an accuracy zealot)
From the FAQ:
Is this Database Engine Open Source?
It is free to use and distribute, and the source code is included. But currently does not have a 'open source style license', but this will probably change soon. See also under license.
The FAQ covers it briefly.
www.h2database.com/html/faq.html
The GCJ version is not as stable as the Java version.
Currently, the GCJ version is also slower than when using the Sun VM.
The comparison states that MySql doesn't run in "embedded mode". I thought it did since version 5.0?
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
6 comments
Watch Thread Reply