RDBMS

[ddevore]

After I finish the reactive journal, I'm thinking that we should support some RDBMS's like Postgres and MySQL. We can use H2 as an in-memory database for testing. Not that I love RDBM's or anything, but a lot of folks out there still use them. I'd be more than happy to write the journals for Postgres and MySQL. WDYT?

As you guys can guess, i'm a NoSQL Mongo fan but found the following video awesomely funny - MongoDB vs MySQL. Forgive me if you've already viewed it.

The preceding email message may contain confidential information of Viridity Energy, Inc. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this message in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the message.

[Martin Krasser]

Am 22.03.13 06:42, schrieb ddevore:

After I finish the reactive journal, I'm thinking that we should support some RDBMS's like Postgres and MySQL. We can use H2 as an in-memory database for testing. Not that I love RDBM's or anything, but a lot of folks out there still use them.

An excellent idea, really like it. Definitely an interesting option for companies with rather strict DBMS policies.

IMO, a good starting point would be a generic JDBC journal with optimization hooks for more specific drivers. Furthermore, instead of storing messages as bytes (blobs) we could also allow applications to map Message payloads (i.e. events/commands) to custom tables. Maybe it's also possible to optimize some relational databases for certain access patterns, such as appending rows only without ever mutating them, to gain some performance.

I'd be more than happy to write the journals for Postgres and MySQL. WDYT?

I'd love to see such a contribution. Thanks for offering help.

As you guys can guess, i'm a NoSQL Mongo fan but found the following video awesomely funny - MongoDB vs MySQL. Forgive me if you've already viewed it.

The preceding email message may contain confidential information of Viridity Energy, Inc. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this message in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the message.

-- 
Martin Krasser

blog:    http://krasserm.blogspot.com
code:    http://github.com/krasserm
twitter: http://twitter.com/mrt1nz

[ddevore]

I agree a generic JDBC w/ hooks is the way to go.

You idea about mapping payloads to custom tables is very interesting. So were you thinking a table per command/event?