c# - .NET, JSON, Embedded, Free Commercial-Use data management solution? What to do? -
i trying develop data management solution commercial product meets several criteria. criteria , reasoning follows:
- the solution should in c# or support c#
- manage data json
- no external schema maintenance
- be able cache or data in memory , persist disk
- not require additional installation
- if solution involves third-party software, license must support no-cost commercial use
requirement #1: application written in c# , prefer solution not involve integrating applications, libraries, or code in language.
requirement #2: there several json-based tools , libraries utilize, need solution data either in or converts to/from json.
requirement #3: want avoid schema maintenance comes using relational database solutions. prefer manage mismatched data-to-object mappings in code , have code update older data instead of managing schema updates separately.
requirement #4: require or data loaded memory @ times, , data persisted disk. whether data persists in memory or not should optional per data type.
requirement #5: when installing product don't want have secondary installations or have external services running other application. self-contained solution best.
requirement #6: intended use distributed commercial product. prefer avoid additional fees or licensing issues come many third-party solutions.
to date have tried several solutions. did not have many constraints , went sqlite.net , use wasn't unpleasant, overhead schema maintenance , data format more like. investigated lot of nosql solutions (such ravendb), other third-party solutions (karvonite), , simple json file storage implementations, i'm not satisfied of them.
is there custom approach or solution missing, else has used successfully? i'm hoping overlooking option(s) after, , nosql , .net experts out there have enough experience in area point me in right direction.
edit: in case original commentators confused, updated question , title better adhere so's policies.
fluent nhibernate automapping on top of sqlite meet requirements except edit #2 - "nosql, preferably data json document"
it automaps relational db schema object model...does not use json. edit might able save json data blob, however. (caveat: know nothing json)
Comments
Post a Comment