Dynalist Architecture Deep Dive


#1

I’d be super interested (and I’m sure other engineers here would be as well) to get a deep dive on how Dynalist works under the hood.

I’ve seen on previous posts it mentioned that MySQL is used to store all of the user data. How does Dynalist store the unstructured documents that users make in a structured/schema-based DB? How is large content (image/video) stored? Do you place images/videos/etc. in S3 or some other object store and place the URI in the DB, or do you place large data within the DB?

What were some of the design considerations when choosing MySQL over something like MongoDB that is built for document structures? Do you have any concerns with scaling MySQL as your users/data grows?

Really enjoying the product and hope to learn more about it! Thanks!