OpenAPI at Scale

Jun 28, 2018Download as PPTX, PDF0 likes375 views

Lots of people talk about the benefits OpenAPI Specification (OAS) can bring to your documentation and testing efforts, but few people talk about the real complexities involved when you try to scale OpenAPI usage across a large organization. This talk is about how to scale your OAS usage, who should be using OAS, and what concrete steps you can take now to save lots of time later. Finally, we’ll take a look at some real world API growing pains that we see at larger Stoplight customers, and their potential solutions.

stoplight.io
OpenAPI at Scale
Marc MacLeod
@marbemac, stoplight.io

stoplight.io
The Happy Path
Your resident OpenAPI expert maintains a
detailed + accurate specification file for your
primary API . Reap the rewards with auto
docs, SDKs, mocks, etc.

stoplight.io
The Reality
Macro trends like microservices,
containerization, IoT, and serverless are driving
us to a world filled with small, distributed, and
composable parts.

stoplight.io
Problems at Scale
Limited Adoption

stoplight.io
Problems at Scale
Limited Adoption Stale OpenAPI

stoplight.io
Limited Adoption Stale OpenAPI Inconsistent APIs
Problems at Scale
!=

stoplight.io
Increasing Adoption: Accessibility
Let’s face it, most people (particularly non-devs)
don’t relish the idea of reading + writing this:

stoplight.io
Increasing Adoption: Accessibility
#1: Don’t force everybody to be an OpenAPI expert.
Visual designers like Stoplight or Apicurio can help.
SwaggerUI is great for a read view.

stoplight.io
Increasing Adoption: Collaboration
#2: Design first over code first.
This allows non-devs to contribute. OpenAPI specs are as
much a business asset as a development asset.

stoplight.io
Increasing Adoption: Collaboration
Get these folks involved!
Technical Writers
Product Managers
QA
Frontend (API Consumers)
Backend
Architects
Business Office

stoplight.io
Increasing Adoption: Discoverability
#3: Invest in a centralized registry early on.
A centralized registry helps everybody understand the
value of OpenAPI, and incentivizes word of mouth spread.

stoplight.io
Problems at Scale
Limited Adoption Stale OpenAPI Inconsistent APIs
!=

stoplight.io
Trust
Your OpenAPI files are your single source of truth.
You never want to ask yourself “Is this OpenAPI file still
accurate?”

stoplight.io
Trust
#4: Treat your OpenAPI file like the critical asset it is, and
bake contract tests into your CI process.
Dredd, Pact, and Stoplight’s Prism are all good options
depending on the scenario.

stoplight.io
Automate Consistency
#5: Create an API style guide, and enforce it during the CI
process.
Speccy by Phil Sturgeon is an awesome OpenAPI linter.

stoplight.io
Shared Assets
#6: Extract common patterns and models into a shared
asset registry.
Enforce usage of these shared assets where appropriate.

stoplight.io
Version From the Start
#7: Bake versioning into all remote URL $refs.

stoplight.io
OpenAPI at Scale
Bake versioning into all URL $refs.
Extract common patterns and models into a shared asset registry.
Create an API style guide, and enforce it during the CI process.
Treat your OpenAPI file like the critical asset it is, and bake contract
tests into your CI process.
Invest in a centralized registry early on.
Design first over code first.
Don’t force everybody to be an OpenAPI expert.#1
#2
#3
#4
#5
#6
#7

stoplight.io
The Stoplight Way
Thanks, and we’re hiring!

OpenAPI 3.0, which is based on the original Swagger 2.0 specification, is meant to provide a standard format to unify how an industry defines and describes RESTful APIs. The release of OAS 3.0 marks a significant milestone in the growth of the API economy — bringing together collaborators from across industries, to evolve the specification to meet the needs of API developers and consumers across the world in an open and transparent manner. We hosted a free Swagger training: OpenAPI 3.0, And What it Means for the Future of Swagger. More than 2,000 people signed up to learn more about the new specification, and to find out about what’s coming next for Swagger and SwaggerHub! You can watch the full recording of the presentation here: https://swaggerhub.com/blog/api-resources/openapi-3-0-video-tutorial/

API Docs with OpenAPI 3.0Fabrizio Ferri-Benedetti

OpenAPI Intro (1).pdfPostman

Writing REST APIs with OpenAPI and Swagger AdaStephane Carrez

The presentation was held in the Ada devroom at the FOSDEM 2018. The OpenAPI specification is an emerging specification to describe RESTful web services. The Swagger suite is a collection of tools to write such API descriptions and have the code generated in more than 29 languages, including Ada. The presentation will describe how to write a REST operation with OpenAPI, generate the Ada client with Swagger Codegen and use the generated code to interact with the server. We will also describe the generated Ada server code and how to implement the server side and run a complete REST server.

Developing Faster with SwaggerTony Tam

