Unconference: Designing Modern Reliable Architectures

What is an unconference?

An unconference is a participant-driven meeting. Attendees come together, bringing their challenges and relying on the experience and know-how of their peers for solutions. A professional facilitator is also there to help keep the discussion moving forward, but where it goes is up to the participants.

It's a facilitated peer group that avoids the hierarchical aspects of a conventional conference, such as a top-down organization. Only the broad themes are predetermined. Everything else is just space for attendees to sound off ideas together, relate to shared challenges and rewards, and identify new ideas and goals. 

Our unconference sessions have been based on the Open Space Technology and Lean Coffee format since 2006.

Why are we doing unconference sessions?

We have designed QCon for senior software practitioners. That role comes with demanding challenges and complex problems. 

Connecting with your peers in a structured environment allows you to:

  • Broaden your perspective with the benefit of the experience of others.
  • Challenge how you've been doing things by breaking out of your bubble.
  • Learn from peers who have already overcome the challenges you're facing now.
  • Benchmark your solutions against other teams and organizations.
  • Get real-world perspectives on challenges that might be too novel or specific to find solutions in books or presentations.
  • Validate your technical roadmap with real-world research.
  • Connect with others like you and build relationships that go beyond the event.

Date

Wednesday Jun 14 / 11:50AM EDT ( 50 minutes )

Location

Carroll Gardens

Video

Video is not available

Slides

Slides are not available

Share

From the same track

Session Architecture

Reliable Architectures Through Observability

Wednesday Jun 14 / 02:55PM EDT

We want our systems to be reliable, but testing alone isn't enough. In a complex, multi-service system, it's impossible to test your way to correctness. That's why we need observability. Observability is the ability to see what our code is doing, in production and in development.

Speaker image - Kent Quirk

Kent Quirk

Staff Engineer @Honeycomb.io

Session Kafka

How to Build a Reliable Kafka Data Processing Pipeline, Focusing on Contention, Uptime and Latency

Wednesday Jun 14 / 10:35AM EDT

Shifting workloads from synchronous to asynchronous can simplify the operational cost of high-throughput HTTP services. But understanding the evolution of performance metrics in the world of complex, high-concurrency, asynchronous distributed systems can be quite challenging.

Speaker image - Lily Mara

Lily Mara

Engineering Manager @OneSignal

Session Architecture

Building an Architecture to Predict Customer Behavior in a Revenue-Critical System

Wednesday Jun 14 / 01:40PM EDT

At Neon digital bank in Brazil, we strive to make revenue-impacting predictions based on customer behavior. Building a low latency and high availability distributed system that meets this requirement becomes especially challenging.

Speaker image - Yves Junqueira

Yves Junqueira

Distinguished Software Engineer @Neon

Session Developer Environment

Architecting a Production Development Environment for Reliability

Wednesday Jun 14 / 04:10PM EDT

At Meta, developers use a combination of development servers, including virtual machines and physical hosts, as well as on-demand containers to perform their daily software engineering work.

Speaker image - Henrique Andrade

Henrique Andrade

Production Engineer @Meta

Session Cloud Architecture

Survival Strategies for the Noisy Neighbor Apocalypse

Wednesday Jun 14 / 05:25PM EDT

Noisy neighbor issues are a common challenge for multi-tenant platforms, leading to resource contention, performance degradation, and costly downtime for other tenants sharing the same resources.

Speaker image - Meenakshi Jindal

Meenakshi Jindal

Staff Software Engineer @Netflix