Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week’s episode, we spoke with Denise Gosnell, chief data officer at Datastax, who is a co-author of the O’Reilly book “A Practitioner’s Guide to Graph Data.” She also graciously wrote a post for us explaining why graph databases are gaining traction in the enterprise. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS senior editor Richard MacManus, and TNS managing editor Joab Jackson. Graph database systems differ from the standard relational (SQL) kind in that they are engineered to more easily capture the relations across different entities. “When you’re looking at your databases, graph databases allow you to model your data more efficiently by using relationships,” Gosnell said. You could capture that relationship information through a series of database joins of separate tables, but eventually, the complexity of this approach would make it prohibitive. “When you look at the full end-to-end complexity for using it in an application or maintaining your code, or updating edges, graph databases are going to make that a lot easier for the full lifecycle and maintenance of that application,” she said.
Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week’s episode, we spoke with Denise Gosnell, chief data officer at Datastax, who is a co-author of the O’Reilly book “A Practitioner’s Guide to Graph Data.” She also graciously wrote a post for us explaining why graph databases are gaining traction in the enterprise.
TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS senior editor Richard MacManus, and TNS managing editor Joab Jackson.
Graph database systems differ from the standard relational (SQL) kind in that they are engineered to more easily capture the relations across different entities. “When you’re looking at your databases, graph databases allow you to model your data more efficiently by using relationships,” Gosnell said.
You could capture that relationship information through a series of database joins of separate tables, but eventually, the complexity of this approach would make it prohibitive. “When you look at the full end-to-end complexity for using it in an application or maintaining your code, or updating edges, graph databases are going to make that a lot easier for the full lifecycle and maintenance of that application,” she said.