Velocity 2019: Building, Managing, and Scaling Cloud-Native Systems
11:59pm 12/10/2018 PST.
Submit a proposal
At Velocity, we focus on teaching new skills, approaches, and technologies for building and managing large-scale, cloud-native systems. Knowledge of a specific tool or technology is important, but success only happens when the people building the systems understand the context of their work as part of a larger whole and understand the interdependencies each technology has on the other.
We’re seeking proposals that provide the content and context engineers need to succeed and reflect the complexity and depth of the systems that today’s organizations are building and managing. Talks at Velocity are opinionated, vendor-neutral, deep-dives into the technology, tools, processes, and people needed to build modern, cloud-native systems. We focus on real-world implementations, case studies, and lessons learned from both success and failure. We’re interested in new tools, techniques, ideas, and experiments that will help our community learn and develop.
People learn best through stories and we want to hear yours. Sessions should describe your personal experience solving real-world problems around improved reliability, performance, scalability, and efficiency of applications. We invite proposals from systems engineers, architects, developers, systems administrators, security, operations, site reliability engineers, and the people managing these complex systems.
Themes we’re focusing on for the 2019 conference program include:
- Cloud, Cloud Native, and Infrastructure
- Containers, Kubernetes, and Microservices
- Monitoring, Observability, and Performance
- SRE and DevOps
- Distributed Data and State
- Systems Engineering and Architecture
- Emerging Tech (Machine Learning, AI, Blockchain)
New to the speaking circuit? We want to hear from you! We’re actively seeking new voices and off-the-beaten-path topics. Any ideas, best practices, or challenges that you’ve encountered and conquered are fair game. If it’s important to you, chances are it’s important to others as well.
You’ll be asked to include the following information for 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). Check out our guidelines for capturing a great portrait.
- A video of the speaker
- Reimbursement needs for travel or other conference-related expenses (if you are self-employed, for example) Note: If your proposal is accepted and you are traveling internationally, we can provide a formal invitation letter upon request.
- Type of presentation: 40-minute session or 3-hour tutorial
Tips for submitting a successful proposal
All presentations and supporting materials must be respectful, inclusive, and adhere to our Code of Conduct. We welcome and encourage talks from those with diverse backgrounds and unique points-of-view.
- Give your proposal a simple and straightforward title.
- Let us know if you are interested in doing either a 40-minute presentation or 3-hour tutorial (or if your talk could work for either).
- Share audience takeaways in your description. Be sure to list the main things attendees will learn from your talk and be able to apply to their work.
- Be authentic: Your peers need original ideas from real-world scenarios with relevant examples.
- Limit the scope: you may not be able to cover “Everything about Framework X” in your session time. Instead, pick a useful aspect, or a particular technique, or walk through a simple program.
- Don’t assume that your company’s name buys you credibility. If you’re talking about something important, spell that out in the description.
- Remember, what’s familiar to you may be new to someone else. While we do want the latest and greatest research and techniques, powerful explanations and stories about how to engineer systems will appeal to a broad audience.
- Keep proposals free of marketing, sales, and vendor pitches. Seriously, we can’t stress this enough. Pure vendor sales pitches will be rejected. If you are a vendor, encourage a user of your product to submit a practical talk on your behalf or submit a technical talk that skips the marketing story in favor of practical and usable information.
Other resources to help write your proposals
- Call for Participation closes December 10, 2018
- All proposers notified by January 2019
- Registration opens February 2019
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