4 Comments

In a traditional SQL environment, database design establishes the data structure that must be followed when developing applications. In DocDB, the data structure is primarily provided by the application itself.

Expand full comment

Great article. Thank you! I am interested in learning more about the failure scenarios, especially during the migration. What if the aysnc replication takes longer than expected? What if the target fails right after the switch? What happens to the incoming queries if the migration takes longer than expected? Do they fail or does it the client retry with backoff resulting in 5 9's of availability?

Expand full comment

I think so in application access in DocDB diagram, you should label the procedure.

For example: As the query hits Database proxy you have shown two paths ,one to chunk service and other to sharded database. Its not like we are querying two things at once.

First we are querying meta chunk service to retrieve the correct shard database and then proxy server queries the shard.

Correct me if I am wrong... As I am a new developer

Expand full comment

The ingenuity it takes to solve problems like this is a proof that AI will not take my job, at least in the foreseeable future that I can see.

Expand full comment