This document discusses how Swagger can be used to develop APIs faster. It describes what Swagger is, provides an example Swagger YAML file, and discusses how code can be generated from Swagger specifications. It also introduces Swagger Inflector, which uses the Swagger specification as the single source of truth to automatically route controllers, map models, and generate sample data when controllers are not implemented. The document encourages rethinking the DRY principle and maintaining the API specification as the central source.

Building APIs with the OpenApi SpecPedro J. Molina

OpenAPI is an the emerging standard for creating, managing and consuming REST APIs. Previously named Swagger, in the last year has been adopted by the Linux Foundation and gained the support of companies like Google, Microsoft, IBM, Paypal, etc. to become a de-facto standard for APIs. In this talk we will review 3 uses cases to apply OpenAPI to enhance and speed-up our developments to create OpenAPI compliant APIs.

What is API - Understanding API SimplifiedJubin Aghara

Rest API with Swagger and NodeJSLuigi Saetta

Api TestingVishwanath KC

This document provides an overview of API testing tools and methods. It defines APIs and REST, describes how API testing works, lists common API testing tools like Postman, and outlines different types of API tests including functionality, reliability, load, and security testing. Examples are given of the GET, POST, PUT, and DELETE HTTP methods along with response status codes. A live demo of an API is presented at the end.

Introducing SwaggerTony Tam

API Governance in the EnterpriseApigee | Google Cloud

Api typesSarah Maddox

This document classifies and describes different types of APIs. It discusses web service APIs like REST and SOAP, library-based APIs that interface with programming languages like JavaScript, class-based APIs for platforms like Java and Android, OS APIs that allow access to system functions and hardware, and object remoting APIs like CORBA. Examples are provided for many API types. The document is intended to provide an overview of the various ways that software applications can communicate through defined programming interfaces.

Automate REST API TestingTechWell

As an organization grows, the body of code that needs to be regression tested constantly increases. However, to maintain high velocity and deliver new features, teams need to minimize the amount of manual regression testing. Eric Smith shares his lessons learned in automating RESTful API tests using JMeter, RSpec, and Spock. Gain insights into the pros and cons of each tool, take back practical knowledge about the tools available, and explore reasons why your shop should require RESTful automation as part of its acceptance test criteria. Many decisions must be made to automate API tests: choosing the platform; how to integrate with the current build and deploy process; and how to integrate with reporting tools to keep key stakeholders informed. Although the initial transition caused his teams to bend their traditional roles, Eric says that ultimately the team became more cross-functionally aligned and developed a greater sense of ownership for delivering a quality product.

What is an APIElliott Richmond

An API is a set of routines, protocols, and tools that allow software applications to communicate with each other. It defines the functionality that is independent of implementation. An API expresses the operations, inputs, outputs, and types of a software component. It allows creation of applications that can access features or data from an operating system, application, or other service. An API acts as an intermediary that allows two applications to communicate, delivering requests from one app to a provider and returning the response.

Api testingHamzaMajid13

SwaggerNexThoughts Technologies

Introduction to red hat agile integration (Red Hat Workshop)Judy Breedlove

Rest api standards and best practicesAnkita Mahajan

Belajar Postman test runnerFachrul Choliluddin

This document discusses various types of API testing including functionality, usability, reliability, load, creativity, security, proficiency, and documentation testing. It provides two examples of API tests - one to test getting a list of countries and another to test getting details of a single country. Key aspects covered include generating test data, preparing variables, using prepared variables in tests, running test collections, and reviewing test results. The overall document provides guidance on developing comprehensive API tests.

Api presentationTiago Cardoso

This document provides an overview of a RESTful JSON API. It discusses that the API uses a REST design with JSON as the output format. It also describes other common protocols like SOAP and XML-RPC. The API is intended for use by desktop, mobile, and third-party web applications that can communicate over HTTP. Key aspects covered include input-output design, error handling, documentation, and user authentication using OAuth. The API implementation leverages the Sinatra framework with common logic modules to share data and configuration across applications. SDKs are also discussed to help integrate external apps with the API.

B4USolution_API-Testingb4usolution .

Getting Started with API Standardization in SwaggerHubSmartBear

This document provides an overview of a presentation on standardizing API documentation using SwaggerHub. The agenda includes an introduction to SmartBear and their tools, why standardization is critical for API quality, defining quality for teams, challenges of OpenAPI Specification development at scale, and how SwaggerHub can help address those challenges. It discusses how SwaggerHub provides a central hub for designing, documenting, and collaborating on APIs to improve efficiency, quality and reduce defects.

Swagger / Quick Start GuideAndrii Gakhov

The document provides an overview of Swagger 2.0 and how it can be used to define REST APIs. Swagger allows both humans and computers to understand APIs without access to code or documentation. It includes a specification and tools like an editor, code generation, and UI. The document demonstrates defining a sample DEMO API in Swagger format and generating interactive documentation with Swagger UI. It also introduces PySwagger for testing APIs based on their Swagger definition.

API Testing: The heart of functional testing" with Bj RollisonTEST Huddle

