by Datadog


As businesses continue to operate faster and more nimbly, they will require faster, more resilient applications; repeatable, predictable, responsive infrastructure; and empowered, highly creative technical teams. This all must happen in an environment where security and compliance are more important than ever.

At Dash, we want to hear your stories of speed, security, and scalability as you build the next generation of infrastructure, applications, and teams. We’ll bring together thousands of the world’s top developers, systems engineers, and business leaders to share how they accelerate and scale out their teams and systems, how they maintain visibility and focus, and how their work today aligns with their visions for the future.

If you have a success story or a cautionary tale of missteps and lessons learned, this is your opportunity to share it!

The themes listed below are suggested topics, but they are only suggestions. Your stories are unique, and we’d love to hear them. The deadline for submissions is August 1st at 11:59 PM EDT.

Speakers will also receive help in preparing their sessions and the opportunity to share their experiences with the Datadog community.



In our pursuit to push our systems to do more, both applications and infrastructure are growing more complex. As this happens, we're running into a common problem: performance. Share what you're doing to build faster applications and systems that deliver better user experiences.


  • Shesh Patel of the New York Times covered how the New York Times used stress testing in preparation for a known high traffic event—the 2018 Midterm Elections.
  • DraftKings CTO Travis Dunn explained how DraftKings used circuit breakers to prevent non-critical systems and minor features from causing outages as they moved to a complex, microservices-based architecture.

Scaling Systems

Dash is about scaling up and speeding up, but we can't do that with the tools and architectures of the past. We've moved from monoliths to microservices, and from servers to containers and serverless, but what's next? Share how you're architecting the applications and infrastructure of the future.


  • Aaron Brady of Shopify spoke about the unique challenges in building and scaling Shopify, their heavy use of MySQL and database sharding, and how they worked to simplify customer onboarding.
  • Bonnie Rhee of Flatiron Health shared what happened when Flatiron Health introduced new technology to maintain developer happiness and how, despite their rigorous release plan, the rollout caused issues ranging from exposing brittle ecosystems and processes, to causing internal server failures. Hear about missteps and mistakes, the lessons learned from these incidents, and the introduction of a celebrated product.


Scaling teams is a delicate balance of adding new members while managing work, mentoring teammates, building processes, and growing culture. The way many teams work has also fundamentally shifted, whether through experiencing growth, adapting to remote/hybrid models, or navigating a return to office. We want to hear about the challenges and successes your team has encountered while scaling or adapting.


Transformations and Case Studies

Organizations and technical systems aren’t static. As we encounter new challenges, we have to adapt our approach and our technologies to solve them. Share your first-hand experiences of technical and organizational evolutions so that others can follow your path to success (or avoid your mistakes).


  • Damian Schenkelman of Auth0 shared Auth0’s experiences in creating and rolling out SRE.
  • Tiffany Low and Willie Yao of Airbnb shared the story of how Airbnb failed to migrate to microservices on their first attempt—at the time, they didn’t have an urgent need, so the costs outweighed the benefits. As they scaled their developer team, however, deployments slowed and the migration became necessary. The lessons from their first attempt helped them successfully migrate to microservices when it mattered most.

Security and Compliance

Applications and infrastructure are growing more complex, and DevOps practices inherently distribute data across services and teams. Baking security into every part of the development cycle is key to success. As businesses grow, the only way to scale out security is to make it more accessible to engineering teams. This becomes especially important as industries add more compliance requirements. Observability is the answer, but it’s not enough to just observe. The best strategies take automated actions based on those findings, stopping attackers at the source before they are able to pivot, exfiltrate data, or persist. Tell us your stories about making security accessible and how you saved time through automation, kept your users safe, and more.


  • Matt Peters and Peter Silberman of Expel explored how to use mathematics and simulation to optimize their workflow in a security operations center (SOC). Using data and experience from the SOC at Expel, they explained how to use statistics and Monte Carlo simulations to explore various optimizations including introducing alert severities, tiering analysts, and reducing investigation and incident response time. For each case they simulated the impact on an SOC and its performance.
  • Nathan Case and Eric Lopez of Resilience
    How do you pivot your strategy when your company grows from 10 highly trained people to 1,800 teammates in 8 months? How do your systems and security plans change, and how do you maintain control of an infrastructure on the ground, the cloud, and SaaS all over the planet? How do you achieve visibility in acquired companies so that security and productivity are not affected. See the mistakes we made and how we found visibility quickly in the face of acquisition and attacks.

Surprise Us

Dash is focused on the future of technical applications and systems, and the teams that build and support them. The future is unknown, but will certainly bring surprises. If you have a talk that fits Dash’s theme, but may not fit into one of our tracks, we encourage you to submit it!

Tips for submitting

  1. Session slots are 40 minutes in length. Plan 25–35 minutes for your talk and the rest for live Q&A.

  2. All Dash main sessions will be on October 19, 2022 between 12pm and 6pm ET in New York City.

  3. Choose the most appropriate theme for your talk. This will ensure it is reviewed by the right people.

  4. Keep the audience in mind. You’ll be presenting to professional developers, engineers, and technically oriented business leaders.

  5. Explain why your story matters and include details of what the audience will learn.

  6. Datadog will provide travel and accommodations for selected speakers. We don’t want travel logistics preventing you from sharing. All speakers will receive a full conference pass.