Build & maintain complex distributed systems
17–18 October 2017: Training
18–20 October 2017: Tutorials & Conference
London, UK

Call for speakers

Call closed 23:59 — 2 May 2017 BST.

Before submitting your proposal, please read about the new direction for Velocity. As we shift our focus to designing and operating distributed systems, we’re moving away from frontend web performance talks as part of the Velocity program.

In 2017 we plan to have more opinionated, deeper-dive tracks. We invite proposals from system engineers, architects, developers, system administrators, operations managers, site reliability engineers, and more—people on the front lines with stories of great success and worthy failures, especially if they provide clear ideas for what to do next. And while people need a sense of what’s possible, bring concrete technical solutions above all else. Please read our tips for preparing a proposal tips for preparing a proposal, and then submit your idea by 23:59 BST 2 May 2017.

Note: Names and company affiliations will not be considered by the program committee during the first round of review. Any videos submitted with the proposal will also be excluded from consideration for the initial review.

Tracks we’re focusing on for the 2017 conference program include:

Systems Engineering

  • Distributed systems
  • Monitoring & Observability
  • Tracing
  • Concurrency
  • Debugging
  • Fault tolerance and failure modes (Chaos engineering, Jepsen, etc.)
  • Incident management and emergency response
  • Resilience engineering

Orchestration, Scheduling, and Containers

  • Docker, Kubernetes, Mesos and more
  • Host-level orchestration systems
  • Deployment at scale
  • Configuration management in the world of the orchestrator
  • Stateful services
  • Continuous Deployment and Delivery

Databases and Distributed Data

  • Data Pipelines
  • RDBMS high availability and document store architecture patterns
  • Caching and in-memory data stores
  • Graph and specialized data stores
  • Build and deploy at the persistence tier
  • Technology-specific migration and data management approaches
  • Distributed object and blocks storage
  • New types of memory
  • Distributed logs, event-driven and CQRS architectures

Networking, Traffic and Edge Management

  • Layer 4 and Layer 7 load balancing
  • DDoS mitigation
  • IPv6 at the edge
  • Content distribution
  • Congestion control in the WAN
  • Overlay networking
  • Whitebox switching and routing
  • Failover strategies
  • Edge routing at scale

Capacity Planning

  • Resource efficiency in the cloud
  • Techniques and methodologies around capacity management
  • Benchmarking and load testing
  • Performance engineering
  • Hybrid cloud and moving from on-premises to the Cloud

Hardware, Storage, and Datacenters

  • Open-channel storage
  • DPDK and pf_ring
  • New types of non-volatile memory and interconnect
  • Hardware management

Technical Leadership

  • Decision-making in a technical environment
  • Hiring
  • Team integration and performance management
  • Training and building skillsets

Required information

You’ll be asked to provide the following information for your proposal. Because the first round will be a blind review, please do not include your name, affiliation, or any other identifying information in the title, description, or abstract of your proposal.

  • Proposed title
  • Description of the presentation
  • Suggested main topic
  • Audience information:
    • Who is the presentation is for?
    • What will they be able to take away?
    • What prerequisite knowledge do they need?
  • For tutorial proposals: hardware installation, materials, and/or downloads attendees will need in advance
  • Speaker(s): biography and hi-res headshot (minimum 1400 pixels wide; required)
  • A video of the speaker
  • Reimbursement needs for travel or other conference-related expenses (if you are self-employed, for example)

Proposals will be considered for the following types of presentations:

  • 40-minute presentations, discussions, or panels
  • 3-hour tutorials

Tips for submitting a successful proposal

Help us understand why your presentation is the right one for Velocity. Please keep in mind that this event is by and for professionals. All presentations and supporting materials must be respectful, inclusive, and adhere to our Code of Conduct.

  • Pick the right topic for your talk to be sure it gets in front of the right program committee members.
  • Be authentic. Your peers need original ideas in real-world scenarios, relevant examples, and knowledge transfer.
  • Give your proposal a simple and straightforward title.
  • Include as much detail about the presentation as possible.
  • If you are proposing a panel, tell us who else would be on it.
  • Keep proposals free of marketing and sales.
  • If you are not the speaker, provide the contact information of the person you’re suggesting. We tend to ignore proposals submitted by PR agencies and require that we can reach the suggested participant directly. Improve the proposal’s chances of being accepted by working closely with the presenter(s) to write a jargon-free proposal that contains clear value for attendees.
  • Keep the audience in mind: they’re professional, and already pretty smart.
  • Limit the scope: in 40 minutes, you won’t be able to cover Everything about Framework X. Instead, pick a useful aspect, or a particular technique, or walk through a simple program.
  • Explain why people will want to attend and what they’ll take away from it
  • Don’t assume that your company’s name buys you credibility. If you’re talking about something important that you have specific knowledge of because of what your company does, spell that out in the description.
  • Does your presentation have the participation of a woman, person of color, or member of another group often underrepresented at tech conferences? Diversity is one of the factors we seriously consider when reviewing proposals as we seek to broaden our speaker roster.

Other resources to help write your proposals:

Important Dates:

  • Call for speakers closes 2 May 2017
  • Registration opens in June 2017
  • All proposers notified by June 2017

Code of Conduct

All participants, including speakers, must follow our Code of Conduct, the core of which is this: an O’Reilly conference should be a safe and productive environment for everyone. Read more »

Create a proposal