View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-81-api-testing-the-heart-of-functional-testing An API, or Application Programming Interface, is a collection of functions that provide much of the functional capabilities in complex software systems. Most customers are accustomed to interacting with a graphical user interface on the computer. But, many customers do not realize the much of the functionality of a program comes from APIs in the operating system or program's dynamic-link libraries (DLL). So, if the business logic or core functionality is exposed via an API call then and if we want to find functional bugs sooner than API testing may be an approach that provides additional value in your overall test strategy. Additionally, API testing can start even before the user interface is complete so functional capabilities can be tested while designers are hashing out the "look and feel." API testing will not replace testing through the user interface, but it can augment your test strategy and provide a solid foundation of automated tests that increase your confidence in the functional quality of your product.

Understanding REST APIs in 5 Simple StepsTessa Mero

This document summarizes the 5 steps to understanding REST APIs: 1) Understanding the purpose of APIs and their importance and growth, 2) Learning that REST defines functions to communicate via HTTP verbs and nouns, 3) Knowing that APIs use requests and responses, 4) Relying on documentation as the reference, and 5) Using debugging and testing tools to prevent issues. It provides examples of requests, responses, API documentation, and tools like Postman for working with REST APIs.

Postman Collection Format v2.0 (pre-draft)Postman

The document proposes a new version 2.0 format for Postman collections that is: - A minimalist and flexible JSON guideline for defining APIs and collections in a human readable way. It allows for extensive documentation, testing, and organization of API definitions. - Built on a JSON structure that can be easily extended and manipulated via a Node.js module. It supports all aspects of API management from modeling to testing to documentation. - Designed to be intuitive with a low learning curve, while still providing the flexibility to extensively document APIs, collections and their components through embedded descriptions and metadata.

Using Typespec for Open Finance Standards - Chris Wood, Ozone APINordic APIs

A presentation given by Chris Wood, Principal Architect, Ozone API, at our 2024 Platform Summit, October 8-9. The development of API standards is critical to helping markets grow their open finance ecosystem. Standards bodies typically use OpenAPI to help create API standards, but their efforts can be accelerated by using compatible design tools like TypeSpec. In this talk we’ll uncover what it means to use TypeSpec for design-first standards development, and dig into the lessons learned from the approach.

Copyright, Open Source and APIs (towards an Interface Commons)

The document discusses copyright and APIs, noting that while recent court rulings have established that APIs cannot be copyrighted, there remains uncertainty and a lack of clarity. It suggests that rather than asserting copyright over APIs, the community would be better served by sharing interfaces through an "interface commons" that encourages open reuse and attribution. Doing so could speed innovation by reducing coding work and improving interoperability between systems.

More Related Content

What's hot (20)

What is API - Understanding API SimplifiedJubin Aghara

Rest API with Swagger and NodeJSLuigi Saetta

Api TestingVishwanath KC

Introducing SwaggerTony Tam

API Governance in the EnterpriseApigee | Google Cloud

Api typesSarah Maddox

Automate REST API TestingTechWell

What is an APIElliott Richmond

Api testingHamzaMajid13

SwaggerNexThoughts Technologies

Introduction to red hat agile integration (Red Hat Workshop)Judy Breedlove

Rest api standards and best practicesAnkita Mahajan

Belajar Postman test runnerFachrul Choliluddin

Api presentationTiago Cardoso

B4USolution_API-Testingb4usolution .

Getting Started with API Standardization in SwaggerHubSmartBear

Swagger / Quick Start GuideAndrii Gakhov

API Testing: The heart of functional testing" with Bj RollisonTEST Huddle

Understanding REST APIs in 5 Simple StepsTessa Mero

Postman Collection Format v2.0 (pre-draft)Postman

What is API - Understanding API SimplifiedJubin Aghara

Rest API with Swagger and NodeJSLuigi Saetta

Api TestingVishwanath KC

Introducing SwaggerTony Tam

API Governance in the EnterpriseApigee | Google Cloud

Api typesSarah Maddox

Automate REST API TestingTechWell

What is an APIElliott Richmond

Api testingHamzaMajid13

SwaggerNexThoughts Technologies

Introduction to red hat agile integration (Red Hat Workshop)Judy Breedlove

Rest api standards and best practicesAnkita Mahajan

Belajar Postman test runnerFachrul Choliluddin

Api presentationTiago Cardoso

B4USolution_API-Testingb4usolution .

Getting Started with API Standardization in SwaggerHubSmartBear

Swagger / Quick Start GuideAndrii Gakhov

API Testing: The heart of functional testing" with Bj RollisonTEST Huddle

Understanding REST APIs in 5 Simple StepsTessa Mero

Postman Collection Format v2.0 (pre-draft)Postman

Similar to OpenAPI at Scale (20)

Using Typespec for Open Finance Standards - Chris Wood, Ozone APINordic APIs

2022 APIsecure_Securing APIs with Open StandardsAPIsecure_ Official

Securing APIs with Open Standards provides tips for securing APIs from the Synack Red Team. It discusses using OpenAPI definitions to document APIs, embracing open box testing, and balancing security and adoption through developer relations. It also demonstrates how insecure user input validation can allow access to private data stored in AWS S3 buckets and how Salesforce record IDs can be brute forced to enable unauthorized access if not properly secured. The presentation emphasizes designing APIs with security in mind, adopting standards like OpenAPI, and balancing security testing with developer onboarding.

