DaaS: All content tagged as DaaS in NoSQL databases and polyglot persistence
Thursday, 28 March 2013
Rackspace: BYOD to Your Preferred Storage
While Amazon Web Services approach is bring-your-own-data to our storage and processing solutions, Rackspace’s strategy seems to be “whatever popular NoSQL storage engine you like, we have your back. Just bring your data“.
Last month Rackspace bought MongoDB hosting provider ObjectRocket and now they acquired Exceptional Cloud Service which brings Redis hosting on board.
It’s difficult to say how well is Amazon’s strategy working as the company doesn’t do a lot to get their customers’ case studies out there—I still need to find a list of 10 companies that are using Amazon Dynamo. But this doesn’t mean a thing. On the other hand, I can see Rackspace’s strategy working and getting a lot of traction considering they’re looking after the most popular NoSQL tools.
✚ The Register writes about this acquisition too: Rackspace gobbles Exceptional Cloud Services for Redis smarts. I assume many others are asking the same question:
So, with Redis and MongoDB due to make their way into the Rackspace cloud proper, what other technologies are catching the web hoster turned cloud whisperer’s eyes?
Original title and link: Rackspace: BYOD to Your Preferred Storage (©myNoSQL)
Wednesday, 30 January 2013
The Business of Database as a Service
From a PR announcement about Cloudant’s business results in 2012 :
Cloudant says that during 2012, a year that saw its staff grow to 45 employees, the company’s customer base grew to more than 12,000 multi-tenant customers, counting both free customers, as well as the 50 that pay for its dedicated clusters.
I wholeheartedly hope these results are not indicative for the Database-as-a-Service market. I also wish Cloudant an even better 2013.
I haven’t seen any numbers from major platforms like Amazon Web Services, Heroku, or Rackspace, so if you have any please do share them.
Original title and link: The Business of Database as a Service (©myNoSQL)
Wednesday, 23 January 2013
Neo Technology Is H… Wait, It’s Building Neo4j-As-A-Service
Neo Technology’s hiring announcement is clear about their intention:
“[…] you will be resonsible for building, managing, and maintaining a 24x7 NOSQL Databases-as-a-Service operation […]”
In the graph databases space, OrientDB is offering a hosting solution NuvolaBase, but I have no numbers about their business so far.
Original title and link: Neo Technology Is H… Wait, It’s Building Neo4j-As-A-Service (©myNoSQL)
Sunday, 2 December 2012
Hosted Riak With Riak-On
First let me welcome Riak ON!, the first company planning to offer a hosted Riak solution or Riak-as-a-Service.
Second, I’d like to ask for your help in answering the question that pops into my mind everytime I’m thinking about Data-as-a-Service: leaving aside the benefits of managed services, what are the scenarios in which a Data-as-a-Service can be used when the application layer is not colocated1?
-
A different way to formulate this question is: what apps can tolerate the WAN latency and network failures? Obviously these questions do not apply to services like Amazon Web Services or Heroku or dotCloud which offer you both Data-as-a-Service and a PaaS or IaaS. ↩
Original title and link: Hosted Riak With Riak-On (©myNoSQL)
Thursday, 1 November 2012
The Database World in a Venn Diagram
Infochimps put together a comprehensive Venn diagram of the database world in the TechCrunch article Big Data Right Now: Five Trendy Open Source Technologies
Original title and link: The Database World in a Venn Diagram (©myNoSQL)
Tuesday, 31 January 2012
Where Does Xeround Fit In The CAP Theorem?
Itamar Haber over the Xeround blog:
Q: Is Xeround Inconsistent? Xeround employs a set of majority-based algorithms to facilitate its reading and writing of data from/to multiple, distributed nodes. […] Via the use of these algorithms we are ensured that all access to the data is consistent so inconsistency is not an issue.
Q: Is Xeround Unavailable? There is no single point of failure in Xeround and every component that the system consists of is redundant and replaceable.
Q: Is Xeround Partitioning-Intolerant? Yes, to a certain extent it is.
After reading it, I got the same impression as VoltDB’s John Hugg who commented:
It sounds like you’ve gotten this backwards. According to you, in the face of a network event, the system becomes unavailable, but remains consistent. I think you have partition tolerance, but with reduced availability.
Instead of focusing strictly on the CAP characteristics of a distributed database, one should focus on what is the required behavior for their system and look for the database solution that offers them the guarantees they need.
Original title and link: Where Does Xeround Fit In The CAP Theorem? (©myNoSQL)
via: http://xeround.com/blog/2012/01/xeround-and-the-cap-theorem
Most Popular Articles
- Translate SQL to MongoDB MapReduce
- Tutorial: Getting Started With Cassandra
- CouchDB vs MongoDB: An attempt for a More Informed Comparison
- Cassandra @ Twitter: An Interview with Ryan King
- A Couple of Nice GUI Tools for MongoDB
- NoSQL benchmarks and performance evaluations
- Ehcache: Distributed Cache or NoSQL Store?
- Document Databases Compared: CouchDB, MongoDB, RavenDB
- Quick Review of Existing Graph Databases
- NoSQL Data Modeling