overlyaing KV store on top of a relational store m...
# getting-starteda
adventurous-air-87342
05/27/2021, 5:16 PMoverlyaing KV store on top of a relational store may lead to performance issues. I don’t know if this is true of course..
m
mammoth-bear-12532
05/27/2021, 5:25 PM
MySQL on SSD as k-v store is actually how Facebook and LinkedIn data infrastructure runs. It is rock solid from that perspective.
mammoth-bear-12532
05/27/2021, 5:26 PM
However, there are cases where you really need a scale-out K-V store and something like Cassandra / DynamoDB / ... can be used there. Although MySQL now has Vitess.
mammoth-bear-12532
05/27/2021, 5:28 PM
@adventurous-air-87342: Here is a good read on how FB uses MySQL under the covers for its oltp data storage (https://medium.com/yugabyte/facebooks-user-db-is-it-sql-or-nosql-6ec01b2e7f65)
mammoth-bear-12532
05/27/2021, 5:31 PM
An old but still accurate talk from LinkedIn on their system that uses MySQL (Espresso) (https://www.slideshare.net/amywtang/li-espresso-sigmodtalk)
b
big-carpet-38439
05/27/2021, 5:59 PMits more performant than your usual mysql tables i'd argue
big-carpet-38439
05/27/2021, 5:59 PMdue to the minimal indexing requirements.
m
most-pillow-90882
04/05/2022, 6:35 PMHas anyone completely replaced the mysql container with DynamoDB (or other NoSQL) for the backend? It would simplify some things for me from an internal deployment perspective?
m
mammoth-bear-12532
04/12/2022, 3:22 PM
Hi @most-pillow-90882: here is a PR that replaces the mysql container with Cassandra. https://github.com/datahub-project/datahub/pull/3286
plus1 1
thank you 1