MemSQL Launches Unlimited Community Edition
blog.memsql.com
MemSQL Launches Unlimited Community Edition
1–10 of 56 posts
Re: MemSQL Launches Unlimited Community Edition
#2Aphyr's posts (taken with appropriate amounts of salt) have become the authority on marketing claims. That said, many solutions are perfectly viable with their shortcomings, but knowing what those shortcomings are is essential.
Re: MemSQL Launches Unlimited Community Edition
#3- fully distributed joins
- native geospatial index and datatypes
- lots of new SQL surface area
- concurrency improvements
- analytic optimizer
- Spark, HDFS, and S3 connectors
Re: MemSQL Launches Unlimited Community Edition
#4Cue "Call me maybe, MemSQL" Aphyr's posts (taken with appropriate amounts of salt) have become the authority on marketing claims. That said, many solutions are perfectly viable with their shortcomings, but knowing what those shortcomings are is essential.
Re: MemSQL Launches Unlimited Community Edition
#5Re: MemSQL Launches Unlimited Community Edition
#6Are there any optimizations or explicit support for proximate ordered joins?
Re: MemSQL Launches Unlimited Community Edition
#7Eric, one of the cofounders, here. happy to answer any questions on MemSQL 4 and the community edition. Some new features in MemSQL 4: - fully distributed joins - native geospatial index and datatypes - lots of new SQL surface area - concurrency improvements - analytic optimizer - Spark, HDFS, and S3 connectors
Re: MemSQL Launches Unlimited Community Edition
#8Eric, one of the cofounders, here. happy to answer any questions on MemSQL 4 and the community edition. Some new features in MemSQL 4: - fully distributed joins - native geospatial index and datatypes - lots of new SQL surface area - concurrency improvements - analytic optimizer - Spark, HDFS, and S3 connectors
What's the catch here? :)
Re: MemSQL Launches Unlimited Community Edition
#9Eric, one of the cofounders, here. happy to answer any questions on MemSQL 4 and the community edition. Some new features in MemSQL 4: - fully distributed joins - native geospatial index and datatypes - lots of new SQL surface area - concurrency improvements - analytic optimizer - Spark, HDFS, and S3 connectors
What's the catch here? :)