Originally released just seven months ago, TransLattice’s Elastic Database (TED), a geographically distributed Relational Database Management System (RDBMS), is getting its second update with v3.0. In addition to the latest SQL sequel, the company also announced that is has joined the Amazon Web Services Partner Network (APN). TED can be distributed across multiple AWS cloud instances, while appearing to the end-user as one cohesive database, which TransLattice said enables exceptional database availability and excellent response time.
“We have now a database that works in the cloud,” said TransLattice CEO Frank Huerta. To be precise, he said the DBMS worked in the cloud previously, but it now works with multiple public cloud providers simultaneously, enabling on-premise and cross-cloud deployment, while retaining the ability to control data location via policy. This helps mitigate the risks concerning outages and vendor lock-in, he said. The Santa Clara, CA-based company was founded in 2007 and officially opened its doors in 2010.
“This is a startup, so it took us a few years to get the product and technology right,” said Huerta. “You get some early feedback and you go back and make it work right. This (V3.0) really is our industrial-strength database.”
After TED’s initial release, analysts Enterprise Management Associates called the company an innovating vendor in the database management space. ‘By enabling a geographically distributed database, TED provides a simple, efficient way to manage disparate operational data stores. Geographical distribution of data – including relational data – is important for enterprise computing and the cloud. TED offers enhancements in system availability, enriched performance for remote users, ease of scalability and data location compliance for technical and database architects.’
EMA said this approach to enterprise and cloud infrastructure results in reduced costs and deployment complexity, while improving system reliability, scalability and response time. TED allows for organizations to select their implementation choices with options in on-premises license, private cloud and public cloud implementations, and reduces operational expenses associated with database administration by automating many of the management tasks associated with a distributed database.
Last month 451 analyst Matt Aslett noted that there is a significant difference between spinning up a relational database in a VMI on the cloud versus deploying a database designed to take advantage of, enable, and be part of, the cloud, i.e. databases on the cloud, not databases of the cloud. ‘To me, a true cloud database would be one designed to take advantage of and enable elastic, distributed architecture.’ In addition to TransLattice, he identified several other companies playing in this space, including NuoDB, GenieDB and somebody called VMware, while Google’s F1 and Spanner projects have legitimized the concept of the globally-distributed SQL database.
‘Either way, the era of the relational cloud database – rather than the relational database on the cloud – has begun.’
Taneja Group analyst Mike Matchett was pretty bullish about the company’s offering. TED database nodes can be TransLattice appliances, virtual machines, cloud based instances, or even all of them at once as access, availability, and performance needs dictate; nodes can be added to the database dynamically, and data will automatically get distributed according to policy or performance needs. ‘The best part is that SQL applications don’t have to be modified or become aware that TED isn’t just the same old local SQL database. Since it drops in, scales easily and cost-effectively, and instantly increases global reach and availability, we think TED will go far.’
Evan Quinn, Senior Principal Analyst, Enterprise Strategy Group, was also optimistic about the D-RDBMS. ‘TED represents three years of research and engineering, and is largely the brainchild of CTO and co-founder Mike Lyle, who was convinced distributed database design could stand an overhaul. The trick to making TED a truly geographically distributed database involved: Ripping and replacing the native (1) storage engine and (2) query processor of Postgres, and (3) adding the intelligent policy management. While TED certainly was designed with Hadoop MapReduce in mind, ESG sees deployments focusing on large OLTP opportunities, starting with the usual vertical suspects for groundbreaking technology, financial services and government.
TransLattice, like many early stage database companies, will lean TED go-to-market mainly on executive committee connections to establish an initial customer base. ESG suspects, however, that the unique aspects of TED will drive a healthy amount of voluntary, inbound leads.’
The transition from company push to customer pull has already started, said Huerta. “Over the past few months, we were going to customers, now they’re calling us. We need to capitalize on that.”
TransLattice has gone back for additional venture capital, which will be primarily devoted to marketing. He said 2013-14 will be very important for the company, with some big installations they’re doing now. “We’ve been through this before… working with key customers… it starts to snowball.”