Call for papers

Closed: April 12, 2019

You’re more than a face in the crowd at SpringOne Platform. Here you can meaningfully connect with the people, process, and tools you need to deliver and operate software that matters. From Spring Framework to .NET Core, Cloud Foundry to Kubernetes, SpringOne connects all the pieces of the modern software puzzle. And beyond that, it’s a chance for developers, operators, architects, data scientists, and executives to talk about what they know.

We’re looking for your stories about crucial cloud topics like platforms, functions, and event-driven architecture. Microservices, reactive, and CI/CD. Data and machine learning. Share what your challenges are and how you’re overcoming them. Where you are in your transformation journey—and where you’re going.

Submit your talk today and share how you’re building software people love.


We’re considering proposals for the following types of presentations:

30-min talks

Some Spring tech topics fit here, but typically we see talks on things like Agile/XP, TDD, Case Studies, Methodology, Product Management, Culture, and Exec/Transformation. These fit well into 30-minute slots.

60-min talks

Most Spring tech talks, Cloud Foundry, Kubernetes, serverless, or Data topics fit here. These are practitioner-oriented topics with lots of live coding or demos and often have a GitHub repo that attendees will be able to go home with.

We’ll also be doing Lightning Talks. Stay tuned for details.

Note: Sessions that can be either 30 or 60 minutes are easy to work with! If you’re submitting a 60-min talk, we highly encourage you to also consider a plan for a 30-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 thrust of your talk from the following options.

Core Framework

Spring Framework, Spring Security, developer tools, Java

Modern Web

REST/OAuth, Spring MVC/WebFlux, ASP .NET Core, HTML/CSS, web server

Data, Databases

Spring Data, Spring Batch, Redis, data science, Apache Spark, machine learning, Hadoop (Note: DBA-focused content is not encouraged)


Apache Geode, Pivotal GemFire, Pivotal Cloud Cache

Event Driven

Application events, messaging, CQRS, event sourcing, domain-driven design, eventual consistency, Apache Kafka, RabbitMQ


Stream processing, Project Reactor, Spring Cloud Stream, general reactive programming, actors


Spring Cloud, Spring Cloud Services, Spring Cloud Function, serverless, Project riff, Pivotal Function Service, Lambda, Knative, events, streams, channels, pub/sub


Kubernetes fundamentals, Envoy, Istio, containers, Pivotal Container Service (PKS), Project riff, Pivotal Function Service (PFS)

Cloud Foundry

Most Cloud Foundry talks focus on ops or dev practitioners: Pivotal Application Service (PAS), Pivotal Container Service (PKS), Pivotal Function Service (PFS), Pivotal Cloud Cache, security, UAA, BOSH, networking


Value stream, automation, culture, continuous improvement, operations, monitoring, observability


Spinnaker, Concourse, Jenkins, canary and blue/green release, progressive deployment pipelines, release management, builds, testing, Concourse, Spinnaker


Mobbing, remote agile, pair programming, test-driven development, estimating (or not estimating), agile/XP, other methodology topics

Transformation Case Studies

End user/customer talks


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


Kotlin, Spring, Boot, JVM, language, static typing, functional, asynchronous, coroutines, Project Reactor, reactive, DSL, performance, interoperability, testing, migration, microservices, event sourcing in conjunction with Kotlin


Cloud-native, containerization, windows, .NET core, .NET framework, modernization, replatforming, Steeltoe, language, tooling


Cloud-native, JavaScript (e.g. ES2017, vNext), V8, Lint, Async/Await, bundler tools, Functional Programming, Transpiler/Compiler

Tips for successful proposals

Help us understand why your presentation is the right one for SpringOne Platform. 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 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 proposals as we seek to broaden our speaker roster.

Keep the audience in mind.

SpringOne attendees are professional, and already pretty smart. Keep proposals free of marketing and sales pitches.

Be authentic.

Your peers need original ideas in real-world scenarios, relevant examples, and knowledge transfer.

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?

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).

Include the context.

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.

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?

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.

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.

Define your audience.

Indicate the experience and knowledge level of the audience that you are targeting: novice, intermediate, or expert.

Proposal resources

Code of conduct

We expect all participants, including speakers, to follow our Code of Conduct, the core of which is this: SpringOne Platform should be a safe and productive environment for everyone.

Speaker travel assistance program

While ticket fees for speakers are of course waived, speaker travel and expenses will not be paid by Pivotal. However, speakers from underrepresented groups may apply for the program when submitting a paper. Applications will be awarded at the discretion of the conference.

Please contact us with any questions or concerns.


If accepted, only your first co-presenter's ticket will be comped. If you need more than two co-presenters, please contact us.