Why we should consider AWS Aurora Database Cloning
Aurora is one of the greatest inventions of AWS’s managed database services. I recommend this everyone to use this instead of MySQL.
A few days back they have announced a new feature called Cloning the database. Initially, I taught this is same as restoring the database from the snapshot or point in time restore. But after reading the documentation, I was wondered about this feature and it pushed me to write this blog.
How it works:
Basically its a Copy-on-Write Protocol. While cloning the database it’ll take the database pages from the source database, So no need to copy the data from source database to cloned database. Also no additional storage for this. Then if you modify anything in the existing data pages on Source or Cloned database it won’t apply it to the actual data pages, instead, it’ll create one more additional data page file and apply the changes there.
Limitations:
- We can create upto 15 clones from any sources or clone to clone.
- We can’t clone this to another region.
- Also we can’t clone it to another account.
CTO & Co-Founder @ShellKode | Building Data & GenAI Solutions
7 年No, I won't replicate the new data, it's not something like replication. It'll just share the existing data to the cloned database. If any modifications happening on clone db that new changes will be written in new data pages.
DevSecOps
7 年After cloning the source db, will the new changes on the source automatically reflect on the cloned db?
CEO at Shellkode | Empowering Businesses with Autonomous AI Agents | Driving Growth Through GenAI, Data & Modernization ??"
7 年Good one.