# Best Scenarios For Tidb

__*Best scenarios for TiDB*__

+ TiDB is suitable for the following scenario:
  + Too much data for a single-node database
  + You don't want to deal with the complexity of database sharding
  + Data access patterns don't have obvious hot spots
  + Require transaction processing, strong consistency disaster recovery
  + Real-time Mixed Transaction/Analytical Processing: HTAP
------------------------------------------------------------
Too much data for a single-node database
  In general, for a single database, if the data volume is massive (more than 1 TB in a single table), there will be a sharp drop in query and update performance, but distributed database, such as TiDB, tend to cover the comfort zone of 100GB to 100TB.

You don't want to deal with the complexity of database sharding
  If there is too much data in the table in the query, we want to perform statistical analysis and transaction across the shards after splitting the sharded table according to a column. This is when distributed database come in handy.

Data access patterns don't have obvious hot spots
  If your business has a large number of Lightning Deals and small table query are updated, distributed database tend to form hot spots, and it is recommended to use caution.

Require transaction processing, strong consistency disaster recovery
  If there is a high availability requirement and multiple write requests, then a single database cannot meet consistency, and distributed data is a good fit because it has the inherent consistency advantage of multiple replica.

Real-time Mixed Transaction/Analytical Processing: HTAP
  The TiDB database can meet the needs of online trading and analysis at the same time because there are two forms of row store and column store at the same time.