April 22, 2006
More on Solid and MySQL?
In a stunningly self-defeating move, my friends at Solid have decided that anything about their already-leaked possible cooperation with MySQL is embargoed.
Indeed, they’ve emphasized to me multiple times that they do not wish me to write about it.
I shall honor their wishes. I hope they are pleased with the sophistication and insight of the coverage they receive from other sources.
Categories: Memory-centric data management, Mid-range, MySQL, OLTP, Open source, solidDB
Subscribe to our complete feed!
Comments
3 Responses to “More on Solid and MySQL?”
Leave a Reply
Search our blogs and white papers
Monash Research blogs
- DBMS 2 covers database management, analytics, and related technologies.
- Text Technologies covers text mining, search, and social software.
- Strategic Messaging analyzes marketing and messaging strategy.
- The Monash Report examines technology and public policy issues.
- Software Memories recounts the history of the software industry.
User consulting
Building a short list? Refining your strategic plan? We can help.
Vendor advisory
We tell vendors what's happening -- and, more important, what they should do about it.
Monash Research highlights
Learn about white papers, webcasts, and blog highlights, by RSS or email. |
-
Recent posts
-
Categories
- About this blog
- Analytic glossary
- Analytic technologies
- Application areas
- Buying processes
- Companies and products
- 1010data
- Ab Initio Software
- Actian and Ingres
- Aerospike
- Akiban
- Aleri and Coral8
- Algebraix
- Alpha Five
- Amazon and its cloud
- ANTs Software
- Aster Data
- Ayasdi
- Basho and Riak
- Business Objects
- Calpont
- Cassandra
- Cast Iron Systems
- Cirro
- Citus Data
- ClearStory Data
- Cloudant
- Cloudera
- Clustrix
- Cogito and 7 Degrees
- Cognos
- Continuent
- Couchbase
- CouchDB
- Databricks, Spark and BDAS
- DATAllegro
- Datameer
- DataStax
- Dataupia
- dbShards and CodeFutures
- Elastra
- EMC
- Endeca
- EnterpriseDB and Postgres Plus
- Exasol
- Expressor
- FileMaker
- GenieDB
- Gooddata
- Greenplum
- Groovy Corporation
- Hadapt
- Hadoop
- HBase
- Hortonworks
- HP and Neoview
- IBM and DB2
- illuminate Solutions
- Infobright
- Informatica
- Information Builders
- Inforsense
- Intel
- Intersystems and Cache'
- Jaspersoft
- Kafka and Confluent
- Kalido
- Kaminario
- Kickfire
- Kognitio
- KXEN
- MapR
- MarkLogic
- McObject
- memcached
- MemSQL
- Metamarkets and Druid
- Microsoft and SQL*Server
- MicroStrategy
- MonetDB
- MongoDB
- MySQL
- Neo Technology and Neo4j
- Netezza
- NuoDB
- Nutonian
- Objectivity and Infinite Graph
- Oracle
- Oracle TimesTen
- ParAccel
- Pentaho
- Pervasive Software
- PivotLink
- Platfora
- PostgreSQL
- Progress, Apama, and DataDirect
- QlikTech and QlikView
- Rainstor
- Revolution Analytics
- Rocana
- salesforce.com
- SAND Technology
- SAP AG
- SAS Institute
- ScaleBase
- ScaleDB
- Schooner Information Technology
- SciDB
- SenSage
- SequoiaDB
- SnapLogic
- Software AG
- solidDB
- Splunk
- Starcounter
- StreamBase
- Sybase
- Syncsort
- Tableau Software
- Talend
- Teradata
- Tokutek and TokuDB
- Truviso
- VectorWise
- Vertica Systems
- VoltDB and H-Store
- WibiData
- Workday
- Xkoto
- XtremeData
- Yarcdata and Cray
- Zettaset
- Zoomdata
- Data integration and middleware
- Data types
- DBMS product categories
- Emulation, transparency, portability
- Fun stuff
- Market share and customer counts
- Memory-centric data management
- Michael Stonebraker
- Parallelization
- Presentations
- Pricing
- Public policy
- Software as a Service (SaaS)
- Specific users
- Storage
- Theory and architecture
- TransRelational
- Uncategorized
-
Date archives
-
Links
-
Admin
Yikes. I wondered about that when writing about it, but I figured that if there’s a press release, and ZDNet picked it up, that it was meant to be out there.
I’ve been an analyst for over 25 years, and I’ve NEVER had an embargo so repeatedly emphasized to me. And no effort was made to separate out what is and isn’t embargoed.
It’s a crying shame, since I suspect I’m literally the only analyst who understands the Solid product line or its potential in open source as well as I do. (Because of the research I’ve done for the forthcoming white paper, in no small part.) And there’s a real case to be made that Solid’s technology is lighter-weight than Ingres or PostgreSQL, and more industrial-strength than any other alternative.
But at this point I don’t expect that line of reasoning to get any significant attention or buzz.
What really burns me up is that I think Solid’s marketers are smart people, who know their craft. But nobody bats 1.000, and they blew this one, badly.
[…] I felt like writing a lot about the great potential fit between MySQL and Solid over the weekend, but Solid didn’t want me to do so. Now, however, I’m not in the mood, so I’ll just say that in OLTP, Solid’s technology is strong where MySQL’s is weak, and vice-versa. E.g., Solid is so proud of its zero-administration capabilities that, without MySQL, it doesn’t have much in the way of admin tools at all. Conversely, I think that many of those websites that crash all the time with MySQL errors would crash less with the Solid engine underneath. (Solid happens to be proud of its BLOB-handling capability, efficiency-wise.) […]