Why Startups Should Not Choose NoSQL
The NoSQL hype is omnipresent. And many startups are tempted to go for Cassandra/MongoDB/HBase/Redis/… . Here I’ll argue why they should rather stick to a SQL solution – MySQL or PostgreSQL.
In my previous post about Cassandra I detailed why I decided not to use it. Now, a dozen presentations watched and several dozen articles read later, I can detail why I think it is not generally a good idea.
NoSQL is great for “web-scale”. That is the mantra of NoSQL evangelists. But an important downside of NoSQL solutions, which is mentioned by most sources (twitter, facebook, rackspace) is that in NoSQL (at least for Cassandra and HBase) you must know what will be the questions that you will be asking upfront. You can’t just query anything you like. On the other hand the relational model allows you to define your model and then ask whatever question (query) comes to your mind. And I can bet that a startup does not yet know all the questions it is about to ask its data store.
Another thing is usability. All developers are familiar with SQL and relational model. And startups must get in the public fast. Why bother learning a new paradigm, a new platform, and new tools (if you are lucky to have tools)?
Now let’s get back to the web-scale. A startup does not need web-scale. Really. You are not getting a million users overnight. Twitter didn’t. Facebook didn’t. If things work out you can gradually upgrade your data model to meet the new demands. That’s how twitter and facebook did. They started with MySQL. Oh, by the way – twitter is still using MySQL for the most important thing – tweets. Now, if you have more data than them, you are.. facebook?
So to summarize – don’t sacrifice flexibility and ease of work for some fictional “trillions of petabytes”. If it happens that you need to handle huge amounts of data, it will be in a way that you will be able to restructure your data model. And at a point when you will know what questions you want to ask.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/301743/viewspace-734242/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Why NoSQL Should Be Called "SQL with Alternative Storage Models"SQL
- Why NoSQL?SQL
- Why should we copy blocks rather than retain?BloCAI
- Ten Reasons Why Android Should Support OpenCLAndroid
- What are HANA's models of cloud computing, and which should I choose?Cloud
- WhyASMLIBandwhynot?ASM
- Managing Startups: Best Blog Posts
- How to Choose Size of Datafile on Raw Devicedev
- In Data Guard,choose switchover or failover?AI
- Why TypeScript?TypeScript
- Why React HooksReactHook
- WHY review code?View
- Why Redis 4.0?Redis
- TextInput should be given height
- What database aspects should be monitored?Database
- NoSQLSQL
- How to Determine When an Index Should be Rebuilt?IndexUI
- The ITer should learn more about ITIL
- [ERROR]XX is marked as crashed and should be repairedErrorAI
- [譯] WebAssembly: How and whyWeb
- WhyRedis4.0?Redis
- why use dynamic SQL?SQL
- PostgreSQL DBA(57) - Could not choose a best candidate operatorSQL
- Entity Framework Tutorial Basics(14):Choose development approachFrameworkdevAPP
- 創業公司的點子創意——Ideas for Startups創業Idea
- 聊聊 NoSQLSQL
- NoSQL 初探SQL
- What you should know about JavaJava
- 第1章 Why RustRust
- why app_start startAPP
- why does angular js rockAngularJS
- Why MVC is Better?(翻譯)MVC
- 2 Why Firms Work Together
- Why would a reverse index be useful ?Index
- Why Java is better than .NETJava
- What are Windows ACLs and why are they important?WindowsImport
- erlang學習: why OTP
- 大學生創業指導——A Student’s Guide to Startups創業GUIIDE