Delphix 4.1 just came out last week. It may sound only like a point release but there is an amazing amount of new technology:
I’m most excited about Amazon AWS support, Oracle 12c PDB support and developer jet pack , aka Jetstream. More coming on these features in upcoming blogs.
AWS support is super exciting because as a cloud enabling technology, Delphix is a perfect fit for AWS. AWS is currently hosting a replicated Delphix appliance replicating from our labs in Menlo Park. This means that I can provision in minutes into AWS any database linked into the Delphix appliance in our office in Menlo Park. For customers wanting to migrate and/or sync database in the cloud this makes it a breeze. As I’ve blogged before, Delphix replication makes datacenter migration easy, fast and efficient. If I have a source database of 3 TB and 4 clones of the source that I want to move to the new data center then that would be 15 TB of data to move (3 TB x 5 copies – 1 source + 4 clones). In the case of Delphix replication it’s about 1 TB! yes 1/15 the space because Delphix compresses by 1/3 and all the clones use most of the same blocks in the source! Also Delphix comes with masking so if you are using AWS for testing and QA those databases being replicated to AWS can all be masked databases.
If you want to use AWS for your database testing, QA or even for tbings like elastic compute, then how (the heck) are you going to get the data to AWS? Delphix provides that solution, not to mention the speed and agility of using virtualized data in the cloud.
Oracle 12c PDB support
Oracle 12c PDBs are cool. They reduce the memory consumption by about 400MB per database, but what about the storage space? The storage space of clone PDBs is still the full size unless you use Netapp or ZFS storage appliance. Now for anyone on any storage the clone storage can be almost negligible and the memory usage minimum, allowing one to put many databases as PDBs on the same hardware and storage infrastructure. This is awesome for teams of developers and QA who want to spin up a either a PDB for each developer and/or multiple PDBs to to QA and testing in parallel.
Jet stream will get it’s own blog post but for now suffice it to say that Jet Stream is an interface created specifically for developers. Up until now Delphix had self service access through the same interface that a Delphix admin would use. A Delphix admin of course sees more and has access to more than a developer. A developer has their own log in which limits what sources they see, how many virtual databases (VDB) they can create, how much storage they can use etc, but the developers use the same UI to take their actions of spinning up a VDB, represhing, rolling back etc. Now there is a UI made specifically for developers that will graphically show the lineage of their VDBs, allow them to graphically branch VDBs and share those branches with other developers.
Delphix interestingly enough supports any database, but to support any database requires that a user of Delphix manually take a lot of time consuming steps. Delphix automation for supported databases makes all the steps required a few clicks of the mouse. Delphix continues adding automation and management support to more and more databases. Sybase support is awesome for those companies using Sybase and SAP with Sybase.
In past blogs I’ve talked about I/O subsystem benchmarking we’ve been working at Delphix. Now Delphix includes the other half of the performance benchmarking which is built in network latency and throughput benchmarking. The network benchmarking combined with the I/O benchmarking immediately informs us upfront what the performance characteristics of the installation hardware will be before launching into a deployment.