Open event (show&tell april 2016)Jorge López-Lago

OpenEvent is a Drupal distribution that represents an Event Open Data Model and publishes event data through a self-documented API. It aims to be a generic foundation for cultural organizations to manage and publish their events online. The distribution includes Drupal 7, the Open Data Model, Schema.org mappings, and features like a read-only API. Future plans include moving it to Drupal.org, improving documentation, refactoring custom code into reusable modules, and attending to the issue queue. Lessons learned include benefits of open source like higher developer motivation and easier code sharing.

APIdays Paris 2019 Backend is the new frontend by Antoine Cheronapidays

Bob and Alice are building a new app together, with Bob working on the backend API and Alice on the frontend. As they work, the API requirements change frequently, requiring changes to parameters, operations, and data models. This can lead to errors when the frontend code is not updated to match. The presentation proposes a solution using OpenAPI specifications enriched with semantics and hypermedia controls to advertise available operations and parameters at runtime. This would allow the frontend code to be written in a more business-focused way and automatically integrate API changes without breaking. Limitations include the difficulty of deeply linking operations to data and the work required to implement and maintain the vocabulary.

API World 2016 - A five-sided prism polarizing Web API developmentRestlet

How ChatGPT led OpenAPI's Recent Spike in PopularityPostman

OpenAPI, formerly known as Swagger, is a specification for building and documenting APIs. This talk is about the significance of OpenAPI in the world of API development and when a lot of people suddenly realised its importance for modern-day software development. We'll explore the technical aspects, wider ecosystem, and future of OpenAPI in the world of API development and discuss the benefits of OpenAPI, its role in API documentation, and its importance in building robust and scalable APIs used by leading companies (e.g. OpenAI).

Developing Brilliant and Powerful APIs in Ruby & PythonSmartBear

This document summarizes a presentation about developing brilliant APIs in Ruby and Python. It discusses choosing between Ruby and Python for APIs and frameworks like Rails, Grape, Flask and Django. It also covers API documentation, testing, and API sandboxing tools. The presentation concludes that Ruby+Rails is best for large projects while Python is great for smaller, as-needed APIs and scripting. It emphasizes the importance of documentation and how Ready! API can help test and sandbox APIs across technologies.

Walter apiNicholas Schiller

Nicholas Schiller presented on using APIs to customize library services. He demonstrated how to build a web application using the WorldCat Search API that automatically adds Boolean search terms to a user's query and formats the results. The application was built with PHP for server-side scripting, HTML5 for interface design, and jQuery Mobile to optimize for different devices. The presentation provided examples of APIs, guidelines for API projects, and resources for further learning about APIs and programming.

Space Camp June 2022 - API First.pdfPostman

A Year of Pyxley: My First Open Source AdventureNick Kridler

Simplifying the OpenAPI Development Experience confluent

This document discusses strategies for simplifying the OpenAPI development experience. It introduces Minispec, a domain-specific language and generator that produces OpenAPI specifications from high-level API descriptions. Minispec aims to reduce complexity and standardize API design. The document also outlines challenges with OpenAPI specifications, such as supporting required, immutable and contextual fields, and discusses how API linters can help address these issues. The goal is to make API design and documentation self-service for development teams.

How and Why you can and should Participate in Open Source Projects (AMIS, Sof...Lucas Jellema

For a long time I have been reluctant to actively contribute to an open source project. I thought it would be rather complicated and demanding – and that I didn't have the knowledge or skills for it or at the very least that they (the project team) weren't waiting for me. In December 2021, I decided to have a serious input into the Dapr.io project – and now finally to determine how it works and whether it is really that complicated. In this session I want to tell you about my experiences. How Fork, Clone, Branch, Push (and PR) is the rhythm of contributing to an open source project and how you do that (these are all Git actions against GitHub repositories). How to learn how such a project functions and how to connect to it; which tools are needed, which communication channels are used. I tell how the standards of the project – largely automatically enforced – help me to become a better software engineer, with an eye for readability and testability of the code. How the review process is quite exciting once you have offered your contribution. And how the final "merge to master" of my contribution and then the actual release (Dapr 1.6 contains my first contribution) are nice milestones. I hope to motivate participants in this session to also take the step yourself and contribute to an open source project in the form of issues or samples, documentation or code. It's valuable to the community and the specific project and I think it's definitely a valuable experience for the "contributer". I looked up to it and now that I've done it gives me confidence – and it tastes like more (I could still use some help with the work on Dapr.io, by the way).

Open Source Security and ChatGPT-Published.pdfJavier Perez

1) ChatGPT and other AI tools allow developers to produce code more quickly and efficiently but the validity and security of generated code must still be verified by developers. 2) While AI can introduce vulnerabilities if misused, it can also help find vulnerabilities when used properly under a developer's guidance. 3) Open source security involves continuously monitoring libraries and dependencies for vulnerabilities and applying patches through practices like software bill of materials and regular scans.

