Joyent makes a great service, but they are WAY overly priced. I'd
recommend a 512 SliceHost/Linode. Or a 1GB @ Voxel/SoftLayer.
-J
On Thu, Aug 12, 2010 at 10:40 AM, Alexander Sicular wrote:
> - You can not tell riak where to place buckets.
> - You could set the N val on a bucket to one, and you
First of all, let's eliminate CouchDB. Its WOL filesystem is irrelevant
for this is generated data. If a document gets lost (for whatever
reason) - it can be regenerated. Topmost though, CouchDB can't run
dynamic queries. That's what the field indexes are for. MongoDB is
happy to store & q
- You can not tell riak where to place buckets.
- You could set the N val on a bucket to one, and you should in the case of
your 'big bucket'. Otherwise you will get N replicas on the same physical host.
-Use linode. 512 > 256 = better.
But in reality , your use case doesnt mesh well with what ri
I can easily wait for Riak Search to do this
http://groups.google.com/group/mongodb-user/browse_thread/thread/c2563a8566591a30/b3d19f21675a899e
- instead of mongodb. Does this deployment I have in mind make sense:
I'll get a medium (or large) Linode box for the big dataset bucket.
Hopefully
