June 15–18, 2020

Call for speakers

Call closes 11:59pm 12/10/2019 PST.

Submit a proposal

Software Architecture Reinvented

Software architecture is the foundation on which all software is built, and from which all software is deployed. The power and stability of a software architecture are critical to any organization looking to compete and thrive in the modern economy. The tools, techniques, and nature of software architecture constantly change, while decisions that impact the architecture become more distributed.

We strive to help our audience learn. We want to hear about real-world experiences, including the benefits of architectural decisions, but especially the pitfalls and tradeoffs. How do frameworks and other architectural underpinnings perform under the crucible of real-world challenges? How have the cloud computing, microservices, and serverless paradigms impacted software architecture? How can the latest trends be leveraged while still supporting legacy systems? How will the software architect’s role continue to evolve, and how will its interdependencies change?

The O’Reilly Software Architecture Conference is one of the few events focused solely on software architecture. The conference promotes leadership and concrete skills critical for software architecture design, development, and deployment. We need your help amplifying the importance of this role throughout an organization, and creating a wealth of information to help practitioners improve the performance of their software architectures. What learning path did you take? How can we raise the visibility of our skills and share core concepts to help our community members perform better in their roles? How have architectural ideas been applied in your industry?

Proposals will be considered for both 50 and 90 minute presentations. Fifty-minute sessions will be interspersed throughout the conference to introduce new concepts, a best practice, or a view into the future. However, many topics in software architecture require more context than 50 minutes allows. Ninety-minute sessions will dive deeper—giving you information, techniques, and workflows you can bring back to work and begin applying immediately.

We suggest a few ideas below, but we encourage you to go beyond them. We’re particularly seeking presentations that cite real-world experience, promote innovative ideas, and/or foster ideas that challenge outdated dogma. Case studies that speak to both architectural failure and success are encouraged. All interesting ideas, presented in interesting ways, are welcome.

If you want to submit a great proposal, read our tips and best practices below. The deadline for submissions is 11:59 pm PT on December 10, 2019.

New architectural styles

  • Microservices architecture
  • Cloud computing
  • Serverless
  • Reactive and its variants

Effective techniques for existing architectures and legacy systems

  • Domain-Driven Design
  • Web
  • Single-page web applications
  • Distributed systems
  • Integration architecture
  • Enterprise architecture
  • Application architecture
  • Effective tradeoff analysis
  • Architecture fitness functions
  • Insights on domain-specific strategies (media, finance, healthcare, etc.)
  • Event-driven Architecture

Intersection of architecture and…

  • Agile
  • DevOps, operations, deployment, Continuous Delivery
  • Security – both internal and external
  • User experience design
  • Caching, load balancing, optimization
  • Scale and performance
  • Business concerns and case studies (notably failure and success with remote management and outsourcing; and how a startup should plan and build an architecture)
  • Chaos engineering
  • Data management
  • Regulation and compliance (e.g. GDPR)
  • AI and machine learning
  • Product management

Required information

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: 50-minute session, 90-minute session, or 3-hour tutorial

Tips for submitting a successful proposal

Help us understand why your presentation is the right one for the Software Architecture Conference. Please keep in mind that this event is by and for professionals. All speakers must adhere to our Code of Conduct. Please be sure that your presentation, including all supporting materials and informal commentary, is welcoming and respectful to all participants, regardless of race, gender, gender identity and expression, age, sexual orientation, disability, physical appearance, national origin, ethnicity, or religion.

  • Keep proposals free of marketing and sales.
  • 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.
  • 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 50 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 Participation closes on December 10
  • All proposers notified by February 2020
  • Registration opens in February 2020

Code of Conduct

All participants, including speakers and presenters, 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. Please be sure that your presentation, including all supporting materials and informal commentary, is welcoming and respectful to all participants, regardless of race, gender, gender identity and expression, age, sexual orientation, disability, physical appearance, national origin, ethnicity, or religion. Read more »

Submit a proposal

Contact us

confreg@oreilly.com

For conference registration information and customer service

partners@oreilly.com

For more information on community discounts and trade opportunities with O’Reilly conferences

Become a sponsor

For information on exhibiting or sponsoring a conference

pr@oreilly.com

For media/analyst press inquires