This is way cool. Already spinning it up on my AWS clusters. Such a quick setup. Super stoked to us it.
MemSQL Launches Unlimited Community Edition
11–20 of 56 posts
Re: MemSQL Launches Unlimited Community Edition
#12Earlier quoted context omitted.
What's the catch here? :)
http://docs.memsql.com/latest/faq/#what-is-memsql-not-for
It seems like the improvements here are OLAP focused, and welcome ones at that, but the docs and product, if not the marketing, seem to be moving away from operational workloads.
From my interpretation of the docs, there are no "transactions" in the Jim Gray / ACID sense of the word. MemSQL offers transactional semantics with READ COMMITTED isolation. This is not just not SERIALIZABLE, it's also not REPEATABLE-READ or SNAPSHOT-READ.
For example, imagine a two statement transaction where statement 1 reads a counter value and statement 2 increments it. If two users run this transaction at the same time, the counter could lose an increment. This example is trivial and probably could be done in a single statement, but many other read-then-write operations could cause such an inconsistency.
Unless I'm misunderstanding something.
Re: MemSQL Launches Unlimited Community Edition
#13 > The Community Edition is distributed as an executable
> binary and is a free edition of the commercial MemSQL
> Enterprise Edition. You are free to download and use
> MemSQL Community Edition within your organization.
Re: MemSQL Launches Unlimited Community Edition
#14Earlier quoted context omitted.
http://docs.memsql.com/latest/faq/#what-is-memsql-not-for
It seems like the improvements here are OLAP focused, and welcome ones at that, but the docs and product, if not the marketing, seem to be moving away from operational workloads. From my interpretation of the docs, there are no "transactions" in the Jim Gray / ACID sense of the word. MemSQL offers transactional semantics with READ COMMITTED isolation. This is not just not SERIALIZABLE, it's also not REPEATABLE-READ o…
Well if MemSQL supports locks, then you can implement any stronger isolation model using both locks and READ COMMITTED transactions. Do they support row-level locking?
Re: MemSQL Launches Unlimited Community Edition
#15Would love to hear from any existing users on their experiences so far (assuming that's allowed under previous licenses). Choosing a database is one of those decisions where I tend to go with the safest, well known option, but maybe I'm missing out.
Re: MemSQL Launches Unlimited Community Edition
#16Eric, 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
Interesting. We've implemented a metadata layer for HDFS and YARN using NDB (MySQL Cluster) - that also supports READ COMMITTED transactions.
Do you support:
- row-level locking
- independent transaction coordinators at data nodes
- pruned index scans
- network-aware transactions (with user-defined partition keys for tables)
- any asynchronous/event API
?
Re: MemSQL Launches Unlimited Community Edition
#17Earlier quoted context omitted.
http://docs.memsql.com/latest/faq/#what-is-memsql-not-for
It seems like the improvements here are OLAP focused, and welcome ones at that, but the docs and product, if not the marketing, seem to be moving away from operational workloads. From my interpretation of the docs, there are no "transactions" in the Jim Gray / ACID sense of the word. MemSQL offers transactional semantics with READ COMMITTED isolation. This is not just not SERIALIZABLE, it's also not REPEATABLE-READ o…
http://voltdb.com/john-hugg-work-volt is this you at voltdb ?
Re: MemSQL Launches Unlimited Community Edition
#18Eric, 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
Hi Eric!
Not sure if you remember me, but we spoke several (5?) years ago when you guys first started. I was the SAP HANA guy and I think we were talking about the landscape of in-memory solutions back then. First off, congrats on the success so far. Second, a few questions:
- How is MemSQL comparing to HANA and Vertica? My understanding is that MemSQL provides the same infrastructure (columnar in-memory based storage) of those solutions but will run on commodity hardware (HANA for example is hardware-vendor locked).
- One of the interesting topics that has come up in the HANA space is that it's expensive to maintain and scale. Specifically, provisioning new servers for data growth and archiving old data out of memory. Are these issues present at all in MemSQL?
- Lots of your customers seem to be using it for company-specific strategic solutions. Are any using it for operations? (like financial close reporting, or as a transactional DB)
Re: MemSQL Launches Unlimited Community Edition
#19Earlier quoted context omitted.
http://docs.memsql.com/latest/faq/#what-is-memsql-not-for
It seems like the improvements here are OLAP focused, and welcome ones at that, but the docs and product, if not the marketing, seem to be moving away from operational workloads. From my interpretation of the docs, there are no "transactions" in the Jim Gray / ACID sense of the word. MemSQL offers transactional semantics with READ COMMITTED isolation. This is not just not SERIALIZABLE, it's also not REPEATABLE-READ o…
seg-fault: Yep. That's me. You could take what I say with a skeptical eye because I work on a competing system, but it increasing appears that that's not actually true.
VoltDB for transactions and ingestion-time analytics and MemSQL for deeper analytics might be a neat combo system. YMMV.
Re: MemSQL Launches Unlimited Community Edition
#20 > While you are free to use Community for your projects,
> MemSQL does not support or endorse using it in production.
Ehhh. Do they mean that the Community Edition is only usable for development?