|
| 1 | +--- |
| 2 | +date: "2025-09-26" |
| 3 | +title: "The TokioConf 2026 Call For Talk Proposals is now open" |
| 4 | +description: "September 26, 2025" |
| 5 | +--- |
| 6 | + |
| 7 | +We are excited to announce that the Call for Speakers for TokioConf 2026 is |
| 8 | +officially open! |
| 9 | + |
| 10 | +As we announced in June, the Tokio project is hosting the inaugural TokioConf, |
| 11 | +which will take place on April 20-22 in Portland, OR, and will gather 300 |
| 12 | +developers to exchange ideas, learn from one another, and explore the future of |
| 13 | +async Rust. The conference focuses on the practical side of async Rust |
| 14 | +development. Whether you've been working with async Rust for years and have |
| 15 | +lessons to share, you're new to it and figuring out the patterns, or you're a |
| 16 | +student preparing to start your first job, we want talks that help everyone who |
| 17 | +uses async Rust in production. |
| 18 | + |
| 19 | +[Submit a talk proposal here][sessionize]. |
| 20 | + |
| 21 | +We're looking for talks across all technical levels - every talk should provide |
| 22 | +people with practical insights they can apply in their own work. Whether you're |
| 23 | +sharing beginner lessons or advanced optimization tricks, focus on real |
| 24 | +experiences and practical applications that people can actually use. We are |
| 25 | +especially interested in talks about: |
| 26 | + |
| 27 | +<ins>Production Lessons:</ins><br/> |
| 28 | +What actually happened when you shipped async code to production - the outages, |
| 29 | +the tough debugging sessions, the scaling surprises. What tools do you wish |
| 30 | +you'd known about, and what would you do differently next time? |
| 31 | + |
| 32 | +<ins>Architecture Patterns & Design:</ins><br/> |
| 33 | +The architectural decisions that worked (and the ones that didn't) - actor |
| 34 | +patterns, channels, when to spin up multiple runtimes, different concurrency |
| 35 | +approaches, and when you probably shouldn't use Tokio at all. |
| 36 | + |
| 37 | +<ins>Performance Optimization:</ins><br/> |
| 38 | +Stories about hunting down that one blocking call that was tanking performance, |
| 39 | +tuning runtimes, dealing with oversubscription, and annoying OS scheduling |
| 40 | +pauses. Share the optimization tricks that actually made a difference. |
| 41 | + |
| 42 | +<ins>Debugging & Monitoring:</ins><br/> |
| 43 | +How do you actually figure out what's going wrong in async code, especially in |
| 44 | +production? Share your debugging and monitoring setups that work. |
| 45 | + |
| 46 | +<ins>Rust Everywhere:</ins><br/> |
| 47 | +Can Rust really work everywhere, not just for high-performance systems? Real |
| 48 | +experiences using async Rust for typical applications, what's working, what's |
| 49 | +still missing, and what we'd need to get there. |
| 50 | + |
| 51 | +<ins>Testing Async Code:</ins><br/> |
| 52 | +How to actually test this stuff without pulling your hair out, catching those |
| 53 | +sneaky cancellation bugs before they hit users, and the practices that help you |
| 54 | +ship reliable async systems. |
| 55 | + |
| 56 | +<ins>Team Adoption:</ins><br/> |
| 57 | +The real story of adoption - what worked when convincing your team, the training |
| 58 | +that actually helped, the failures and false starts, the common concerns and |
| 59 | +roadblocks you hit, and how to build codebases that your whole team can work |
| 60 | +with. |
| 61 | + |
| 62 | +<ins>What's Next:</ins><br/> |
| 63 | +Industry shifts and emerging technologies that will impact how we build async |
| 64 | +applications. New paradigms, AI, evolving infrastructure - what's coming that |
| 65 | +async Rust developers should be thinking about? |
| 66 | + |
| 67 | +## How to Submit |
| 68 | +Have something the community should hear about? We're accepting submissions |
| 69 | +through December 8, 2025. Submit your proposal at |
| 70 | +[https://sessionize.com/tokioconf-2026][sessionize]. We'll be making the final |
| 71 | +decisions late January 2026. |
| 72 | + |
| 73 | +Questions about your talk idea? Reach out to us at |
| 74 | +[hello@tokioconf.com](hello@tokioconf.com) - we're happy to help you figure out |
| 75 | +if your experience would make a great talk. There is also a #tokioconf channel |
| 76 | +on the Tokio project [Discord], another good place to ask questions. |
| 77 | + |
| 78 | +## What Happens Next |
| 79 | +We are busy planning the conference and will be announcing more details over the |
| 80 | +coming months. Sign up for email updates at |
| 81 | +[tokioconf.com](https://tokioconf.com), or follow us on [Bluesky] or [Mastodon] to |
| 82 | +get updates. |
| 83 | + |
| 84 | +Looking forward to hearing what you've learned building with async Rust. |
| 85 | + |
| 86 | +[sessionize]: https://sessionize.com/tokioconf-2026 |
| 87 | +[Discord]: https://discord.gg/tokio |
| 88 | +[Mastodon]: https://hachyderm.io/@tokioconf |
| 89 | +[BlueSky]: https://bsky.app/profile/tokioconf.com |
0 commit comments