Andrew Davidson (SVP Products, @MongoDB) talks about MongoDB's evolution from a software company to a cloud services company (MongoDB Atlas), how developers traditionally interacted with databases, and the need for Developer Data Platforms going forward.
SHOW: 671
CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw
CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"
SHOW SPONSORS:
SHOW NOTES:
Topic 1 - Welcome to the show. Let’s talk about your background, and what you focus on at MongoDB.
Topic 2 - Data is a weird beast. It’s cheap to create, it’s expensive to move, and it’s complicated to use because there’s so many ways to interact with it depending on the use-case. So for someone that thinks about data a lot, how do you frame up the challenges of how applications interact with data?
Topic 3 - People tend to think about MongoDB as a database company, and then a Cloud database company. What did the company learn as it moved to the cloud, as a lot of barriers for developers got knocked down in that transition?
Topic 4 - As a developer today, do I still need to think about the relationship between the underlying data and the database access model needed to make that useful to an application, or are any of those lines blurring or going away?
Topic 5 - Databases have traditionally followed the CAP theorem, and different choices have different strengths and tradeoffs. As you start to think about this concept of developer data platform, how do you try and reframe those tradeoffs? Do any of them go away?
Topic 6 - What are some examples of how companies and their developers are able to think differently about how their new applications can be built with this new platform approach to data?
FEEDBACK?
FEEDBACK?