5 ms·
The current database debate and graph databases
- leandro 18y agoÐis is ſtupid. People condemn ðe relational model for SQL limitations, but SQL is not relational at all.
- TweedHeads 18y agoThe relational model is perfect, what is not is the rigid implementation of it by sql vendors. Oracle offers object views and graphs and a million different ways of storing and retreiving data. Compare that to mysql and it feels like riding a bike over railtracks.
- Femur 18y agoAs an Oracle DBA by profession, I agree with you 100%. The Oracle product is more than 30 years old and extremely refined and developed. It can do amazing things when used properly.
- gnaritas 18y agoYes, it's particularly good at emptying your wallet.
- pj 18y agoOracle is awesome. There are lots of good database products out there. People laud map/reduce and all those fancy new toys because it makes sites easier to scale. For 99% of websites out there, traditional RDBMS's are plenty scalable enough and they give you vastly greater options for data analytics, roll ups, record locking, indexing, etc... Gotta pick the right tool for the right job. The problem with this article is that it is written for the general audience, but the general audience will never get into a scalability issue where a traditional RDBMS won't perform exceptionally well.
- bdfh42 18y agoAt the moment, the demand for highly scalable post relational (can we say) databases is fairly limited although with many governments now keen to try and store every email, phone conversation and Internet browsing session of their populace perhaps the demand is going to increase in the near term. It is my view that the RDBMS has a lot of life in it yet - indeed it's effective penetration is still woefully low. Far too many businesses have no coherent database in place and rely upon piecemeal record keeping and ad hoc processes just to manage day to day transactions. Perhaps we need even better relational solutions before we need post-relational ones.
- davidmathers 18y ago"post relational (can we say)" I think you meant to say "pre-relational"
- jrockway 18y agoThis doesn't really mean much. The computer science collective loves to ignore good ideas for many decades. How many mainstream languages integrate 50-year-old ideas like macros? (Also, look how long it took for people to realize that things like garbage collection and virtual machines were good ideas.)
- Retric 18y agoPeople who don't understand databases theory complain, news at 11. it isn't helpful when the data model evolves over time No, poorly designed and maintained databases have issues, but that's a developer problem not a database problem. SQL is highly flexible and you can dynamically update the database format at run time which few "modern" languages let you do. IMO, The problem is developers who think OOP means all data must map 1 to 1 with an object which manipulates that data and then complain that the database is now tightly coupled with their code. As to scalability it's that's a software problem that has little to do with the relational model. A link's to B and B is somewhere out in the cluster works just fine. You can even write a relational engine that uses a key value store to keep the records. PS: I like to think of it as Java/C++/whatever infecting the database.
- Femur 18y agoHere here! Well worded! This argument about the relational model have been coming up for years and I see articles like this all the time. The fact is that RDBMSs work great when properly implemented and maintained. They are very commonly used and are not going away any time soon.
- jrockway 18y agoThe fact is that RDBMSs work great when properly implemented and maintained. Programs written in assembly also work great when they are properly implemented and maintained. The thing is, properly implementing and maintaining it is difficult and time-consuming. Alternatives to assembly made implementing and maintaining software easier; why do you think that this won't happen with databases? (I consider RDBMSs as "assembly" because everyone thinks they can solve every problem. But you have to work at a very low-level to solve certain kinds of problems with a relational database. Something higher-level is an improvement, even if it isn't "necessary". You can write your Web 2.0 app in CPU microcode, but you probably shouldn't.)
- dasil003 18y agoThat's not really a fair comparison though. There's no parity mismatch between assembly and high level languages. Sure assembly opens a few doors for optimization, but you don't give up any fundamental logic when you move to a higher level language. As for RDBMS, well, they have scaling issues because of the rich functionality they provide, and some queries can definitely be tricky for the same reason. However conceptually they are much more straightforward than assembly, and offer a very pure data model with more overall utility than any of the alternatives. That's not to say that we don't need alternative data stores for some applications. But I do want to go on record as saying this article is a mixture of hype and FUD. RDBMS' have been challenged for decades by alternative supposedly-superior technologies. I think the problem is that no model is as comprehensive as the relational model. It's trivial to write a faster database providing some subset of SQL. You can even reduce the parity mismatch to some languages by making it store objects more directly. That's great, but I have yet to see any serious challenge to the relational model's stengths, instead all I see is hype and tutorials about how to convert some simple query to map-reduce.
- spot 18y agoan interesting & open graph database from danny hillis & co: http://www.freebase.com http://www.freebase.com http://www.freebase.com/view/freebase/faq http://www.freebase.com/view/freebase/faq http://www.freebase.com/view/en/creating_types_and_properties http://www.freebase.com/view/en/creating_types_and_propertie...
- arohner 18y agoOften I wonder if people are attacking the wrong problem. Personally, my "DB" problems mostly revolve around SQL the language, as opposed to the RDBMS model. SQL is a piss poor language for what most developers want to accomplish. 1) SQL queries are not composable, and it's a bear to make more complex queries by building on top of existing queries. i.e. I have a query to find all customers who live in CA. Now I want to find the list of customers who live in CA and bought product Foo in the last year. There are many tools like ActiveRecord and SQLAlchemy that attempt to sweep some of the complexity under the rug, but nothing comes close to covering it in the general case, and once it breaks you're back to writing SQL by hand. I blame the complexity of the language syntax. 2.) The SQL model is declarative, which is nice when it works, but really sucks when it doesn't. Being able to look at a query and know whether it is fast or not depends highly on your DB vendor and product version, and is basically impossible without the EXPLAIN command. Writing efficient SQL requires you know that your vendors optimizes this command, but not that command, but only in versions 8.2 and later. 3.) Sometimes, I really really want to call map, filter and reduce on my dataset to write my own queries. In some cases, it is much simpler than a page of SQL. Yes, this isn't purely relational, but I don't care. I want fast, simple access to my data, and preferably in the same language I'm using for development . No programming paradigm (imperative, OO, declarative, functional) is perfectly applicable in all situations. So why does SQL declare that declarative style is the One True Way to get access to your data?
- deleted 18y ago[deleted]