OID 键控 blob 存储在程序员中是否有市场？
一位朋友开发了一个非常令人惊叹的 blob 存储，我认为需要使用它，但我想知道人们是否认为这样的东西有市场，以及程序员是否可以做出此类决定。 它支持使用增量的在线备份，并且比我所知道的任何东西都快得多，它经过了严格的测试并在一些非常小众的应用程序中使用。 我认为任何拥有二进制文件格式的人都愿意使用它作为替代方案。 它具有 C++ 接口，并已适应 .NET 序列化。
它绝对让 SQL Blob 表彻底崩溃。
想法？
编辑：它更好，因为：
- 它非常快。
- 它是事务性的，具有完整的恢复扫描，比平面文件要好得多。
A friend has developed a very amazing blob store and I think it needs to be used, but I'm wondering whether people think such a thing has a market, and if programmers ever get to make these kinds of decisions. It has support for online backups using deltas and is much faster than anything I know of, it's undergone rigorous testing and being used in some very niche applications. I would think anyone with a binary file format would like to use it as an alternative. It has a C++ interface and has been adapted to .NET serialisation.
It absolutely blows SQL blob tables out of the water.
Thoughts?
Edit: It is better because:
- It is very fast.
- It is transactional, with a full recovery scan, so far better than flat files.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
市场是有的，但不是很大。 还有长期存在的竞争，请参阅BerkleyDB（其中是一个独立销售的产品（公司名称：SleepyCat），但不久前被 Oracle 收购。
There's a market, but not a massive one. There is also long-established competition, see BerkleyDB (which was an independently marketted product (company name: SleepyCat), but they were bought by Oracle a while back.
想法？ 您还没有说它如何更好...（或者对于平面 BLOB/数据库/文件解决方案如何更好）。
此外，常规 .NET（二进制）序列化不太适合长期存储（在数据库中），因为它是特定于实现的（并与程序集绑定）。 对于序列化，您可能需要查看独立于平台的解决方案，例如 Google 的协议缓冲区（它具有 的实现C++、java、C# 和其他 - 包括我自己的一个）。
Thoughts? You haven't said how it is better... (or how it is better to a flat BLOB/database/file solution).
Also, regular .NET (binary) serialization isn't well-suited to long-term storage (in a database), since it is implementation-specific (and tied to the assemblies). For serialization, you might want to look at platform-independent solutions such as Google's protocol buffers (which has implementations for C++, java, C#, and others- including one of my own).
根据许可和成本，我当然会考虑。 就在几周前，我询问了类似的事情，并最终使用目前是一个 SQLite 数据库文件，我怀疑这不是最佳的。
（我经营自己的软件开发公司，所以我做出购买决定。:-)）
Depending on the licensing and cost, I'd certainly look at it. I asked about something like this just a couple weeks ago, and ended up using an SQLite database file for the moment, which I suspect is less than optimal.
(And I run my own software development company, so I do make the purchasing decisions. :-) )