I'm working through Google Drive/Dropbox systems design and I'm struggling specifically with consistency with the metadata DB once we need to horizontally scale. We need consistency so ACID RDBMS makes sense (and document metadata is highly relational so it also makes sense there as well).
But doesn't the baked in benefit of consistency start to go away when we have to shard an RDBMS for scale/location/speed reasons? Looking for some insight into how this might scale out.
(Also, I realize we could use Cassandra with replication mode favoring consistency, but I'm really trying to get my head around the RDBMS solution to properly defend it) #sysdesign #software #engineering
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
Flagged by the community.