I believe the original subtitle is "Extreme Scale Transaction Processing" . "The NoSQL killer" is kind of childish, nothing is going to kill anything.
sensationalism sells, probably why your "original" link was missed by poster
InfiniSQL
11–20 of 61 posts
Re: InfiniSQL
#12A few things (I'm the author of InfiniSQL)
1) I include keystore-like stored procedures in the source. They do get/set with integer key and string val. I haven't done thorough benchmarking, but I expect them to outperform the other benchmark I've published, which is quite a bit more complex workload
2) (camus2) agreed, nothing ever dies in IT. But roll back the clock a few years. How much noSQL would come into exisence if there was a free xzySQL that scaled across nodes, was fast, etc. I believe the answer is that there'd be very few network-based noSQL for operational workloads if that had been the case.
3) jwatte: Yeah! Jagged edges too!
4) stephen24: Also, I intend to change the license from AGPL to GPL next time I push out some code. No excuse not to try it out.
5) siliconc0w: There's an architectural write-up at High Scalability: http://highscalability.com/blog/2013/11/25/how-to-make-an-in... -- I believe that the actor model architecture is distinct in InfiniSQL.
6) diwu1989: Yes and no. Yes, MemSQL is more mature. No,
(a) I'm not sure how MemSQL scales horizontally (especially since that was a feature added after v1 of their code was released), and,
(b) MemSQL isn't free software
7) itsbits: for now InfiniSQL is mainly for hackers and early adopters--the dependencies are pretty clearly documented but it requires some effort to work with in its current state
Re: InfiniSQL
#13A few things (I'm the author of InfiniSQL) 1) I include keystore-like stored procedures in the source. They do get/set with integer key and string val. I haven't done thorough benchmarking, but I expect them to outperform the other benchmark I've published, which is quite a bit more complex workload 2) (camus2) agreed, nothing ever dies in IT. But roll back the clock a few years. How much noSQL would come into exisen…
Please consider the Apache License or some other license instead of the GPL. There are many organizations that cannot use any flavor of GPL, including LGPL, for legal reasons. You can debate the wisdom of that amongst yourselves, but alas, that's how it is in some places.
(And I really want to try this...)
Re: InfiniSQL
#14So...uh...how does it work? Anyone know if there is an architecture overview somewhere? And why there isn't a link to it on the damn front page?
Front page > Documentation > Overview
It practically is on the front page.
Re: InfiniSQL
#15I'm supposed to use the perl api for user and schema management? Perl holds a special place in my heart, but I'm not too excited about managing my database with it. How about an interactive console?
I'm currently using MySQL, how similar is the SQL syntax?
Re: InfiniSQL
#16A few things (I'm the author of InfiniSQL) 1) I include keystore-like stored procedures in the source. They do get/set with integer key and string val. I haven't done thorough benchmarking, but I expect them to outperform the other benchmark I've published, which is quite a bit more complex workload 2) (camus2) agreed, nothing ever dies in IT. But roll back the clock a few years. How much noSQL would come into exisen…
Please consider the Apache License or some other license instead of the GPL. There are many organizations that cannot use any flavor of GPL, including LGPL, for legal reasons. You can debate the wisdom of that amongst yourselves, but alas, that's how it is in some places. (And I really want to try this...)
I assume these shops have Linux in their environments, including the GNU toolchain. There must be some contradiction somewhere that I'm not aware of.
Based on FSF feedback, I'm going to modify the license to include a Classpath-like exception. The intention is to allow people to write stored procedures that link against infinisql without triggering the copyleft. Only if the source to infinisql itself is modified (and distributed) will the copyleft apply.
I'm curious to know the rationale against the GPL in general (not just the AGPL), and how those shops allow Linux & gnu toolchains in spite of their rule against the GPL.
Re: InfiniSQL
#17I'm supposed to use the perl api for user and schema management? Perl holds a special place in my heart, but I'm not too excited about managing my database with it. How about an interactive console? I'm currently using MySQL, how similar is the SQL syntax?
On backlog to fix. But InfiniSQL is for hackers and early adopters at this stage.
The SQL support is documented (http://www.infinisql.org/docs/index/)
Re: InfiniSQL
#18A few things (I'm the author of InfiniSQL) 1) I include keystore-like stored procedures in the source. They do get/set with integer key and string val. I haven't done thorough benchmarking, but I expect them to outperform the other benchmark I've published, which is quite a bit more complex workload 2) (camus2) agreed, nothing ever dies in IT. But roll back the clock a few years. How much noSQL would come into exisen…
Please consider the Apache License or some other license instead of the GPL. There are many organizations that cannot use any flavor of GPL, including LGPL, for legal reasons. You can debate the wisdom of that amongst yourselves, but alas, that's how it is in some places. (And I really want to try this...)
So many reasons to keep GPL.
They can use GPL just fine, it's just that they don't wanna contribute if they modify it.
Re: InfiniSQL
#19I'm supposed to use the perl api for user and schema management? Perl holds a special place in my heart, but I'm not too excited about managing my database with it. How about an interactive console? I'm currently using MySQL, how similar is the SQL syntax?
On backlog to fix. But InfiniSQL is for hackers and early adopters at this stage. The SQL support is documented ( http://www.infinisql.org/docs/index/ )
Awesome project and a killer concept. No one has been able to really solve relational database scalability yet. I'll have to study the implementation. I was just talking with some friends a few weeks ago about this problem and we concluded that if someone came up with a distributed relational database with decent scalable performance they would be very successful indeed. Will try it out and follow the progress. Hope it takes off.
Re: InfiniSQL
#20I actually thought this was another joke at first...