OpenACT - Meet1 - Intro to APIsOpenACT

These are the slides used for the first developer meetup, happened in Bangalore, on 5th May. Organized by OpenACT - Open API Consumers' Team For more details on OpenACT, Check our Facebook Page: https://www.facebook.com/OpenACT Twitter: https://twitter.com/#!/APITeam Webpage: http://OpenACT.org/ For upcoming events, check out: http://OpenACT.org/events

Chris Mathias Presents Advanced API Design Considerations at LA CTO ForumChris Mathias

The Open WebLachlan Hardy

The document discusses the open web and provides definitions and examples. It defines the open web as having open standards approved by standards bodies, open specifications with reference implementations and multiple vendors, and public involvement in evolution. It provides examples of open standards like HTML and open specifications like OAuth. The open web is argued to be cheaper and better through more review. Open architecture principles like readable and hackable URLs and open APIs are suggested to make systems more connected and the community empowered through open identity systems and data access.

Library, Library Lets Use THAT Library – DFW MobileAdam Hill

This document discusses how to bind native iOS libraries for use in Xamarin applications. It introduces the concepts of libraries and native binding. It describes Objective Sharpie, a tool that facilitates binding libraries by generating C# wrapper code from native iOS frameworks and libraries. It outlines the basic workflow for using Objective Sharpie to bind a library, including running Objective Sharpie against the library, adding the generated files to a binding project, and compiling. It notes some additional steps that may be needed like verifying bindings and addressing issues. It demonstrates binding a sample library and discusses alternative approaches like using CocoaPods.

Chiara Chiappini - Swift and the future of iOS app developmentCodemotion

AI assisted testing using postman and openAI.pdfsivaganeshsivakumar1

The document discusses using AI and OpenAI APIs to assist with software testing. It provides an overview of AI types like narrow, general and super intelligence. It also discusses generative AI and common tools for text, image, video and code generation. The document demonstrates how to use OpenAI APIs with Postman, including exploring ideas for API fuzzing and test result analysis. It shares the current state of AI in testing tools and how AI could help with other testing activities beyond automation.

Using Typespec for Open Finance Standards - Chris Wood, Ozone APINordic APIs

2022 APIsecure_Securing APIs with Open StandardsAPIsecure_ Official

Open event (show&tell april 2016)Jorge López-Lago

APIdays Paris 2019 Backend is the new frontend by Antoine Cheronapidays

API World 2016 - A five-sided prism polarizing Web API developmentRestlet

How ChatGPT led OpenAPI's Recent Spike in PopularityPostman

Developing Brilliant and Powerful APIs in Ruby & PythonSmartBear

Walter apiNicholas Schiller

Space Camp June 2022 - API First.pdfPostman

A Year of Pyxley: My First Open Source AdventureNick Kridler

Simplifying the OpenAPI Development Experience confluent

