New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Jun 05, 2008
McObject has released version 3.0 of its open source embedded database targeted at Java and .NET developers. As any other embedded database, Perst has no administration costs, but unlike other embedded databases, Perst stores the objects directly as Java or C# objects. That eliminates the need for conversions between internal representation of objects and Java/C# representations.
McObject boasts with a very small database engine core of about 5,000 lines, and the run-time needs between 30K and 300K of memory depending on access pattern. Perst works under Java SE, EE, and ME, and also under .NET including .NET Compact Framework. Other features are:
Perst 3.0 offers full text search, compressed objects under Java, and LINQ support under .NET. Besides Perst, McObject has a commercial version of the embedded database called eXtremeDB.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Getting Started with Stratos - an Open Source Cloud Platform
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Thanks for sharing the info about Perst. I just want to add a clarification.
Perst and eXtremeDB are separate and different products -- eXtremeDB is not the commercial version of Perst.
eXtremeDB is McObject's commercial embedded database system for use with C and C++. Perst is our open source, dual license embedded database for Java and .NET.
Both are well worth checking out if you need a small-footprint, highly efficient, full-featured database system in these environments.
Thanks.
Ted
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
1 comment
Watch Thread Reply