Using GraphQL as a Secure Innovation Boundary and data-driven culture driver

Do these scenarios sound familiar?

* "It's hard to innovate; every time we want to access some data we need to talk to multiple teams and wait to get approval."
* "When we access our core data we need to wait for a time-constrained subject matter expert to help us out; the data schema of our core systems is hard to decipher without their help."
* "The easiest way for us to integrate with core systems is via the reporting replica databases, but now all of our systems are tightly coupled and we can't evolve our core systems."
* "Our systems integration landscape is a security nightmare, there is no cross-cutting authorisation or telemetry and we are using shared database credentials between systems that give full access to all the data."

As consultants, we've seen these problems occur commonly across multiple organisations. As it turned out, we were no exception either! We recently realised that these problems we've helped identify and solve for our customers were impacting our business, Telstra Purple, the largest Australian-owned technology services company. To address this, we took our learnings from multiple customer projects and applied them to our business. This involved using GraphQL to implement a Secure Innovation Boundary that we lovingly call Purple Graph!

In this presentation, we will describe how we went about pitching, prototyping, launching and operating Purple Graph. We will cover the learnings we've had along the way (technical and non-technical) and talk about the cultural change that we are starting to drive using this technology.

You'll leave this presentation with an understanding of the people, process and technology changes we were able to drive using this technology as well as our technical and non-technical tips to help you want to roll out a similar change to your organisation.

Kieran Jacobsen

He/Him. Microsoft MVP and GitKraken Ambassador. 🌏 🏳‍🌈 Gay.

Melbourne, Australia

View Speaker Profile