How To Make An Infinitely Scalable RDBMS
highscalability.com
How To Make An Infinitely Scalable RDBMS
1–10 of 92 posts
Re: How To Make An Infinitely Scalable RDBMS
#2GNU AFPL?
Clause 13 is a real pain to deal with when exposing this over the network.
I guess the developer wants to sell a license (like the mysql java client GPL'ing).
Can't blame him, he needs to get paid.
Re: How To Make An Infinitely Scalable RDBMS
#3GNU AFPL? Clause 13 is a real pain to deal with when exposing this over the network. I guess the developer wants to sell a license (like the mysql java client GPL'ing). Can't blame him, he needs to get paid.
MongoDB does this too. I personally think its not too bad - its free for whoever wants to use it, but if you want to modify and use it commercially, you do have to pay.
Re: How To Make An Infinitely Scalable RDBMS
#4[deleted]
Re: How To Make An Infinitely Scalable RDBMS
#5GNU AFPL? Clause 13 is a real pain to deal with when exposing this over the network. I guess the developer wants to sell a license (like the mysql java client GPL'ing). Can't blame him, he needs to get paid.
Hi, gopalv. What samspenc said. My understanding of the AGPL is that only the modifications made to the source code itself of the covered project would need to be opened up (or have a commercial license). Meaning that merely using InfiniSQL won't require you to open source your app. MongoDB has the same license BTW, and lots of people use it without being forced to open their code.
And, yes, I want to get paid somehow--but the AGPL won't stop anybody from using my work how they see fit. But if they modify it and distribute it, then they'll have to comply with the license (or contact me directly for an alternate arrangement).
Re: How To Make An Infinitely Scalable RDBMS
#6I'm a little skeptical:
- a bunch of the novel components (the UPS aware persistence layer, for example) aren't actually built yet
- they're pushing for people to build businesses on it already. I would characterize it as "bleeding-edge with bits of glass glued on", so this doesn't seem entirely honest.
- there's mostly a lot of breathless talk about how great and fast and scalable it is, but no mention of CAP theorem. To boil down their feature set, it's an in-memory RDBMS using the Actor model.
Re: How To Make An Infinitely Scalable RDBMS
#7GNU AFPL? Clause 13 is a real pain to deal with when exposing this over the network. I guess the developer wants to sell a license (like the mysql java client GPL'ing). Can't blame him, he needs to get paid.
Hi, gopalv. What samspenc said. My understanding of the AGPL is that only the modifications made to the source code itself of the covered project would need to be opened up (or have a commercial license). Meaning that merely using InfiniSQL won't require you to open source your app. MongoDB has the same license BTW, and lots of people use it without being forced to open their code. And, yes, I want to get paid someho…
I fully understand what this means and I hope you do get calls about alternate licensing, but remember that people like me do not make these decisions.
I thankfully don't have to - this means I don't need to talk to lawyers about this.
Because AGPL took away the most important bit of unassailable ground I had to argue with when it came to deploying GPL - "Using this code implies no criteria we have to comply to, only if we distribute it".
Clause 12 and 13 - basically took that away from me completely.
Look, I'm not going to tell you what license to use.
But leave me enough room to complain that I have had trouble convincing people that we can use AGPL code in a critical function without obtaining a previous commercial license by paying the developer.
Re: How To Make An Infinitely Scalable RDBMS
#8I'm a little skeptical: - a bunch of the novel components (the UPS aware persistence layer, for example) aren't actually built yet - they're pushing for people to build businesses on it already. I would characterize it as "bleeding-edge with bits of glass glued on", so this doesn't seem entirely honest. - there's mostly a lot of breathless talk about how great and fast and scalable it is, but no mention of CAP theore…
Hi, Alan. Yes, many things are not built yet. Nowhere am I pushing anybody to build their business on it yet, but I am looking for hackers and early adopters/alpha testers. I've gone through pains on every doc that I've created that this is early, alpha, needs lots of work--including the 2nd paragraph of the linked-to article:
"InfiniSQL is still in early stages of development--it already has many capabilities, but many more are necessary for it to be useful in a production environment."
Regarding CAP, I'm not addressing multi-site availability at this stage--I want to get single site fully operational, redundant, and so on.
And, yes, to boil it down, it's an in-memory RDBMS using the Actor model.
The most important feature is that it performs transactions involving records on multiple nodes better than anything. This is the workload that keystores functionally cannot do, and which other distributed RDBMS' suffer under. It's also open source, has over 100 pages of technical docs, and is functional enough for people to pound on with some workloads--but not something to put into production yet.
Re: How To Make An Infinitely Scalable RDBMS
#9In-memory distributed database? VoltDB is already way past 500Ktx/sec on a 12-node cluster.
On their site though, it says no sharding and that it can do these 500Ktx/sec even when each transaction involves data on multiple nodes. Does this performance degrade directly in relation to the number of nodes a tx needs to touch?
A simple, straightforward, wire-level description of how things work when coordinating and performing transactions across would be very useful. There's a lot of excited talk about actors, but nothing that really examines why this is faster, or any sort of technical analysis.
Re: How To Make An Infinitely Scalable RDBMS
#10Earlier quoted context omitted.
Hi, gopalv. What samspenc said. My understanding of the AGPL is that only the modifications made to the source code itself of the covered project would need to be opened up (or have a commercial license). Meaning that merely using InfiniSQL won't require you to open source your app. MongoDB has the same license BTW, and lots of people use it without being forced to open their code. And, yes, I want to get paid someho…
I fully understand what this means and I hope you do get calls about alternate licensing, but remember that people like me do not make these decisions. I thankfully don't have to - this means I don't need to talk to lawyers about this. Because AGPL took away the most important bit of unassailable ground I had to argue with when it came to deploying GPL - "Using this code implies no criteria we have to comply to, only…
Hi, gopalv. I'm glad to talk to you further privately if you wish. You can go to InfiniSQL's site to send me your email, connect on LinkedIn, or whatever: http://www.infinisql.org/community/
I'm not too religious about licensing--if I can get early adopters/contributors, and so on, I'm willing to consider changing the license terms.
I'm looking for open doors.