﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Charlie commented on Designing a document database: Storage</title><description>Just had another look at Couch Db, yes I was missing the point :)
  
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment8</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment8</guid><pubDate>Wed, 11 Mar 2009 12:06:39 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Storage</title><description>Charlie,
  
You are missing the point, we are not storing scanned documents. Look at couch db for example.
  
In addition to that, I really don't think that we will reach the 16 TB limit so quickly. If you do, run another instance.
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment7</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment7</guid><pubDate>Wed, 11 Mar 2009 03:15:59 GMT</pubDate></item><item><title>Charlie Barker commented on Designing a document database: Storage</title><description>ESENT has a 16TB  size limit.
  
I you were storing scanned documents that averaged 1mb you could only store 16 million documents in a single ESENT db. Not a horrific limitation but one worth noting now.
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment6</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment6</guid><pubDate>Tue, 10 Mar 2009 18:30:10 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Storage</title><description>Esent doesn't run on Linux
  
But I am not going to worry about that until there is a contributer that is actually going to make it run there.
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment5</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment5</guid><pubDate>Tue, 10 Mar 2009 05:44:28 GMT</pubDate></item><item><title>Yitzchok commented on Designing a document database: Storage</title><description>Any Esent support on Linux? if not maybe its best to separate the datastore part so that you can create a backend database/store implementation and the main system doesn't really know about the datastore. Or will this just make the system too slow.
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment4</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment4</guid><pubDate>Tue, 10 Mar 2009 05:20:50 GMT</pubDate></item><item><title>josh commented on Designing a document database: Storage</title><description>ok. my bad. didn't read your couch db posts. this makes more sense after reading about couch db.
  
  
now i'm really curious how it works. how it finds the document you're looking for.  i'll have to read more about couch db.
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment3</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment3</guid><pubDate>Tue, 10 Mar 2009 04:09:54 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Storage</title><description>Josh,
  
document database are not e-doc apps, nothing like share point.
  
Take a look at lucene or couch db for the details
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment2</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment2</guid><pubDate>Tue, 10 Mar 2009 03:38:58 GMT</pubDate></item><item><title>josh commented on Designing a document database: Storage</title><description>I'm really curious where you re going with this. one old client had us help write an electronic doc application, which had to address some similar questions.  With the previous mention of schema-less database, it seems you're going in a really different direction with this.
  
  
not sure I understand what you mean by view for this. could you clarify?
</description><link>http://ayende.com/3898/designing-a-document-database-storage#comment1</link><guid>http://ayende.com/3898/designing-a-document-database-storage#comment1</guid><pubDate>Mon, 09 Mar 2009 23:23:28 GMT</pubDate></item></channel></rss>