Lenley Hensarling & Marc Linster, EnterpriseDB - #IBMEdge
01. Marc Linster, EnterpriseDB, visits #theCUBE!. (00:17) 02. Lenley Hensarling, Enterprise DB, visits #theCUBE!. (00:29) 03. Background of EnterpriseDB. (00:50) 04. Unpacking Postgres. (01:39) 05. Selling PostgreSQL Database: The Killer Platform. (02:23) 06. The Application Model and Re-Looking at the Database. (05:38) 07. Data Federation: Leave the Data Where it Is. (08:05) 08. EnterpriseDB and the IBM Relationship. (09:00) 09. Oracle, the Cost Component and the Writing on the Wall. (10:10) 10. Amazon: Missing the Hybrid Cloud?. (12:30) 11. Is There a Typical POWER Customer?. (14:20) 12. EnterpriseDB in the IOT Space. (16:13) 13. IBM's Purchase of the Weather Company. (17:36) 14. EnterpriseDB Engagement Model. (18:07) Track List created with http://www.vinjavideo.com. --- --- Experts give insight into the sudden rise of databases | #IBMEdge by Nelson Williams | Sep 22, 2016 If data is the lifeblood of business, then databases are the beating heart. Data must be efficiently cataloged, stored and made available for queries to be of any use; databases perform this function. As the tech world has seen a rise in uses for data, so too has the database world discovered new technologies and fresh ways to deliver faster, cleaner data. To help understand this rise in the power of databases, Dave Vellante (@dvellante), cohost of theCUBE, from the SiliconANGLE Media team, visited the IBM Edge 2016 conference in Las Vegas. There, he spoke to Marc Linster, SVP of Product Development at EnterpriseDB, and Lenley Hensarling, SVP of Product Management and Strategy at EnterpriseDB. PostgreSQL and the open-source example The conversation started with a look into how EnterpriseDB runs its business. Hensarling compared its operation to the open-source model used by Red Hat, Inc., except with Postgres (PostgreSQL) databases. He explained that they take the distribution, add testing and then add some other functionality. Instead of leaving things to the customer, EnterpriseDB tests everything together and gives the customer a package with complete documentation. Linster then added that there’s something they call a “data federation.” Some data should live in specialized databases, but with a data wrapper, they can run queries across these databases without moving the data. He stated that it’s exciting how they can run a fit-for-purpose architecture within an integrated system. “The philosophy is, leave the data where it is,” Linster said. Why now for databases? The discussion then turned toward why databases are suddenly so important. Hensarling pointed out that the application model has changed. Companies have fit-for-purpose database solutions and may have four or five of those. This means more databases. He explained that Postgres is able to fit well in that environment because it doesn’t try to do everything. Instead, it uses data wrappers to project relational database schemes on information in those mixed systems. RELATED: One company's move to get all the medical data they can | #SeizeTheData Hensarling believed that databases are moving to the Cloud, both public and private. This has changed EnterpriseDB’s perspective. Now, the company leaves things in the hands of the customer, allowing them to choose which, and whose, cloud data goes to. He mentioned customers have shown a preference for this bring-your-own-license approach.