nosql tel aviv meetup #2: nosql at scale - architecture and common pitfalls
TRANSCRIPT
Arthur Gimpell
‹ ›2
About Me
•Working with databases for 8 years
•5 years, SQL Server & .NET
•3 years with NoSQL & Python & Node.js
•2015 - Founded DataZone
Arthur Gimpell
‹ ›3
DataZone | Data is our business! What’s yours?
•Consultancy & projects
•Private & public training
•Multi vendor, multi tier support with SLA
•Child unit of CloudZone, public cloud leaders
NoSQL Why Not?
Arthur Gimpell
‹ ›5
All the wrong reasons…
•Web Scale! Web Scale!
•Costs reduction*
•Free school for developers
Source: mongodb-is-web-scale.com
Common Pitfalls
Arthur Gimpell
‹ ›7
RDBMS Practices
Normalization in the low cost storage era
Arthur Gimpell
‹ ›8
RDBMS Practices
Expecting the Wrong Features
Jobs
Mailing Servers
Queues
TriggersStored
Procedures
Shell
Commands
Arthur Gimpell
‹ ›9
RDBMS Practices
ORM != ODM
Object Relational Mapping - Targets:
•Speeding development.
•Mapping multiple relations to Objects
•Simple Standard CRUD
Object Document Mapper - Targets:
•Managing references & embeddeds
•Typing your data
•Retries, Events, Transactions
Arthur Gimpell
‹ ›10
Architecture
Commodity hardware - over distribution
Cluster 1Cluster 2
Arthur Gimpell
‹ ›11
Architecture
Cluster Majority
A
Cluster 1
B
C
A
Cluster 2
B
Arthur Gimpell
‹ ›12
Summary
Adjust the technology to your needs, not vice versa.
Be aware of your engine’s distribution model, plan your cluster accordingly.
Model your data by the engine’s best practices - read them.
Don’t over size, don’t under size, run performance tests on various deployments.
Databases are made for storing & efficiently manipulating data, not sending emails.
Run Backups! Replication is not a replacement for cold backups.
