If inscribe
Relationship between business systems mostly use the DB, table, built entity class and write data query,
So if you are using a KV database, using relational DB, what are the benefits and bad place?

Basically see KV database query speed is faster

CodePudding user response:

We say now development is mixed mode

So, even the language we will not require harmonisation, do you think we will be entangled with unified database
?So the problem is not how kv database, and play a this vs that, this benefit, that is bad, the faster the unpleasant

Important question (of course I don't want to say 3 times)
1. You analyze your own business, break up your business, review the suitable for their relationships, including those for kv, and even some things we said that such a figure with the secondary data is more suitable for

Although I don't want to say "full head only CURD, ORM", but the nature of the ans neter should return to programming, don't always wandering

CodePudding user response:

See requirements and needs

CodePudding user response:

It is yes,
I didn't use fruit KV data in the project, but found that KV is a bit much, really don't know for business CRUD project, what pit and solutions

CodePudding user response:

Look business needs, complex data structure with a relational database, simple concurrency is work with KV database, not idle complex mixed with,

CodePudding user response:

If you learn database principle or to use formal lessons learned "database first paradigm" will know, relational database nature is particular about the primary key as the key to query the entire record, with k - v in fact doesn't make sense! Said "no database is the same," said "k - v" database is like said the spoon, it is not the same tableware,

No (do not use the relationship between language, do not support transactions, not easy to read and write a record of any combination of fields (but must be the value object or document to read and write), and even cannot create and reasonable make use of the index, in addition to the k consistency constraints, cascading deletes and cascading updates and so on, of course, also did not trigger a stored procedure, etc., there is no relationship between SQL query and query compilation techniques, without logging system, not all kinds of object management, no management client tools, have no legal power system, and so on and so on,

The simple cache as "database", "benefit" has its simplicity, but also have the title of the abuse of the means of the party,

CodePudding user response:

Many applications simply can't afford to use the traditional commercial relational database system, such as many host access services need to be in memory synchronous some state information, the business have the basic request for performance processing speed, is not what a relational database can carry, must be level access memory variable amplitude, but also need to cluster synchronization, so what will first think of using a memory k - v service program, and is open source, the database is this? This is just the external cache service,