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 Nov 25, 2008
In this interview, Damien Katz talks about CouchDB, a distributed, fault tolerant, document oriented database developed by Apache Incubator. CouchDB is written in Erlang, and the database is accessed through an HTTP/JSON API. The database view engine is run on JavaScript, but other languages have been used like Ruby and Python.
Watch: Damien Katz Relaxing on CouchDB (20 min.)
Damien details what CouchDB is, how it works and what purposes serves best. A former IBM employee working on Lotus Notes, Damien started CouchDB using a lot of good ideas existing in Notes while trying to avoid the mistakes made with it.
CouchDB is a schema-free document oriented database good at indexing and searching through documents. Documents can be created and edited both online and offline, CouchDB resolving conflicts and replicating documents. The first version of the database was written in C++, but later Erlang was chosen due to its capability to handle concurrency well. As a result, CouchDB supports 20,000 simultaneous connections according to an preliminary benchmark quoted by Damien.
The database view engine is provided by JavaScript, but the database was constructed in such a way that more languages can be used to create views of the database, and there are already versions using Ruby, Python and PHP.
At the end of the interview, Damien talks a bit about what he doesn’t like in Erlang, string manipulation being one of them.
Mobile and the New Two-Tiered Web Architecture
18 agile and lean practices for effective software development governance
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.
2 comments
Watch Thread Reply