문제

I have a few .Net projects that would benefit from using a document/object database opposed to a relational one. I think that db4o would be a good choice, but we're not sure how much the cost is. I'd love to use MongoDB but it's design isn't for small scale, single server applications.

Are there other options out there that I just haven't run across for small scale applications?


EDIT: So is this a space that doesn't have a good solution, yet? Are there no small scale & durable document databases? Would my best choice be to use MongoDB and set the --syncdelay option set to 1?

도움이 되었습니까?

해결책 3

So RavenDB looks to fit what I'm looking for. I played around with the source and gave it a spin. It's a mix of CouchDB and MongoDB. The main difference is that it uses the ESE engine built into Windows which provides crash recovery, which is mainly what I'm looking for. According to Ayende's Blog there's still much more to be done before it's released, but it's fun to follow along from GutHub.

다른 팁

ISO / IEC / IEEE 9945 : 2009을 원합니다. iso / iec 9945-1 : 1996, ISO / IEC 9945-1 : 2003 및 ISO / IEC / IEEE 9945 : 2009 개정되었습니다.

다음 POSIX FAQ 추가 정보, 특별히 관련 Q4...에어디에서 1003.1 표준을 다운로드 할 수 있습니까? 등록이 필요한 무료 HTML 온라인 버전에 대한 링크가 포함되어 있습니다. 여기에.

if, it's really very small scale, just serialize/deserialize it yourself :) or create a document based structure in an embedded relational database like SqLite...

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top