Thread
#getting-started
    a

    adventurous-air-87342

    1 year ago
    overlyaing 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

    1 year ago
    MySQL on SSD as k-v store is actually how Facebook and LinkedIn data infrastructure runs. It is rock solid from that perspective.
    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.
    @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)
    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

    1 year ago
    its more performant than your usual mysql tables i'd argue
    due to the minimal indexing requirements.
    m

    most-pillow-90882

    5 months ago
    Has 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

    5 months ago
    Hi @most-pillow-90882: here is a PR that replaces the mysql container with Cassandra. https://github.com/datahub-project/datahub/pull/3286