6 ms·

Announcing MulletDB (Formerly NoNoSQL)

40 points by semmons 16y ago

JeffJenkins 16y ago
I don't really understand why I would want to use this. Why wouldn't I just use SQLite3, if that's what's powering the SQL searches? (maybe with a pretty layer on top for external access.) The KV/document stores that have been coming out are trying to address shortcomings, perceived or real, with RDBMSs. I think some explanation of the trade-offs which each part of the "mullet" make and how they would be obviated by this system would be helpful. Right now there are a ton of KV/Document stores as well as SQL databases, and I don't know how this is going to be different or why I should pay attention to this project.
- FraaJad 16y ago
  * DB for persistence, kv for speed and disk for scaling(?). Different parts of your app might fit one of these cases. Why not have them all under one API? * Use protocols to scale, not backends * Single interface to talk to db/kv store and disk * In addition, use an SQL-like interface, if that's what floats your boat. * Moving data between db/kv/disk is a server side operation.
  - zedshaw 16y ago
    Exactly. I'm glad someone's paying attention. Additionally, it's mostly a project I started on a dare that I started liking to hack on. Not really expecting anyone to use it for a while, if ever.
- kez 16y ago
  I don't think anyone else will understand why you would want to use it either. More competition, more innovation, better products for us to use in the future? You probably don't need to pay attention to this project. Did you pay attention to Google when it first launched, or Apple when it made the Newton? If you're not that interested in the database technologies, you can just not pay attention, and hope that it becomes unavoidable if it is truly remarkable in the future.
jqueryin 16y ago
So... does this mean that the MulletDB slogan will be "business on the frontend, party on the backend?"
- vyrotek 16y ago
  I would hope it would be the other way around :)
- FraaJad 16y ago
  Close. It says "SQL For Business, NoSQL For Partay" right on the front page.
sbarre 16y ago
Valley Mullet FTW!!
icey 16y ago
So... what are the real impacts on a commercial website that uses AGPLed code?
- callahad 16y ago
  I am not a lawyer. If Zed does indeed release a Python driver under the MIT license, and you use that, it's essentially no different than using the LGPL in an end-user distributed app. You'd have to make any of your changes to MulletDB available to your end users, but your proprietary code could remain closed. MongoDB takes this approach, and has written more at http://www.mongodb.org/display/DOCS/Licensing http://www.mongodb.org/display/DOCS/Licensing
  - zedshaw 16y ago
    Actually, I figured if it's AGPL then basically everything has to be AGPL. We'll see how that goes.
    - deleted 16y ago
      [deleted]
    - icey 16y ago
      Do you (or anyone, really) know of a place with a decent definition of how AGPL code needs to be treated? I'm not clear about what the line is that says "everything from this point must have its source released" versus "all this stuff is OK to license as you please"
    - callahad 16y ago
      Sort of. Thanks to section 13 in each license, AGPLv3 and GPLv3 code can be combined. You end up keeping the Affero provisions on your work, which should be sufficient protection.

40 points by semmons 16y ago

I don't really understand why I would want to use this. Why wouldn't I just use SQLite3, if that's what's powering the SQL searches? (maybe with a pretty layer on top for external access.) The KV/document stores that have been coming out are trying to address shortcomings, perceived or real, with RDBMSs. I think some explanation of the trade-offs which each part of the "mullet" make and how they would be obviated by this system would be helpful. Right now there are a ton of KV/Document stores as well as SQL databases, and I don't know how this is going to be different or why I should pay attention to this project.

FraaJad 16y ago
* DB for persistence, kv for speed and disk for scaling(?). Different parts of your app might fit one of these cases. Why not have them all under one API? * Use protocols to scale, not backends * Single interface to talk to db/kv store and disk * In addition, use an SQL-like interface, if that's what floats your boat. * Moving data between db/kv/disk is a server side operation.
- zedshaw 16y ago
  Exactly. I'm glad someone's paying attention. Additionally, it's mostly a project I started on a dare that I started liking to hack on. Not really expecting anyone to use it for a while, if ever.
kez 16y ago
I don't think anyone else will understand why you would want to use it either. More competition, more innovation, better products for us to use in the future? You probably don't need to pay attention to this project. Did you pay attention to Google when it first launched, or Apple when it made the Newton? If you're not that interested in the database technologies, you can just not pay attention, and hope that it becomes unavoidable if it is truly remarkable in the future.

jqueryin 16y ago

So... does this mean that the MulletDB slogan will be "business on the frontend, party on the backend?"

vyrotek 16y ago
I would hope it would be the other way around :)
FraaJad 16y ago
Close. It says "SQL For Business, NoSQL For Partay" right on the front page.

sbarre 16y ago

Valley Mullet FTW!!

icey 16y ago

So... what are the real impacts on a commercial website that uses AGPLed code?

callahad 16y ago
I am not a lawyer. If Zed does indeed release a Python driver under the MIT license, and you use that, it's essentially no different than using the LGPL in an end-user distributed app. You'd have to make any of your changes to MulletDB available to your end users, but your proprietary code could remain closed. MongoDB takes this approach, and has written more at http://www.mongodb.org/display/DOCS/Licensing http://www.mongodb.org/display/DOCS/Licensing
- zedshaw 16y ago
  Actually, I figured if it's AGPL then basically everything has to be AGPL. We'll see how that goes.
  - deleted 16y ago
    [deleted]
  - icey 16y ago
    Do you (or anyone, really) know of a place with a decent definition of how AGPL code needs to be treated? I'm not clear about what the line is that says "everything from this point must have its source released" versus "all this stuff is OK to license as you please"
  - callahad 16y ago
    Sort of. Thanks to section 13 in each license, AGPLv3 and GPLv3 code can be combined. You end up keeping the Affero provisions on your work, which should be sufficient protection.