Call for Papers
SpringOne is all about your stories. From Spring Framework to Kubernetes to microservices and everything in between, we want you to submit a paper that shares your insights and expertise on topics like streaming data, design patterns, event-driven architectures, DevSecOps, platforms, data and machine learning, and CI/CD. (And so much more beyond that.)
Tell us about your challenges and how you’re overcoming them. What you've discovered that you’d like to share with the community. Where you are in your transformation journey—and where you’re going next.
Call for Papers closes June 20, 2022.Submit a talk
Already created an account? Sign in to submit a talk.
This year’s event will feature six tracks:
Platforms and Stacks
People, Process, and Culture
When you submit your talk, you can identify whether you’re more comfortable presenting in person or virtually.
We’re considering papers for the following types of presentations:
Some Spring tech topics fit here, but typically we see talks on things like development practices, TDD, case studies, product management, culture, and digital transformation.
Most tech talks in the areas of Spring, Kubernetes, serverless, data, or other topics fit here. These are practitioner-oriented, deep-dive topics with lots of live coding or demos, and they often have a GitHub repo that attendees can go home with.
Note: Sessions that can be either 25 or 50 minutes are easy to work with! If you’re submitting a 50-min talk, we highly encourage you to also consider a plan for a 25-min talk if it becomes necessary. If shortening really isn’t an option, please note that in the “Notes for the Content Committee” field. If you can expand or contract your topic in either direction, please note that as well.
We organize and consider sessions by their primary meta tag. Please choose the single most relevant tag that aligns to the core of your talk from the following options.
GraphQL Java, HTTP, WebSocket, RSocket, GraphQL Schema, GraphQL Query Language
Spring Native, GraalVM
Spring Data, Spring Batch, Redis, data science, Apache Spark, machine learning, Hadoop, streams (Note: DBA-focused content is not encouraged)
Spring Security, OAuth, Spring Authorization Server
Spring Cloud, Spring Cloud Services, Spring Cloud Function, serverless, Lambda, Knative, events, streams, channels
Spring Cloud, Spring Cloud Services, Spring Cloud Function, serverless, Lambda, Knative, events, streams, channels, pub/sub, architecture, distributed architecture
REST, Spring MVC, Spring WebFlux, ASP .NET Core, HTML/CSS, web server, full stack
TDD, unit testing, integration testing, JUnit, Mockito
General architecture topics
General Kotlin topics
Value stream, automation, culture, continuous improvement, security, operations, monitoring, observability
Spinnaker, Concourse, Jenkins, canary and blue/green release, progressive deployment pipelines, release management, builds, testing
Mobbing, remote agile, pair programming, test-driven development, estimating (or not estimating), agile/XP, other methodology topics
Stream processing, Project Reactor, Spring Cloud Stream, general reactive programming, actors
Kubernetes fundamentals, Envoy, Istio, containers, VMware Tanzu Kubernetes Grid
Most Cloud Foundry talks focus on ops or dev practitioners: VMware Tanzu Application Service, VMware Tanzu Kubernetes Grid, security, UAA, BOSH, networking
Streaming, IoT, event mesh, high throughput, message broker, event log, Spring Cloud Stream, MQTT, AMQP, Websocket, STOMP, reactive
Language and tooling
General language and tooling topics
General .NET topics
Evolution, migrating to the cloud, disruption, accelerating the journey, replatforming, organizational transformation
Transformation, management, enterprise architect, executives, strategy, vision, innovation, finance, support, growth, value, business, transform, collaboration
General Spring topics
What's new in Spring
AOT, Native, Spring for GraphQL, Spring Framework 6.0, Spring Boot 3.0
Spring MVC, Spring WebFlux, REST, GraphQL, Spring for GraphQL
React, Vue, Svelte, Angular, full stack
Tips for a successful paper
Help us understand why your presentation is right for SpringOne. Below are some tips for writing a successful paper. 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.
1. Be inclusive.
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 papers as we seek to broaden our speaker roster.
2. Keep the audience in mind.
SpringOne attendees are professional, and already have a base level of technical knowledge. Attendees come to SpringOne to learn, so consider keeping papers free of marketing and sales pitches.
3. Be authentic.
Your peers need original ideas in real-world scenarios, relevant examples, and knowledge transfer.
4. Be thorough.
Short, concise abstracts are great for the conference website, but we strongly suggest supplying details for committee consideration. Use the notes field to be specific: What technology will you use? If your abstract is vague, or covers many different subjects, what is the main thrust of your talk?
5. Introduce the team.
If you are proposing a panel, tell us who else would be on it. If co-presenting, include detail about your co-presenter(s).
6. Context is important.
If your talk is about a truly groundbreaking topic, it’ll be helpful to describe it in terms that attendees might already be familiar with.
7. 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 be introduced to it?
8. Be innovative.
Repeated talks from the conference circuit are less appealing. If you speak frequently at events, be sure to note why this presentation is different.
9. 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.
10. Define your audience.
Indicate the experience and knowledge level of the audience that you are targeting: novice, intermediate, or expert.
Resources and policies
Code of conduct
We expect all participants, including speakers, to follow our Code of Conduct, the core of which is: SpringOne should be a safe and productive environment for everyone.
If your paper is accepted, you’ll be able to add co-presenters. If you need more than three co-presenters, please contact us.