Hi Jonathan,
I'm really interested in the type of hybrid architecture you've mentioned.
How is the read-only index constructed in the design you're mentioning?
It'd be much appreciated if you could briefly describe the order of
writes/reads given postgres and non-postgres components of the
I’m familiar with both PostgreSQL and Riak (1.4, not 2.0).
I know that Riak 2.0 now offers strong consistency. Have not yet seen what that
does to performance.
Big plusses for PostgreSQL:
- you can do both relational and NOSQL tasks (the Binary JSON in the latest
PostgreSQL).
-
A very popular design I see is often this:
- PostgreSQL for account, inventory, transactional; and all writes
- NoSQL (Redis, Riak, Mongo, etc) for read-only index postgres (almost
like a read-through cache) and assembled documents
On Jan 5, 2015, at 5:46 PM, Raymond Cote
Hello, I am looking at creating a toy project which may turn into an actual
business if I'm lucky, the ideal is generally just an exchange for people
to trade some type of asset.
I'm looking at using either PostgreSQL or Riak, and I'm wondering if there
are opinions and suggestions that someone
On Mon, 5 Jan 2015 11:37:37 -0500
xu xiut xiut...@gmail.com wrote:
Hello, I am looking at creating a toy project which may turn into an actual
business if I'm lucky, the ideal is generally just an exchange for people
to trade some type of asset.
I'm looking at using either PostgreSQL or
I’m familiar with both PostgreSQL and Riak (1.4, not 2.0).
I know that Riak 2.0 now offers strong consistency. Have not yet seen what that
does to performance.
Big plusses for PostgreSQL:
- you can do both relational and NOSQL tasks (the Binary JSON in the latest
PostgreSQL).
- well-tested
On 1/5/2015 10:37 AM, xu xiut wrote:
Hello, I am looking at creating a toy project which may turn into an
actual business if I'm lucky, the ideal is generally just an exchange
for people to trade some type of asset.
I'm looking at using either PostgreSQL or Riak, and I'm wondering if
there are
