Comments on: An interesting new player in the Database world http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/ Thu, 10 Sep 2009 20:01:25 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: ProjectX Blog » Blog Archive » Digest - Xlinks 16/2/08 http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/comment-page-1/#comment-27 ProjectX Blog » Blog Archive » Digest - Xlinks 16/2/08 Sat, 16 Feb 2008 00:04:07 +0000 http://www.webalis.com/2008/02/09/an-interesting-new-player-in-the-database-world/#comment-27 [...] new player in the database market - Bigtable Added on 02/12/2008 at 10:33AM new player in the database market - Bigtable [...] [...] new player in the database market – Bigtable Added on 02/12/2008 at 10:33AM new player in the database market – Bigtable [...]

]]> By: Interesting Links of the week(Feb 15th 2008) « Rambling http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/comment-page-1/#comment-26 Interesting Links of the week(Feb 15th 2008) « Rambling Fri, 15 Feb 2008 13:16:31 +0000 http://www.webalis.com/2008/02/09/an-interesting-new-player-in-the-database-world/#comment-26 [...] 1.An interesting new player in the Database world. 2.Years of Experience Does Matter. 3.Java SE 6 Update N(Formerly consumer JRE) Early Access. 4.JSR 666: Solving Java’s Problems. 5.First make it right. Then make it fast. 6.Reflection in Action. 7.GWT-Ext 2.0 released. [...] [...] 1.An interesting new player in the Database world. 2.Years of Experience Does Matter. 3.Java SE 6 Update N(Formerly consumer JRE) Early Access. 4.JSR 666: Solving Java’s Problems. 5.First make it right. Then make it fast. 6.Reflection in Action. 7.GWT-Ext 2.0 released. [...]

]]> By: Thierry http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/comment-page-1/#comment-25 Thierry Mon, 11 Feb 2008 23:09:23 +0000 http://www.webalis.com/2008/02/09/an-interesting-new-player-in-the-database-world/#comment-25 <blockquote> I don’t think you’d be able to use this database system to replace PostgreSQL or MySQL, Thierry. I’m sure for some applications, it would work well but you wouldn’t be able to (AFAICT) join tables and perform complex queries because the model they expose is not relational. </blockquote> It's not exactly the idea I had in mind... My idea was more to have several databases nodes (I would call them "grapes") that where independent, and that would be able to replicate to another "grapes". A bit like a peer2peer sharing software works, aggregating several clients. As I stated, I've designed a web page screenshoting service (waiting for a real server to be up before announcing it, I don't want to hammer my virtual server), and I specifically thought about the picture storage here. I imagined that having independant implementations that would do the capture, and store the picture in a distributed database would allow A) To have independant nodes that can serve request B) To allow the exchange of cached shots between several grapes, to lighten the resources. I'm nowhere near this, but thinking about it is something that makes me wonder if anything like this exists today. The more I read about it, and I try to visualize how to implement it, the more I see that's is a very specialized area, and it would not work the way I would like, but this makes me wonder nonetheless... It especially remembers me of <a href="http://www.peercast.org/" rel="nofollow">PeerCast</a> which would relay web-radios streaming through the gnutella peer2peer network protocol. The idea was really good, and I liked it very much. It was a bit of bitTorrent before it's time, distributing radio bandwidth between it's listener.

I don’t think you’d be able to use this database system to replace PostgreSQL or MySQL, Thierry. I’m sure for some applications, it would work well but you wouldn’t be able to (AFAICT) join tables and perform complex queries because the model they expose is not relational.

It’s not exactly the idea I had in mind…
My idea was more to have several databases nodes (I would call them “grapes”) that where independent, and that would be able to replicate to another “grapes”.
A bit like a peer2peer sharing software works, aggregating several clients.

As I stated, I’ve designed a web page screenshoting service (waiting for a real server to be up before announcing it, I don’t want to hammer my virtual server), and I specifically thought about the picture storage here.
I imagined that having independant implementations that would do the capture, and store the picture in a distributed database would allow
A) To have independant nodes that can serve request
B) To allow the exchange of cached shots between several grapes, to lighten the resources.

I’m nowhere near this, but thinking about it is something that makes me wonder if anything like this exists today.

The more I read about it, and I try to visualize how to implement it, the more I see that’s is a very specialized area, and it would not work the way I would like, but this makes me wonder nonetheless…

It especially remembers me of PeerCast which would relay web-radios streaming through the gnutella peer2peer network protocol.
The idea was really good, and I liked it very much.
It was a bit of bitTorrent before it’s time, distributing radio bandwidth between it’s listener.

]]> By: sharvil http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/comment-page-1/#comment-22 sharvil Mon, 11 Feb 2008 17:36:07 +0000 http://www.webalis.com/2008/02/09/an-interesting-new-player-in-the-database-world/#comment-22 It looks like they're leveraging the <a href="http://hadoop.apache.org/core/" rel="nofollow">Hadoop</a> infrastructure for this project. It's nice to see such large-scale open-source projects implementing systems that have proved successful in the industry. I don't think you'd be able to use this database system to replace PostgreSQL or MySQL, Thierry. I'm sure for some applications, it would work well but you wouldn't be able to (AFAICT) join tables and perform complex queries because the model they expose is not relational. In fact, you'd even lose constraints on columns and referential integrity. I think Bigtable and HyperTable are attempts at solving a smaller, specialized set of problems in a more efficient way than a relational database. It looks like they’re leveraging the Hadoop infrastructure for this project. It’s nice to see such large-scale open-source projects implementing systems that have proved successful in the industry.

I don’t think you’d be able to use this database system to replace PostgreSQL or MySQL, Thierry. I’m sure for some applications, it would work well but you wouldn’t be able to (AFAICT) join tables and perform complex queries because the model they expose is not relational. In fact, you’d even lose constraints on columns and referential integrity. I think Bigtable and HyperTable are attempts at solving a smaller, specialized set of problems in a more efficient way than a relational database.

]]> By: Amit http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/comment-page-1/#comment-24 Amit Mon, 11 Feb 2008 15:55:43 +0000 http://www.webalis.com/2008/02/09/an-interesting-new-player-in-the-database-world/#comment-24 Hypertable is still in Alpha release Hypertable is still in Alpha release

]]> By: Forrest http://www.webalis.com/2008/02/an-interesting-new-player-in-the-database-world/comment-page-1/#comment-23 Forrest Sun, 10 Feb 2008 03:32:40 +0000 http://www.webalis.com/2008/02/09/an-interesting-new-player-in-the-database-world/#comment-23 Truly high-scale database applications are in a league of their own. We've been having trouble with distributed queries in SQL Server not being delegated to the foreign server to perform joins. Instead an entire table is copied into temporary storage and parsed using a table scan. We've been starting to do some innovating things to fight the issue ... but that distracts you from writing the actual functionality you're working on. I'm very eager to hear the results of your testing. Truly high-scale database applications are in a league of their own. We’ve been having trouble with distributed queries in SQL Server not being delegated to the foreign server to perform joins. Instead an entire table is copied into temporary storage and parsed using a table scan. We’ve been starting to do some innovating things to fight the issue … but that distracts you from writing the actual functionality you’re working on.

I’m very eager to hear the results of your testing.

]]>