InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Interview: Avi Bryant on DabbleDB, Smalltalk and Persistence

Posted by Werner Schuster on Jul 23, 2008

Sections
Development,
Architecture & Design
Topics
Runtimes ,
Ruby ,
Dynamic Languages ,
Performance & Scalability ,
Architecture
Tags
Object Databases ,
Seaside ,
Database ,
QCon London 2008 ,
SmallTalk ,
GemStone ,
QCon
In part two of Avi Bryant's video interview (part one of the interview with Avi discussing GemStone's MagLev), Avi talks about his work with Smalltalk and DabbleDB.
DabbleDB is built on Squeak Smalltalk and uses the Seaside web framework. Avi discusses Seaside's influences, such as WebObjects (when WebObjects was still written in Objective-C).

DabbleDB doesn't use an RDBMs - instead it uses Smalltalk's image concept to store data. A Smalltalk VM can persist the state of the VM to disk, basically performing a core dump. The VM can later  load the image and continue running the program from the point where the image was persisted, similar to the way tools like VMWare can suspend, store, and later resume execution of a virtualized machine.
DabbleDB uses this capability to persist data, but also to easily move applications between servers. The data in DabbleDB can also be extracted with a tool that walks all the domain objects and stores this object graph to disk - which allows to update the code in the Smalltalk seperatly from the data.

The interview contains more information - such as whether Seaside applications need to use continuations, the Smalltalk SCM tool Monticello, whether lack of kernel threads is a problem for Squeak and more.

Watch "Avi Bryant on DabbleDB, Smalltalk and Persistence".

No comments

Watch Thread Reply

Educational Content

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.

Cool Code

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.

Collaboration: At the Extremities of Extreme

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.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

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.

10 tips on how to prevent business value risk

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.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

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.