您的位置: 首页  >  技术问答  >  如何确定数据库服务器或嵌入式数据库是否合适

如何确定数据库服务器或嵌入式数据库是否合适

分类: 技术问答 • 2022-03-11 08:41:31
问题描述：

Bolt is a pure Go key/value store inspired by Howard Chu's and the LMDB project. The goal of the project is to provide a simple, fast, and reliable database for projects that don't require a full database server such as Postgres or MySQL.

Bolt readme

How does one determine if an application requires a full database server? I assume it has to do with number of concurrent writers?

I'm planning on writing a simple distributed social networking application as a fun project.

Bolt是受Howard Chu和LMDB项目启发的纯Go键/值存储。 该项目的目标是为不需要完整的数据库服务器（例如Postgres或MySQL）的项目提供一个简单，快速且可靠的数据库。 p> blockquote>

螺栓自述文件 p>

可以确定应用程序是否需要完整的数据库服务器？ 我认为这与并发作者的数量有关？ p>

我正计划编写一个简单的分布式社交网络应用程序作为一个有趣的项目。 p> div>

答

  1. An embedded database resides within the application. It doesn't need to be relational.

    For instance, the media manager on your computer has a database embedded within it to store audio/video metadata and file location. This database could be relational, in which case, the database could be something like sqlite or mysql. (i don't think postgres can be deployed embedded in an application). Embedded databases are great if you want to cache local information, or you're sure that information within the application does not need to be communicated externally for the application's functionality. A core design goal for embedded databases is having a low footprint, so in many cases embedded databases omit features found in dedicated databases.

  2. A dedicated database server supports one or many clients' read and write operations, and usually provides more features than the embedded versions. Postgres and Mysql are both dedicated databases and are used widely in networked applications. They are also both relational databases, and not key-value stores, which Bolt seems to be.

  3. A key value store is a non-relational database. Think redis (or dicts in python), where

    • retrieval: the client gives the database the key, and the database responds with the value.
    • assigning: the client provides the database a key & value, and the database assigns a new key with given value, or updates the existing key's value.

    Note: postgres has hstore, which is a key value store.

Just like relational databases, key-value databases can be embedded within or reside separately on dedicated hardware. Here are some example questions one must ask while making these architecture decisions.

  1. Does my application depend on data that need to be communicated, and do I want to communicate the data by writing to a central database, or does each chat client connect to the other client on a peer to peer model and stores its own data?

  2. Do I need a relational model in my application, or a key-value store, or some other exotic data model?

Just my personal opinion, the relational model has been successful at satisfying a wide variety of persistent requirements over the last 30 odd years. Has very mature solutions for both embedded or dedicated deployment. It is a good place to start.

相关推荐