Hi Justin,

Can you point me at an example of the MongoDB based architecture you describe. 
I’m busy putting together a project with Mongo for fun and that’s probably the 
next thing to consider. Thus far I have a set of extensions to the Mongo driver 
for C# that supports expressions and an implementation of the 
MembershipProvider (Yuck).

Cheers,

Ade


From: Justin Bozonier 
Sent: Saturday, November 05, 2011 2:58 PM
To: [email protected] 
Subject: Re: NoSql, what's your defaults these days?

For prototypes I default to an in memory dictionary in Heroku.

For more robustness I start to store that dictionary in Mongo.

To scale beyond there my preference is to push data into Mongo and have 
separate concurrent services work to digest/aggregate/cache views on that data. 
I'm good with eventual consistency.

Good question! Looking forward to more answers.

Sent from my iPhone

On Nov 5, 2011, at 2:45 PM, Adron Hall <[email protected]> wrote:


  Hello ALT.NETters

  So I've been messing around a lot more with NoSQL solutions, mainly from the 
perspective of getting prototypes faster with the increased flexibility.  My 
defaults have been the following as of late: 

  1. If I'm stuck with SQL Server, (i.e. some Corporate IT Limitation or 
something) I've often tried to go the SisoDb Route, in other words, I try to 
design my architecture where it is not limited by the relational and column 
concerns of an RDBMS. This is, primarily being that I'm trying to do more rapid 
prototyping of applications.
  2. MongoDb is my other go to for a real NoSQL Solution. So far the reason has 
been because of the extensive support and what appears to be greater usage of 
the solutions available on the market. This doesn't in any way mean that 
MongoDb is the best solution, just the path with the least resistance. Getting 
a solution running with Ruby on Rails, .NET, or whatever is usually the stack 
that is utilizing the database is generally extremely easy - more so than 
setting up a SQL Server by an order of magnitude (at least from a time 
perspective).

  Another thing that I've found myself using for fast prototyping of an 
application, and for local server caching of data, is to use bin deployable SQL 
CE. With .NET MVC it's crazy simple to get something out the door. If your dev 
environment is already setup one can usually get a CRUD app out the door in 
about a half hour of fiddling.  <-  Very nice.

  Some others I want to try out really soon are Riak, Neo4j, and Redis. The 
link posted looks really good for some comparisons too, pretty helpful (the one 
Ben posted at http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis)

  My questions are...
    a.. What are other people using for prototyping applications? 
    b.. What are other people using for reporting solutions? Like BI, etc? 
    c.. What are other people using for high row/document/data or "big data" 
storage?  ( > Terabytes of data, multiple millions of rows/documents of data) 
    d.. What solutions do you find the most flexible out of the options that 
are market these days? (such as HBase, Cassandra, Neo4j, Redis, Riak, etc)
  Thanks!
  -- 
  Adron B Hall

  Tech: http://compositecode.com
  Transit:  http://transitsleuth.com
  Twitter: http://www.twitter.com/adron

  -- 
  You received this message because you are subscribed to the Google Groups 
"Seattle area Alt.Net" group.
  To post to this group, send email to [email protected].
  To unsubscribe from this group, send email to 
[email protected].
  For more options, visit this group at 
http://groups.google.com/group/altnetseattle?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Seattle area Alt.Net" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/altnetseattle?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Seattle area Alt.Net" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/altnetseattle?hl=en.

Reply via email to