Build resilient systems at scale
May 27–29, 2015 • Santa Clara, CA

Velocity 2015 Call for Speakers

Call closed 11:59pm 02/02/2015 PST.

Out of the fire of Velocity came a New Way of doing things forged in a web-centric world. Along the way, something changed fundamentally about not just tech companies, but companies in general. As we looked around more recently, we realized it wasn’t just about the web and fast pages any more. It’s becoming clear that the way of doing things on the web that we’ve been discussing at Velocity has profoundly influenced how businesses (and other organizations) operate, online or otherwise.

As such, we are reorganizing the conference around the themes we see as most important to helping modern, coded businesses thrive. These themes encompass both technical and non-technical topics, and include:

  • End-to-End Optimization
  • IT as a Business Driver
  • Ubiquitous Delivery
  • Deliberately Unstable Systems

We invite proposals from practitioners, architects, developers, system administrators, operations managers, 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, and then submit your idea by February 2, 2015.

Topics we’re seeking for the 2015 conference program include:

End-to-End Optimization
Our notion of performance has evolved significantly over the past many years—it’s not just about reducing latency and round trips, we have to take a user-focused approach. There’s still plenty of room for deep technical talks, but a broader view of optimizing the user experience is welcome, too. Additionally, technological change is impossible without cultural/organizational change. Any organization—whether for profit or in the public sector—simply cannot move at the pace of current technological systems without adjusting their social systems.

  • User experience optimization
  • Network, database and middleware optimization
  • Organizational optimization

IT as a Business Driver
Gone are the days of the “Department of No.” Companies that re-envision traditional IT as a service provider are able to move more quickly, release more often, and adjust strategy as needed.

  • Instrumentation and Automation
  • Continuous Delivery
  • Cloud administration
  • Containerization/deployment
  • Docker and CoreOS
  • Software Defined Networking/Network abstraction
  • “Infrastructure as code” disruption of networking
  • Continuous Security
  • DevOps in the Enterprise

Ubiquitous Delivery
Building and maintaining products and services intended to reach people (and things, aka IoT) anywhere, anytime.

  • Edge computing
  • Building the infrastructure of the IoT
  • Mobile apps
  • Responsive design
  • Offline functionality and wireless mesh networks

Deliberately Unstable Systems
Expect failure, and design/build/test for it.

  • SOA architectures
  • Managing risk and complexity
  • Incident management
  • Human machine cooperation
  • Metrics/monitoring
  • Systems thinking
  • Microservices

You’ll be asked to include the following information for your proposal:

  • Proposed title
  • Overview and extended descriptions of the presentation: main idea, subtopics, conclusion
  • Suggested topic
  • Prerequisites
  • Speaker(s): expertise, summary biography, and hi-res headshot

Proposals will be considered for the following types of presentations:

  • Session: 40-minute presentations, discussions, or panels
  • Tutorial: typically 90-minute presentations

Tips for Successful Proposals

Help us understand why your presentation is the right one for Velocity. Below are some tips for writing a successful proposal. Please keep in mind that this event is by and for professionals. Our participants expect that all presentations and supporting materials will be respectful, inclusive, and adhere to our Code of Conduct.

  • Be authentic. Your peers need original ideas in real-world scenarios, relevant examples, and knowledge transfer.
  • Give your proposal a simple and straightforward title. Clever or inappropriate titles make it harder to figure out what you’re really talking about.
  • Include as much detail about the presentation as possible. Longer talks should provide more details.
  • 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 unless 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.
  • Context is important. If your talk is about something truly ground-breaking, it’ll be helpful if you describe it in terms of things that attendees might already know of.
  • 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: is your topic gaining traction? Is it critical to business? Will attendees learn how to use it, program it, or just what it is?
  • Repeated talks from the conference circuit are less likely to be appealing. If you speak at a lot of events, be sure to note why this presentation is different.
  • 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.
  • Indicate in your proposal notes whether you can give all the talks you submitted.
  • 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.
  • We welcome sessions for attendees with a variety of skill levels. Indicate the experience and knowledge level of the audience that you are targeting: novice, intermediate, or expert.

Other resources to help write your proposals:

Code of Conduct

We expect all participants, including speakers, to support 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 your proposal now

Important Dates

  • Registration Opens – January 2015
  • Call for Participation Closes – February 2, 2015
  • All proposers notified – By March 2015