ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

DaaS: All content tagged as DaaS in NoSQL databases and polyglot persistence

Standalone Heroku Postgres’ Unanswered Question

While the offer is clear and valuable in itself:

  • 99.99% uptime
  • 99.999999999% (eleven nines) durability
  • read-only asynchronous replicas
  • database cloning

I’ve been reading all posts about the announcement looking for the answer to the most obvious question: why would you use Heroku’s Postgres service from outside the Heroku platform?

As far as I can tell:

  • the network latency will be significant
  • network partitions will occur (more often than having both you application and data in the same DC)
  • transfer costs will be significant

So what is the answer?

Media coverage :

Original title and link: Standalone Heroku Postgres’ Unanswered Question (NoSQL database©myNoSQL)


Traditional SQL DaaS vs NewSQL

Mike Hogan (CEO ScaleDB) provides some very valid issues with traditional relational databases operating as Databases-as-a-Service:

When moving from a self-managed database—either in the cloud or on premise—to a DaaS, the “DBA-in-the-cloud” doesn’t have that visibility into the business requirements, performance requirements, development schedule, and more. This lack of visibility turns the already challenging task of hand-tuning the database into a near impossibility using traditional databases.

And these are just the most visible ones.

On the other hand, I totally agree with Markus ‘maol’ Perdrizat pointing out that NewSQL is not the only solution to these problems:

I agree with the problem positioning, but feel strongly that NewSQL is not a requirement to address the problem here, you can equally work a little services layer and put all the control into the hands of the user, essentially replacing (a lot of) the DBA tasks with automation and APIs.

What NewSQL gives you though, and we see that with Xeround and supposedly also ScaleDB, is the elasticity and transparent sharding that’s difficult to achieve with the more traditional Oracle, Sybase or SQL Server databases that are still often required in the enterprise space.

Original title and link: Traditional SQL DaaS vs NewSQL (NoSQL database©myNoSQL)

via: http://scaledb.blogspot.com/2011/09/lack-of-business-visibility-cripples.html


Hadoop-Enabled SOA Architectures

John Akred (data and platforms lead at Accenture Technology Labs) for ZDNet:

We take the data infrastructure layer, and take data stores like Hadoop, and the existing enterprise systems that give that data valuable context and integrate those at the data layer. And we abstract that integrated data platform from the consuming applications via service-oriented data access patterns. So we’re exposing our enterprise data platform to the enterprise via services rather than direct query access.

Service oriented architectures aren’t new. But realizing the abstraction of the applications from the data layers via service oriented architectures has not been easy, and in many cases enterprises end up essentially implementing point to point interfaces over service oriented architectures. When you get to the data platform view, its really important to build well-known web services that enable data access, so that application developers are no longer having to understand the performance characteristics and implementation of a database.

This sounds more like data-centric architecture or if you want Data(base)-as-a-Service. Hadoop can be indeed an important part of a Data(base)-as-a-Platform solution on its analytic side.

Original title and link: Hadoop-Enable SOA Architecture (NoSQL database©myNoSQL)

via: http://www.zdnet.com/blog/service-oriented/service-oriented-architectures-role-in-the-emerging-hadoop-world/7880


Google Launches Google Cloud SQL a Relational Database as a Service

Google has just announced a new (lab) product: Google Cloud SQL which is Google’s Database-as-a-Service version of Amazon RDS—based on initial information, Google Cloud SQL could be characterized as a very basic/intro version of Amazon RDS.

Main features listed in the announcement:

  • Managed environment
  • High reliability and availability - your data is replicated synchronously to multiple data centers. Machine, rack and data center failures are handled automatically to minimize end-user impact. It also support asynchronous replication
  • Familiar MySQL database environment with JDBC support (for Java-based App Engine applications) and DB-API support (for Python-based App Engine applications). It even support data import and export using mysqldump
  • Simple and powerful integration with Google App Engine.
  • Command line tool
  • SQL prompt in the Google APIs Console

The service is free for now and Google promises a 30 days notice without giving any hints on the pricing model though.

Original title and link: Google Launches Google Cloud SQL a Relational Database as a Service (NoSQL database©myNoSQL)


CloudSpokes: From Microsoft Azure to Database.com

CloudSpokes, an Appirio-led community rearchitected their solution from Windows Azure to Salesforce’s Database.com:

Initially, Messinger said, his team was really happy with Windows Azure’s table storage and blob storage features, but trouble arose when it came to deploying computing resources called “Web Roles.” […]

Additionally, said Messinger, Windows Azure required some level of database-administration know-how, which is something the CloudSpokes didn’t really want to deal with. It wanted to focus on the front end and other business-critical aspects rather than on DBA work. So it looked to Database.com, and Messinger and Singh haven’t looked back since beginning the transition in mid-July.

