Comments on: Scaling Without A Database http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/ Thoughts from the edge of the 'net Sun, 13 Dec 2009 20:49:21 +0000 http://wordpress.com/ hourly 1 By: François Schiettecatte http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-202 François Schiettecatte Mon, 30 Apr 2007 12:26:12 +0000 http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-202 Jim Aside from the sales pitch (I still approved the comment since I thought Nenest was an interesting idea,) what you are doing there is moving the storage from the web site in question to another place, data still has to be stored somewhere, and any web site which uses Nenest becomes dependent on its availability and scaling capabilities, so the bottleneck problems may well still remain. Jim

Aside from the sales pitch (I still approved the comment since I thought Nenest was an interesting idea,) what you are doing there is moving the storage from the web site in question to another place, data still has to be stored somewhere, and any web site which uses Nenest becomes dependent on its availability and scaling capabilities, so the bottleneck problems may well still remain.

]]> By: Jim http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-184 Jim Mon, 30 Apr 2007 00:57:01 +0000 http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-184 There are some web framework could help to achieve this goal. Nenest is such a tool, with which you don't need host a database on your site, but just use its API, from IFRAME tag to HTML API, and XML API, integrate the data with your pages. There are some web framework could help to achieve this goal. Nenest is such a tool, with which you don’t need host a database on your site, but just use its API, from IFRAME tag to HTML API, and XML API, integrate the data with your pages.

]]> By: François Schiettecatte http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-102 François Schiettecatte Thu, 26 Apr 2007 19:58:23 +0000 http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-102 I agree with you completely, we don't need an RDBMS for every project. If you are going to store key/value pairs, I think that BerkeleyDB is perfectly adequate, and if you are really into SQL, then SQLite may be a good solution. And thank you for your comments. I agree with you completely, we don’t need an RDBMS for every project. If you are going to store key/value pairs, I think that BerkeleyDB is perfectly adequate, and if you are really into SQL, then SQLite may be a good solution.

And thank you for your comments.

]]> By: Robert McIntosh http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-96 Robert McIntosh Thu, 26 Apr 2007 16:31:59 +0000 http://fschiettecatte.wordpress.com/2007/04/25/scaling-without-a-database/#comment-96 I never said any of my thoughts were ground breaking :-) After reading a few comments to my post, I realized that what I was trying to convey didn't quite reach everyone in the way I wanted. I have no issues with relational databases. Don't hate them, don't dislike them. To be honest, what I don't like are tools like Hibernate that try to shield you from said databases. After all, SQL is pretty darn powerful and isn't hard for what most people need to do. Everything that you point out in this post is completely valid. Yes you have to process that XML in some way, yes you need to partition correctly and appropriately. None of that changes with or wihtout a RDMBS (as you mention in your last paragraph). The overall theme of my post was more about do we NEED a relational DB for EVERY app we build. Are there other alternatives that can simplify things? That is where I was going. With that in mind, I'm actually putting my hypothesis to the test very soon and I'll write about it along the way. Regardless, thanks for the comments. You bring up good points that I didn't touch on. I never said any of my thoughts were ground breaking :-) After reading a few comments to my post, I realized that what I was trying to convey didn’t quite reach everyone in the way I wanted. I have no issues with relational databases. Don’t hate them, don’t dislike them. To be honest, what I don’t like are tools like Hibernate that try to shield you from said databases. After all, SQL is pretty darn powerful and isn’t hard for what most people need to do.

Everything that you point out in this post is completely valid. Yes you have to process that XML in some way, yes you need to partition correctly and appropriately. None of that changes with or wihtout a RDMBS (as you mention in your last paragraph). The overall theme of my post was more about do we NEED a relational DB for EVERY app we build. Are there other alternatives that can simplify things? That is where I was going.

With that in mind, I’m actually putting my hypothesis to the test very soon and I’ll write about it along the way.

Regardless, thanks for the comments. You bring up good points that I didn’t touch on.

]]>