Database Sharding with ActiveRecord

Database Sharding is a highly scalable approach for improving the throughput of large database-centric business applications. It is a type of database partitioning that separates very large databases into smaller, faster, easier managed parts called data shards​.

Transcript

1. Database Sharding with Active Record
2. Database Sharding is a highly scalable approach for improving the throughput of large database-centric business applications. It is a type of database partitioning that separates very large databases into smaller, faster, easier managed parts called data shards What is Database Sharding?
3. Database Partitions
4. “Involves creating tables with fewer columns and using additional tables to store the remaining columns. Normalization also involves this splitting of columns across tables, but vertical partitioning goes beyond that and partitions columns even when already normalized.” Vertical Partition
5. Horizontal Partition “Involves putting different rows into different tables. For example, customers with ZIP codes less than 50000 are stored in CustomersEast, while customers with ZIP codes greater than or equal to 50000 are stored in CustomersWest. The two partition tables are then CustomersEast and CustomersWest, while a view with a union might be created over both of them to provide a complete view of all customers.”
6. Database sharding partitions the problematic table(s) in the same way, but it does this across potentially multiple instances of the schema. The obvious advantage would be that search load for the large partitioned table can now be split across multiple servers (logical or physical), not just multiple indexes on the same logical server. The difference
7. Reasons to Implement DS • The growth in database transactions and large volumes of data.
 • If you need to move data along databases
 • Applications that have a multi-tenancy approach and want to horizontal scalability.

9. Octopus is a better way to do Database Sharding in ActiveRecord. Sharding allows multiple databases in the same rails application. The API is designed to be as simple as possible. Octopus focuses on the end user, giving the power of multiple databases but with reliable code and flexibility. Octopus is compatible with Rails 4 and Rails 5. Octupus Gem
10. • Sharding (with multiple shards, and grouped shards).
 • Replication (Master/slave support, with multiple slaves).
 • Moving data between shards with migrations.
 Octupus support
11. How Octupus works?
12. ¡ Demo! https://github.com/KarenVentura/database-sharding