Announcing MulletDB (Formerly NoNoSQL)(sheddingbikes.com)
sheddingbikes.com
Announcing MulletDB (Formerly NoNoSQL)
http://sheddingbikes.com/posts/1274762986.html
4 comments
* 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.
* 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.
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.
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.
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.
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.
So... what are the real impacts on a commercial website that uses AGPLed code?
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
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
Actually, I figured if it's AGPL then basically everything has to be AGPL. We'll see how that goes.
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"
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"
[deleted]
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.
Valley Mullet FTW!!
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.