AwDb vs Datomic

[William la Forge]

Learned a lot today about Datomic. It compares nicely with AwDb:

• Both are immutable databases and leverage this for parallel queries.
  
• Both deal with time the same way.
  
• Both build on the same set of indexes.
  
• Both make good use of in-memory caches.

Datomic has some nice advantages:

• It is a more mature product.
  
• It has an established customer base.
  
• It has a large development team.
  
• Queries and storage scale horizontally, though transactions are processed in a single JVM.
  
• It has a nice query language.
  

AwDb also has some nice advantages:

• Significantly faster, though this is mostly an educated guess based on the unique technologies built into AwDb.
  
• An OO model, providing better integration with an application.
  

And yes, we could build an OO model on top of Datomic. But for too many things, speed is critical. And while caches help, they often do not get you the performance you need, especially for updates.

Bill La Forge CTO

[Bill]

Two points.

First, both Datomic and AwDb support multi-valued attributes.

Second, AwDb is itself a database, while Datomic layers over a variety of databases. Having a fast, built-in database is a real speed advantage.

[Vicky Kak]

Worth reading
http://tonsky.me/blog/unofficial-guide-to-datomic-internals/

--
You received this message because you are subscribed to the Google Groups "AgileWikiDevelopers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilewikidevelo...@googlegroups.com.
To post to this group, send email to agilewiki...@googlegroups.com.
Visit this group at http://groups.google.com/group/agilewikidevelopers.
For more options, visit https://groups.google.com/d/optout.