[email protected] conferences: APIs
APIs are the backbone of modern, interconnected software systems. Ensure your APIs are flexible, functional, and user friendly at [email protected] conferences: APIs.
Listen to expert speakers discuss API design patterns, effective development methodologies, and the latest tools for amazing APIs.
august 3 2021
from 12pm est
free one day conference
All [email protected] conferences are free to attend. Just register for your lobby pass.
talks from experts
Featuring speakers from Manning’s network of authors and experts.
live on twitch
No travel needed. [email protected] conferences stream globally via Twitch.
conference schedule
12:00 EST: John Skeet – Network API Version Strategies
12:40 EST: Lukas Rosenstock – From Domain Model to API – an approach to API Design First
1:05 EST: Arnaud Laurent – Supercharge OpenAPI to describe APIs in a complete and efficient way
1:40 EST: Jose Haro Peralta – API Development workflows for successful integrations
2:05 EST: Felienne Hermans – How to make your API more useable
2:30 EST: Taurius Litvinavicius – What you can find in .NET API Requests
3:00 EST: Mike Amundsen – Testing your APIs with Postman and Newman
3:30 EST: Fernando Doglio – Fun with Redis: creating a reactive architecture using Redis and Microservices
3:55 EST: Ivana Isadora Devcic – 5 choices that transform API documentation from average to amazing
4:20 EST: Neil Madden – OAuth 2 Scope Design for Security
4:45 EST: Jean Yang – Bridging the Gap between Design-First and Implementation-First
conference speakers
Jon Skeet
Jon Skeet is a Staff Developer Relations Engineer at Google, currently working on the .NET Client Libraries for Google Cloud Platform. Jon is best known for his contributions to Stack Overflow. He is the author of C# in Depth and Software Mistakes and Tradeoffs.
APIs evolve, and that’s a good thing. We need to be able to add features and sometimes even correct API design mistakes. But how do we do this without breaking users? Network APIs present significantly different versioning challenges to those encountered working directly in code. In this talk we’ll look at two approaches and consider their impacts on both the API producer and the API consumers.
Mike Amundsen
An internationally known author and speaker, Mike Amundsen consults with organizations around the worl d on network architecture, Web development, and the intersection of technology & society. He works with companies large and small to help them capitalize on the opportunities provided by APIs, Microservices, and Digital Transformation. Amundsen has author ed numerous books and papers. His most recent book is “Design and Build Great Web APIs” with Pragmatic Programmers. He contributed to the O’Reilly book, “Continuous API Management” (2018). Amundsen’s “RESTful Web Clients” was published by O’Reilly in Febru ary 2017 and he co – authored “Microservice Architecture” (June 2016).
Testing is an essential part of a quality API strategy. And API testing means taking an “outside – in” approach to writing and executing those tests. This talk w/ show you how to create simple request tests (SRTs) to probe your API endpoints as well as apply Dan North’s Behavior – Driven Approach (BDD) to writing powerful tests. You’ll also learn to apply a common model for writing API tests using the Protocol – Structure – Value pattern to create stable, reliable tests that continue to work as expected even as you r API changes over time. If you want to improve your testing strategies and increase the success of your API program, this talk is for you.
Arnaud Lauret
A software architect with extensive experience in the banking industry, Arnaud Lauret has spent 10 years using, designing, and building APIs. He blogs under the name of API Handyman and has created the API Stylebook website. Arnaud is the author of the Design of Web APIs.
The OpenAPI Specification has become an industry standard to describe Web APIs during the design phase or to create API documentation. During this session, Arnaud Lauret will demonstrate how to take advantage of the OpenAPI specification’s basic to advanced features to efficiently create complete, accurate, maintainable and user friendly API descriptions.
Felienne Hermans
Dr. Felienne Hermans is an associate professor at Leiden University in the Netherlands. She has spent the last decade researching learning and teaching programming. Felienne is an award-winning educator, the creator of the Hedy programming language for novice programmers, and a host of Software Engineering Radio—one of the world’s largest programming podcasts. She is the author of The Programmer’s Brain.
When you design an API, often you are thinking as the programmer, in terms of what options the API should expose? But how to consider the understanding of the user of the API? In this talk, Felienne, author of the Programmer’s Brain will outline a framework to help you think of the ease of understanding of API’s
Jose Haro Peralta
Jose Haro Peralta is a full stack consultant based in London. He specialises in Python and DevOps. He has worked in different industries, including IoT, financial services, and retail, helping clients architect and build microservices platforms, deliver successful API integrations, and write clean and maintainable Python code. Jose is the author of Microservice APIs in Python.
APIs are the fundamental tenets of the Internet. They enable integrations between different services, and they power the servers that bring our applications to life. API integrations lay at the core of our API-driven world, and delivering successful API integrations is fundamental to sustain it. However, more often than not, API integrations tend to fail due to ineffective development workflows. In this presentation, I want to present various API development workflows that have helped me and my clients deliver successful API integrations. I’ll show how documentation-driven development, using mock servers, robust API testing frameworks, and API visibility tools can help to significantly reduce the chances of API integration failure and to keep errors under control.
Lukas Rosenstock
Lukas Rosenstock is an independent software developer, technical writer, speaker, API consultant, and entrepreneur who has over a decade of experience working in and with startups. He’s the co-author of Designing APIs with Swagger and OpenAPItogether with Josh Ponelat.
API Design First is a recommended approach towards building APIs in which software teams collaborate to create an API definition in the machine-readable OpenAPI format before writing any code. The definition then acts as the single source of truth that drives the implementation and the rest of the software development lifecycle. This talk walks through an API Design First process that starts with domain modeling and follows a set of rules and best practices to convert the domain model into a well-designed API.We will explore the relationship between domain model concepts andAPI resource schemas, and we will discover how to map domain model actions in a CRUD approach for a REST-ful API design. The talk is based upon two chapters from our upcoming book.
Fernando Doglio
Fernando Doglio has twenty years of experience in the software industry, where he has worked in areas from web development to big data.
Redis is a very versatile product, one that has a lot more use cases than working as a cache storage system. Through the use of Redis I’ll show you how you can use it to create a reactive architecture based around a set of APIs.
Neil Madden
Neil Madden is Security Director at ForgeRock and the author of API Security in Action. He has over 20 years of industry experience, and an in-depth knowledge of application security topics. He is a frequent contributor to the OAuth Working Group at the IETF. Neil holds a PhD in Computer Science and lives in the UK with his wife and daughter.
OAuth 2 is very widely used for securing access to APIs. Access to resources is restricted based on the concept of “scope”. But what is a scope? How does it differ from permissions or roles? In this talk, you’ll learn best practices for securing access to resources using OAuth 2 scopes and when other technologies may be a better fit. We’ll also look at upcoming changes to OAuth 2 that broaden the applicability of scopes.
Jean Yang
Jean Yang (@jeanqasaur) is the founder and CEO of Akita Software, building the first API-centric observability platform. Previously, Jean was a professor of Computer Science at Carnegie Mellon University. Jean has a PhD from MIT and was selected as one of the MIT Technology Review’s 35 Innovators Under 35 for programming tools work in 2016.
The rise of APIs and service-oriented architectures has made it easier than ever before to build complex, organically evolving web applications. This is at odds with a design-first approach to building systems! As a result of this tension, design-first systems are often not able to take advantage of the benefits of modern architectures, while teams that have embraced service-oriented architectures have trouble with design-first. Our solution: when it comes to working with APIs, moving from specification-first to specification-in-the-loop. In this talk, I’ll show how automatically learning API specifications (and additional API properties) can provide a nice complement to handwritten APIs, bridging the gap between design-first and implementation-first approaches.
Ivana Isadora Devcic
Ivana Isadora Devcic is a technical writer, editor, and open source advocate with a background in linguistics and translation. Building on her experience as a documentation developer for enterprise security software and RESTful APIs, Ivana has made it her mission to help people use software more efficiently and productively. Ivana currently works at Redocly (https://redoc.ly/) on products that live and breathe API documentation.
An API without documentation is an incomplete product (or at best, an interesting experiment). However, not all API documentation is created equal. When you think of best-in-class examples of API documentation, you can usually pinpoint a few distinguishing factors that make those examples stand out from the rest. Yet in many cases, the difference between average and amazing documentation is not so much in the specifics, but in the overall experience. In this talk, we will explore 5 decisions you can implement to evolve your API documentation. We’ll also look at how the documentation quality impacts API adoption, and address common challenges in maintaining API documentation.
Taurius Litvinavicius
Taurius Litvinavicius has been building APIs for a long time, during which he has tried several options – Golang, Python, C++, but in the he stayed loyal to the C# arrangement for the API development. He has built APIs for XML endpoints, for JSON and even his own custom formats.
Most of the time in API development people access things like form data, json body, query parameters and perhaps headers. That may seem like a lot of options, but more things exist in the request and interesting things can be found if you dive deeper, if you leave the constraints of action and controller. In this talk you will find out where things begin on that API request in C# APIs and what interesting data you can find besides the common stuff. We will explore the controller class, which will help you understand the structure of it all and then you will see why Startup.cs is important and how everything begins inside it.
media partners
register for [email protected] conferences: APIs
All preregistrations receive:
Just sign up with an email.
Upcoming [email protected] conferences
Oct 12, 2021
[email protected] conferences: Security

December 7, 2021
[email protected] conferences: Data Engineering