Over the past two years, we have seen a dramatic shift in Jupyter’s deployment, from ad hoc usage by individuals to production enterprise application at scale. Today, Jupyter is used across thousands of enterprises, including Fortune 500 companies, international research facilities, universities, and startups. This adoption has been driven by enterprises embracing data science and machine learning at all levels of operation and product development.
Brian Granger explains how this has expanded the Jupyter community and revealed new use cases with new challenges and opportunities, as he explores the Jupyter ecosystem from the perspective of enterprise use cases. You’ll discover the core value propositions and risks for enterprises adopting Jupyter and open source in general, how Jupyter is evolving to address enterprise use cases, and how organizations can engage the Jupyter community in a productive manner to best leverage their investment in open source. Particular areas of focus include large-scale collaboration, working with sensitive data (GDPR, HIPAA, FERPA, proprietary data, etc.), and scaling Jupyter deployments within complex enterprises.
This talk sets the stage for the rest of the JupyterCon Business Summit by framing relevant questions to be addressed in subsequent talks, a roundtable discussion, and unconference sessions. Be sure to join in.
Brian Granger is an associate professor of physics and data science at Cal Poly State University in San Luis Obispo. Brian is a leader of the IPython project, cofounder of Project Jupyter, and an active contributor to a number of other open source projects focused on data science in Python. Recently, he cocreated the Altair package for statistical visualization in Python. He is an advisory board member of NumFOCUS and a faculty fellow of the Cal Poly Center for Innovation and Entrepreneurship.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com