With Amazon Web Service’s re:Invent 2015 conference taking place this week, there’s been a steady stream of cloudy news releases, with new additions from both Elastic (formerly ElasticSearch) and MariaDB cropping up in the feeds.
The Elastic collaboration comes in the form of a new Amazon Elasticsearch Service (Amazon ES for short). Developers can quickly launch scalable Elasticsearch cluster from the AWS Management Console, point clients to the cluster’s endpoint, and start to load, process, analyze, and then get speedy data visualisation.
Writing on the official Amazon blog, Jeff Barr outlined the motivation for joining forces with the Lucene based search server, commenting, “Elasticsearch is a real-time, distributed search and analytics engine that fits nicely into a cloud environment. It is document-oriented and does not require a schema to be defined up-front. It supports structured, unstructured, and time-series queries and serves as a substrate for other applications and visualization tools including Kibana.”
On the MariaDB front, AWS have introduced the open source MySQL compatible database to the latest offering of AWS RDS as a fully managed service. This includes 6TB of storage, 30,000 IOPS, and support for high-availability deployments. Until now, Amazon has offered support for MySQL, Oracle, SQL Server, InnoDB and PostgreSQL – this addition brings the roster up to six. Amazon will be using the community version of MariaDB in this case.
If you’re on one of these databases and considering porting across to Amazon, the good news is that, thanks to the new AWS Database Migration Service, it’s now easier to migrate on premise database engines to run on AWS. You can also use this solution to migrate from proprietary engines running on-premises to open source engines running in AWS. The service can be used as a one-time proposition, or to maintain continuous replication between databases without the need for software installation or tricky configuration.