Whether you are a seasoned developer, a cloud computing enthusiast, or simply curious about the scene, this event is the perfect opportunity to connect with like-minded individuals in Manchester. We have two main talks plus the opportunity for lightning talks of 5-10 minutes again so please contact us on the night or beforehand to get in on the action.
We are back at Bonded Warehouse, thanks to Morson-Edge for hosting again, with food provided by Valarian.
To help you find the venue, the what3words location is hooks.decreased.universally. Make sure to come past the Crystal Maze side and ring the bell for reception.
Agenda
| Time | Description |
|---|---|
| 18:30 | Networking with food and drinks |
| 19:00 | Data Residency Is Not Data Sovereignty: What UK Boards Get Wrong - Arik Fletcher |
| 19:30 | Break |
| 19:45 | Lightning talks - Sign up now or on the night |
| 20:00 | Break |
| 20:15 | Designed to Recover. But Can It Actually Recover? - Anas Khan |
| 20:45 | Break |
| 21:00 | End |
Lightning talks (so far)
- Running K8S on bare metal - Joe Armstrong from LinkPool
- Your AI Model Changed. Is Its Explanation Still True? - Miracle Chukwuma, Osagiede Samuel
-
7:00 PM - 7:30 PM GMT
Data Residency Is Not Data Sovereignty: What UK Boards Get Wrong
in-personMost UK boards believe that storing data in a UK data centre means it is protected by UK law. It does not. This session unpacks the difference between data residency, which is where data physically sits, and data sovereignty, which is who legally controls it. It examines the regulatory and commercial consequences under regimes such as the US CLOUD Act, and sets out what technology and security leaders should actually do to manage the exposure.
Arik Fletcher: https://www.linkedin.com/in/arikf
-
8:15 PM - 8:45 PM GMT
Designed to Recover. But Can It Actually Recover?
in-personCloud-native platforms can improve resilience, but designing for recovery and actually being able to recover are two different things. In this session I'll look at the practical gaps that often sit behind a resilient architecture: DNS, identity, networking, data, third parties, runbooks, ownership and testing. Drawing on real-world disaster recovery and resilience programs, I'll share why component-level resilience doesn't always translate into service-level recoverability, and the questions architects and engineers should be asking before calling a service resilient.
Anas Khan - https://www.linkedin.com/in/anas-khan-46951518