How and Why you can and should Participate in Open Source Projects (AMIS, Sof...Lucas Jellema

Open Source Security and ChatGPT-Published.pdfJavier Perez

OpenACT - Meet1 - Intro to APIsOpenACT

Chris Mathias Presents Advanced API Design Considerations at LA CTO ForumChris Mathias

The Open WebLachlan Hardy

Library, Library Lets Use THAT Library – DFW MobileAdam Hill

Chiara Chiappini - Swift and the future of iOS app developmentCodemotion

AI assisted testing using postman and openAI.pdfsivaganeshsivakumar1

More from Nordic APIs (20)

How to Choose the Right API Platform - We Have the Tool You Need! - Mikkel Iv...Nordic APIs

A presentation given by Mikkel Iversen, Business Development Director at Redpill Linpro, at our 2024 Platform Summit, October 8-9. In this session we will demo a tool developed by Redpill Linpro to help you choose the right platform to support your API initiative. The evaluation model combines AI and our vast experience from the API and integration space to help you choose the platform that best suits your requirements.

Bulletproof Backend Architecture: Building Adaptive Services with Self-Descri...Nordic APIs

A presentation given by Sean Travis Taylor, Head of Platform at Redeem, at our 2024 Platform Summit, October 8-9. The ability for web services to adapt to changes is crucial for maintaining seamless integration and operational efficiency throughout the many services that stitch together commerce, work and play across the vastness of the Internet.Illustrated with a fictional case study from the ecommerce sector, this talk introduces an approach to achieving such adaptability through the use of self-describing messages: a method where each message carries all the required data and metadata necessary for processing, without relying on any external data handling or centralized knowledge.Our case study involves an ecommerce storefront that relies on data from a third-party vendor with a highly volatile API. Despite the vendor’s frequent API changes, our approach using self-describing messages ensures that the storefront maintains uninterrupted service, safeguarding both sales and customer experience. This example not only underscores the robustness of self-describing messages in handling API volatility but also highlights their role in preventing business disruptions and reducing the need for frequent developer interventions and cross-functional meetings.The session will also discuss major advantages of systems that incorporate self-describing messages like improved scalability and easier updates and upgrades without centralized data handling. By the conclusion of this talk, attendees will appreciate the strategic value of implementing self-describing messages to enhance service adaptability and maintain business operations in the face of constant change.

Implementing Zero Trust Security in API Gateway with Cilium - Pubudu Gunatila...Nordic APIs

A presentation given by Pubudu Gunatilaka, Senior Technical Lead at WSO2, at our 2024 Platform Summit, October 8-9. Cilium, an open-source, cloud-native solution using eBPF, can integrate with the Kubernetes Gateway API to significantly enhance API management with advanced networking, security, and observability features. It offers high-performance, programmable networking for modern cloud-native environments. This session will overview Cilium and the Kubernetes Gateway API, looking at current capabilities and how to use these technologies to enhance both north-south and east-west-style API management. Attendees will walk away with actionable advice for using state-of-the-art cloud-native tools to improve API management and a zero-trust security posture.

Event-Driven Architecture the Cloud-Native Way - Manuel Ottlik, HDI Global SENordic APIs

A presentation given by Manuel Ottlik, Product Owner for Global Integration Platform at HDI Global SE, at our 2024 Platform Summit, October 8-9. When it comes to integrating software, you can choose between synchronous integration, most often done through REST APIs, or asynchronous communication, often referred to as event-driven architectures. While the synchronous world is pleasantly simple, asynchronous communication still lacks interoperability in terms of protocols, brokers and registries. Going cloud-native with the CloudEvents project for common event metadata and xRegistry as an approach to standardising the management of this metadata in registries will increase this interoperability and ultimately make your life easier when working with event-driven architectures.

Navigating the Post-OpenAPI Era with Innovative API Design Frameworks - Danie...Nordic APIs

A presentation given by Daniel Kocot, Head of API Consulting at codecentric AG, at our 2024 Platform Summit, October 8-9. The Post-OpenAPI Era in API design marks a pivotal shift towards innovative frameworks like Microsoft TypeSpec, TaxiLang, Fern, and Apple Pkl, offering solutions beyond OpenAPI’s constraints. This talk dives into how these frameworks transform API design, providing flexibility, expressiveness, and improved developer experiences. We’ll explore the features and advantages of each framework, demonstrating their potential to enhance API documentation, client generation, and collaborative design processes. Highlighting real-world case studies, we illustrate the positive impact on development speed, usability, and end-user satisfaction. Attendees will gain insights into integrating these frameworks into development workflows, understanding the future landscape of API development, and envisioning the possibilities this new era brings.

Schema-first API Design Using Typespec - Cailin Smith, MicrosoftNordic APIs

A presentation given by Cailin Smith, Senior Software Engineer at Microsoft, at our 2024 Platform Summit, October 8-9. TypeSpec is a relatively new open source schema language coming out of Azure. In this talk, I will introduce you to the basics of using TypeSpec, and how apps.methodscript.com uses a Schema-First API design, allowing for developers to skip writing glue code, while maintaining a gigantic client support matrix, minimizing bugs, and speeding up API development.

Avoiding APIpocalypse; API Resiliency Testing FTW! - Naresh Jain, XnsioNordic APIs

A presentation given by Naresh Jain, Founder & CEO of Xnsio, at our 2024 Platform Summit, October 8-9. As we build more complex distributed Applications, the resilience of APIs can be the linchpin of application reliability and user satisfaction. This demo will delve into practical tools and techniques used to enhance the resilience of APIs. We will explore how we utilise API specifications for simulating various input data, network conditions and failure modes to test how well the API handles unexpected situations. Our demo will begin with an overview of API resilience — why it matters, and what it means to build robust APIs that gracefully handles flaky dependencies in real-world operations. We'll discuss the role of contract testing in achieving resilience and how to turn API specifications into executable contracts that can be continuously validated. We'll also cover how to integrate with CI/CD pipelines and practices to foster better collaboration between API stakeholders through shared understanding and executable documentation.

How to Build an Integration Platform with Open Source - Magnus Hedner, BenifyNordic APIs

A presentation given by Magnus Hedner, Manager of Integration Platforms at Benify, at our 2024 Platform Summit, October 8-9. The talk of the town is "the great unbundling". We've added "... using open source." There are a lot of tool vendors, offering complete bundles including all components you need (Yes I have worked with a few of those). But there is also an alternative, if you want to have full control of the components of your integration platform. This is a talk on how we have built an integration platform, comprising API gateways, an integration tool, security, monitoring, and how we tailor it to our needs.

API Design First in Practise – An Experience Report - Hari Krishnan, SpecmaticNordic APIs

A presentation given by Hari Krishnan, Co-founder & CTO at Specmatic, at our 2024 Platform Summit, October 8-9. API Design First requires that all stakeholders adhere to the spec that has been agreed. Come join me in this talk where I share our experience helping team instantly convert API specs into executable contracts to help them independently develop and confidently deploy their components. This approach of using API specs as executable contracts addresses several shortcomings associated with code generation based techniques we had tried in the past. I will also be sharing how we went about iterative API Design to allow for collaborative evolution of features. And mainly avoiding breaking compatibility during API evolution. Key takeaways: 1. API Specifications to API Tests in seconds – Also generative API coverage report (similar to code coverage, but for APIs) to verify adherence for API implementations 2. API Specifications as API Mocks 3. Backward Compatibility Testing – API Spec vs API Spec 4. Using Linters effectively 5. Extracting common API Specification elements and reusing them 6. Single source of truth for API specifications to promote collaboration between all stakeholders

The Right Kind of API – How To Choose Appropriate API Protocols and Data Form...Nordic APIs

A presentation given by Sumit Amar, Vice President of Engineering at WEX , at our 2024 Platform Summit, October 8-9. In this session we will evaluate various data formats (JSON, XML, Protocol Buffers, and YAML), and discuss their pros and cons in varying scenarios. We will also evaluate how they pair with adequate data channels (HTTP/S, Binary over gRPC, gRPCweb in browsers, or Web Sockets). We will review various API use cases and map them with the right combination of data formats and channels for best performance, scalability, and maintainability.

Why Frequent API Hackathons Are Key to Product Market Feedback and Go-to-Mark...Nordic APIs

A presentation given by Per Lange, Founder at Cillers, at our 2024 Platform Summit, October 8-9. An API hackathon is an event where developers learn how to build something interesting on top of a specific company’s API. These gatherings are crucial for software companies targeting developers. Frequent API hackathons are particularly valuable because they quickly reveal and address fundamental platform issues. Getting the basics right is essential—a trait that distinguishes the world's fastest-growing tech companies. And with the next hackathon fast approaching, there's a renewed urgency within the CTO and product teams to address these persistent issues. This ensures that developers won't encounter the same problems at successive events. Additionally, API hackathons enhance product awareness and familiarity. When developers become acquainted with your technology and realize that your software significantly improves upon critical business use cases, many will switch to your solution. In this speech, Per Lange will detail how to run world-class API hackathons effectively and frequently.

Maximizing API Management Efficiency: The Power of Shifting Down with APIOps ...Nordic APIs

A presentation given by Dominic Lüchinger, Senior Platform Engineer at SIX Group, at our 2024 Platform Summit, October 8-9. APIOps is a methodology that combines GitOps and DevOps to streamline API management. Learn how it empowers product teams, ensuring regulatory compliance, reducing cognitive load, and accelerating time to market. Discover the power of shifting down with a self-service platform approach. Does your organization need a platform engineering team for this? With real-world examples and actionable insights, this session will enable you to bootstrap APIOps effectively in your organization to continuously improve your API offerings.

APIs Vs Events - Bala Bairapaka, Sandvik ABNordic APIs

A presentation given by Bala Bairapaka, Solution Architect Sandvik AB, at our 2024 Platform Summit, October 8-9. Event-Driven Architecture (EDA) and APIs (Application Programming Interfaces) offer distinct approaches to system design. EDA uses asynchronous communication where components emit and react to events, making it highly scalable and suitable for real-time applications like IoT and financial transactions, though it can be complex to manage. In contrast, APIs typically use synchronous communication with a request-response model, resulting in tighter coupling but easier implementation, ideal for CRUD operations and microservices. While EDA excels in scenarios requiring real-time processing and scalability, APIs are better suited for web services and applications needing straightforward, synchronous interactions. Understanding these differences can help you choose the right architecture for your project’s specific needs. In this talk I will highlight how EDA’s real-time processing can revolutionize industries by enabling instant data analysis and decision-making. Imagine the power of a system that can react to events as they happen, driving innovations in fields like IoT and financial services. You will learn the simplicity and ease of use of APIs, which can significantly speed up development and integration processes, allowing businesses to bring new features to market faster than ever before. I will share real-world examples to make these concepts tangible: how EDA powers high frequency trading platforms, ensuring transactions are executed in milliseconds, or how APIs streamline interactions in popular web services, making our daily digital experiences seamless. When I illustrate these practical applications, you’ll not only informed but also take inspired actions and learn transformative potential of choosing the right architecture for your projects.”

GraphQL in the Post-Hype Era - Daniel Hervas, Reckon DigitalNordic APIs

A presentation given by Daniel Hervás, Lead Engineer / Technical Coordinator at Reckon Digital, at our 2024 Platform Summit, October 8-9. Around 2019, the year of the creation of the GraphQL Foundation, GraphQL saw a huge boom in popularity and started getting mass adoption from API devs worldwide. Now, in 2024, other technologies and trends have taken the spotlight (crypto, LLMs, AI...), and the buzz around GraphQL APIs seems to have died down somewhat... so what happened to it? Is it still relevant? Should you be building a GraphQL API in 2024 if you want to be one of the cool kids? Mature, stale, boring, or still trendy and useful? In this talk, we'll go over the current state of the GraphQL ecosystem, what the community, through extended usage throughout these years, has found to be good and bad use cases for GraphQL, and in which situations it makes sense to expose a GraphQL API layer. This talk will be of interest to both technical and non-technical audiences.

From Good API Design to Secure Design - Axel Grosse, 42CrunchNordic APIs

A presentation given by Axel Grosse, Global Head of Presales at 42Crunch, at our 2024 Platform Summit, October 8-9. - How to fortify your APIs leveraging AI assistants and static and dynamic testing - 85% of enterprises acknowledge suffering an API attack in 2023. This practical session demonstrates how security and development teams can collaborate to improve the overall security posture of an API implementation. Attendees will learn how to test and harden their OpenAPI Description to support a rock solid runtime protection and in parallel how to find and fix vulnerabilities in code for secure end-to-end API delivery. During the session you’ll see how Static and Dynamic API test and assessments are run and learn how to utilize the Copilot API assistant to lend a helping hand with code remediation. How to fortify your APIs leveraging AI assistants and static and dynamic testing 85% of enterprises acknowledge suffering an API attack in 2023. This practical session demonstrates how security and development teams can collaborate to improve the overall security posture of an API implementation. Attendees will learn how to test and harden their OpenAPI Description to support a rock solid runtime protection and in parallel how to find and fix vulnerabilities in code for secure end-to-end API delivery. During the session you’ll see how Static and Dynamic API test and assessments are run and learn how to utilize the Copilot API assistant to lend a helping hand with code remediation.

API Revolution in IoT: How Platform Engineering Streamlines API Development -...Nordic APIs

A presentation given by Alina Astapovich & Gang Luo, Site Reliability Engineer & SRE Manager at Electrolux, at our 2024 Platform Summit, October 8-9. As the IoT landscape continues to expand rapidly, the role of APIs in managing and controlling connected devices becomes increasingly critical. At Electrolux, where we support over 10 million appliances globally, API development is essential for delivering meaningful digital experience to our consumers. In this talk, we dive into our journey of transforming API development through Platform Engineering at Electrolux Digital Experience Organization. We will look at the challenges we overcame, addressing critical aspects such as managing public and private APIs, implementing diverse security mechanisms, and enforcing API governance. Furthermore, we will explore strategies for enhancing developer experience through self-service API provisioning, empowering developers to innovate more efficiently. Join us to gain insights into how Platform Engineering has streamlined API development at Electrolux.

Unlocking the ROI of API Platforms: What Success Actually Looks Like - Budhad...Nordic APIs

A presentation given by Budhaditya Bhattacharya, Developer Advocate at Tyk, at our 2024 Platform Summit, October 8-9. By 2026, 80% of software engineering organizations are expected to have a platform engineering initiative, with APIs and API management platforms playing a key role in driving the platform engineering success. While this journey has already begun in several organisations, there are several questions that are being asked over and over again: What does a good API platform actually look like? Which KPIs should we pursue, and how would they translate into ROI? How are more mature API platform teams achieving their objectives? In this presentation, we will explore the answers to these questions through real-world case studies across industries. We will take a closer look at: The key metrics and KPIs they set out to achieve Challenges they faced Strategies they implemented to overcome them How you can apply these strategies to evolve your platform maturity

Increase Your Productivity with No-Code GraphQL Mocking - Hugo Guerrero, Red HatNordic APIs

A presentation given by Hugo Guerrero, Sr. Principal Developer Advocate at Red Hat, at our 2024 Platform Summit, October 8-9. You're about to embark on a new adventure that incorporates GraphQL! Here's a filthy method for becoming a ten-time engineer: fake it until you make it! Mocking GraphQL allows you to better serve the business by providing clear descriptions of schemas, types, and examples. This also aids in the separation of front-end and back-end activities. Join this session to learn more about getting started with GraphQL mocking without having to worry about coding or constructing your own fake server.

Securely Boosting Any Product with Generative AI APIs - Ruben Sitbon, Theodo ...Nordic APIs

A presentation given by Ruben Sitbon, Lead Solution Architect at Theodo Fintech, at our 2024 Platform Summit, October 8-9. ChatGPT has changed the way people and companies perceive the value of artificial intelligence. Many startups have launched products with generative AI at their core, and innovative SaaS players have all integrated GenAI extensions or plugins, but it’s now clear that users will continue to expect bigger and better GenAI upgrades to the features of products they use on a daily basis. Ruben Sitbon describes how a framework relying on generative AI in-house APIs can be used to easily boost product features, and bundle security and continuous compliance.

GraphQL, REST or RPC? Making the Choice! - Rob Allen, Nineteen Feet LimitedNordic APIs

A presentation given by Rob Allen, API Consultant at Nineteen Feet Limited, at our 2024 Platform Summit, October 8-9. When you've been tasked with creating an HTTP API, the fundamental decision you need to make is which architecture to choose. Should your API be RESTful? What about GraphQL? or RPC? In this session, I'll explain the choices and how each works. We'll then look at their strengths and weaknesses in order to help guide your decision. By the end of this talk, you'll be well-placed to choose the right API architecture for your project.