This is the first time I’m reading a scenario where DaaS (database as a service) is explicitely mentioned as the main reason for migrating the architecture of an application.

Original title and link: CloudSpokes: From Microsoft Azure to Database.com (NoSQL database©myNoSQL)

via: http://gigaom.com/cloud/cloud-breakup-why-cloudspokes-chose-database-com-over-azure/


The Future of Cloud Services: IDC Report

An IDC Report about the impact of cloud computing on the IT market:

In 2015, public cloud services will account for 46 percent of net new growth in overall IT spending in five key product categories – applications, application development and deployment, systems infrastructure software, basic storage, and servers, according to the report.

Software-oriented cloud services (SaaS) will account for roughly three quarters of all spending on public cloud IT services throughout the forecast. This includes all three software-oriented cloud categories, not just applications. Spending on hardware-oriented cloud services (servers and storage) will be largely driven by SaaS providers building out their infrastructure.

If I read this correctly, there’s now word about Database-as-a-Service.

Original title and link: The Future of Cloud Services: IDC Report (NoSQL database©myNoSQL)

via: http://www.eweek.com/c/a/Midmarket/IT-Cloud-Services-Spending-to-Reach-729-Billion-in-2015-IDC-Report-547901/


About the MongoLab, MongoDB DaaS, Investment

MongoLab’s offering capitalizes on two important trends we see impacting the vast majority of our portfolio companies:  the rapid adoption of the cloud deployment model and and the increasing use of “Big Data” and NoSQL tools. […] Of the many offerings in the “Big Data” and NoSQL universe, we like the fact that MongoLab has chosen to specialize in 10gen’s MongoDB.  MongoDB’s scalability (in size and read/write volume), its ability to run MapReduce jobs and its accelerating adoption among developers are all compelling aspects of the MongoDB platform.

MongoDB adoption is great.

Original title and link: About the MongoLab, MongoDB DaaS, Investment (NoSQL databases © myNoSQL)

via: http://www.foundrygroup.com/wp/2011/05/our-investment-in-mongolab/


Dealmaker Media: Data-as-a-Service Startups

If you are one of the many people out there searching for database solutions, we have found five companies that are providing answers to all your database problems in unique and innovative ways.

  • Akiban
  • Clustrix
  • Hadapt
  • NimbusDB
  • RethinkDB

Let’s see:

  • Akiban: features a video and requires joining a Design Partners Program(?)
  • NimbusDB: has no release yet even if it is in the works for a couple of years
  • Hadapt: launched two weeks ago (nb: Daniel Abadi has been working on HadoopDB for a while though)
  • RethinkDB: is in private beta

Don’t confuse PR messages for a promise and promises for reality.

Original title and link: Dealmaker Media: Data-as-a-Service Startups (NoSQL databases © myNoSQL)

via: http://www.undertheradarblog.com/blog/data-as-a-service-announcing-our-seventh-group-of-startups/


Forrester report: SQL Azure Raises the Bar on Cloud Databases

Got the link to this Forrester report about SQL Azure (PDF) authored by Noel Yuhanna from the SQL Azure - The Year in Review:

Most customers stated that SQL Azure delivers a reliable cloud database platform to support various small to moderately sized applications as well as other data management requirements such as backup, disaster recovery, testing, and collaboration. Unlike other DBMS vendors such as IBM, Oracle, and Sybase that offer public cloud database largely using the Amazon Elastic Compute Cloud (Amazon EC2) platform, Microsoft SQL Azure is unique because of its multitenant architecture, which allows it to offer greater economies of scale and increased ease of use. […] Application developers and database administrators seeking a cloud database will find that SQL Azure offers a reliable and cost-effective platform to build and deploy small to moderately sized applications.

There are a couple of inconsistencies in the document, but the SQL Azure case studies section is worth reading.

Back to the fun part. In the pros section:

High availability at no extra effort or cost. […] In addition, SQL Azure automatically offers built-in server and storage redundancy, a data replication solution for built-in high availability, and transparent application failover to ensure minimal disruption.

The cons section:

Zero downtime availability. Although SQL Azure supports failover architecture should a database server fail, there is some downtime, ranging from a few seconds to minutes, associated with switching the application over to another server.

Back to pros:

Scale-out capacity growth via a sharded data platform. SQL Azure offers the ability to shard data into hundreds or even thousands of logical databases, which developers can use collectively for a given application.

and in the cons:

Automatic sharding of data for extreme scalability. SQL Azure does not automatically shard data into various partitions to scale across physical servers.

Just focus only on the three case studies included in the paper (PDF).

Markus ‘maol’ Perdrizat

Original title and link: Forrester report: SQL Azure Raises the Bar on Cloud Databases (NoSQL databases © myNoSQL)