Pain Points In API Development? They’re Everywhere

Nov 1, 2018Download as PPTX, PDF2 likes1,007 views

There’s an inherent tension for organizations doing API development: how to keep both your API developers as well as your infrastructure happy, at the same time. Decoupling front-end and back-end development allows parallel development, and helps keep your front-end, middle-end, and back-end efforts working asynchronously. This speeds progress, but requires far more – and far better – collaboration to be successful. Even an independent developer working with APIs requires good collaboration tools. In this talk, Abhinav Asthana will provide tips on how to improve in API development using collaboration tools like executable API descriptions, API mock servers, and documentation. He will include specific examples of how companies (such as VMware, Coursera, and AMC Theatres) have used collaboration to attain more agile development, to onboard developers, and to ensure input from all participants/stakeholders.

PRESENTED BY
Pain Points in
API Development
Abhinav Asthana
Founder & CEO, Postman

Source: ProgrammableWeb
APIs have become pervasive.
That’s why we are here!
Modern Software
is built on APIs.

Postman’s Perspective
5M+ Developers 2.5M+ Collections Created

APIs are technical AND business abstractions

Common problems
while building APIs
Lots of things can go wrong while
building APIs
• Internal abstractions being exposed
externally
• APIs exposing programming language
constructs (error messages, data types)
• Developers might not understand objects
inside your API
• Designing only for specific use cases
• Not accounting for undocumented surface
area - Every observable behavior of the API
will be consumed by a developer (Hyrum’s
Law - www.hyrumslaw.com)

Common problems
while using APIs
• Little or no documentation
• Just reference documentation
• No use cases
• No successful case studies
• Unclear business rules (rate limiting, pricing,
constraints)

Framework:
Technical Abstraction
QA
DevOps
Tech Writers
Architects
Data
Engineers
Partner
Engineers
Integration
Engineers
Security
Engineers

Framework:
Product Abstraction
DevRel
Sales
Engineers
Support
Engineers
Product
Marketers
Business
Analysts
Publishers

Why do we have
problems?
• Disconnect between loops internally and
externally is the source of all problems when
it comes to building and promoting your APIs
• Similar to building a product but affects APIs
more as you can expose internal technical
issues externally
• Pushing out a public API is a cross
disciplinary effort

How to fix this?
• Review all of your loops
• Create transparency through communication
channels in these loops
• Get a dedicated manager to see through all
these
• Write stuff down

Put all your APIs in one place
#1 Tips for INTERNAL APIs

Count the number of meetings that
happen while you are building your API
#2 Tips for INTERNAL APIs

Tips for INTERNAL APIs
Introduce a change in your API and
trace impact
#3

Build a maturity model for your APIs
#4 Tips for INTERNAL APIs
99
80
95
90
100
90
0 25 50 75 100
Quality
Agility
Availability
Resilience
Security
Performance

Use public APIs for internal applications
#5 Tips for INTERNAL APIs

Developer-friendly design - look at
patterns but don’t overinvest
#1 Tips for EXTERNAL APIs

Clarify versioning guidelines
#2 Tips for EXTERNAL APIs

Create walkthroughs - use Run in
Postman, Apps
#3 Tips for EXTERNAL APIs

Provide a public roadmap
#4 Tips for EXTERNAL APIs

Provide a public issue tracker to
catch open bugs
#5 Tips for EXTERNAL APIs

Conclusion
1.Pain points in API development come from lack of clarity in the
organization's development loops
2.Development loops should be documented and studied - they vary
from org to org
3.Feed information back into the development loop and map out
changes in the process

You may have heard the term “API Product.” But what does it mean? In this talk I will introduce the concept and explain the benefits and challenges of transforming your organization to view your APIs as measurable products that expose your companies capabilities creating agility, autonomy, and acceleration. Traditional product manufacturers create new product and launch them into the marketplace and then measure value; we will teach you to view your APIs in the same way. Concepts covered in this presentation will be designing APIs with Design Thinking, funding your product, building teams, marketing your API, managing your marketplace, and measuring success.

API MonetizationCapgemini

This document discusses API monetization strategies for banks. It notes that banks currently view other entities like big tech companies and fintechs as competitors, but expect them to become partners in a future banking ecosystem enabled by APIs. It outlines key business questions around using APIs to create new revenue streams and monetization models like pay-per-use, tiered pricing, and revenue sharing. The document provides examples of APIs being successfully monetized and best practices for API management. It recommends developing a roadmap within 8-10 weeks to prioritize API opportunities and quickly focus API investments.

MuleSoft's Approach to Driving Customer Outcomes MuleSoft

MuleSoft's approach to driving customer outcomes centers around three pillars: business outcomes, technology delivery, and organizational enablement. They provide six paths for customers to focus on along with playbooks for each path. The goal is to establish a foundation, build to scale, plan for success, and measure impact. MuleSoft offers services like Catalyst Launch to help customers deploy Anypoint Platform, implement initial use cases, build a Center for Enablement, and develop dashboards and KPIs. They work closely with customers to ensure success through customized delivery approaches, offerings, and engagement styles.

How to Execute a Successful API StrategyMatt McLarty

This document discusses executing a successful API strategy through a programmatic approach. It begins by outlining the digital age and how APIs serve as digital enablers, allowing companies to transform digitally. It then discusses what an API program entails and how to execute one through establishing a digital strategy, aligning the organization and culture, evaluating technologies, and engaging the ecosystem. The document also outlines several API program workshops that can help organizations at different stages of an API program, from strategy to productization of APIs.

Azure Synapse AnalyticsWinWire Technologies Inc

SAP PI POIntegration Srini

More Information here: https://www.integrationsrini.com/sap-po/complete-understanding-of-sap-pi/ SAP Process Integration or SAP PI PO is the On-Premise Integration Tool that is released by SAP Company. The main purpose of SAP Process Integration Tool is to integrate Applications within the company landscape or with external partner applications. SAP Process Integration is one of the component of SAP Process Orchestration Product. Process Orchestration: SAP Process Orchestration is a combo product that has 3 components: SAP Process Integration. Business Process Management. Business Rules Management.

Inflectra Partner Program 2022Inflectra

Life Cycle Of Pre SalesShobhit Khanna

VILT - Archiving and Decommissioning with OpenText InfoArchiveVILT

OpenText InfoArchive is an application-agnostic solution, for managing information and archiving, supporting different enterprise needs of information ingestion, for all kinds of applications. It allows for the application management cost reduction, an information governance enhancement while adding value to the business process through information re-utilization. It provides four information ingestion methods, in order to cover the most demanding requirements on all concurrent projects, while optimizing the information source application. With OpenText InfoArchive there is no need to go for a single approach for all archiving and decommissioning needs.

Amazon Connect & AI - Shaping the Future of Customer Interactions - GenAI and...CloudHesive

Sap hana tutorialSridhar Kasthuri

SAP HANA is an in-memory database that can be deployed on-premise or in the cloud. It is optimized for real-time analytics and application development. At the core is the SAP HANA database, which uses in-memory column-based storage for ultra-fast data access. SAP HANA Studio provides tools for administration, modeling, and application development on SAP HANA. It includes perspectives for system administration, database development, and application development.

Disaster Recovery for SAP HANA with SUSE LinuxDirk Oppenkowski

Introduction to MuleSoftSalesforce Developers

With the MuleSoft Anypoint Platform, you can build scalable data integrations and flows across any application, data source, and device - whether in the cloud or on-premise. The platform provides a suite of out-of-the-box connectors that work across any system, and you can customize them to whatever you need with minimal code. This means you can integrate and deploy innovative, robust customer apps even faster. Join this webinar, learn the basics of the Anypoint Platform, and see how it works with Salesforce and any of your third party systems.

[AI] ML Operationalization with Microsoft AzureKorkrid Akepanidtaworn

I am an instructor of the MLOps workshop for some anonymous startup incubation program where the objectives are (1) to orchestrate and deploy updates to the application and the deep learning model in a unified way. (2) To design a DevOps pipeline to coordinate retrieving the latest best model from the model registry, packaging the web application, deploying the web application and inferencing web service.

How do OpenAI GPT Models Work - Misconceptions and Tips for DevelopersIvo Andreev

Introduction to Azure DatabricksJames Serra

Databricks is a Software-as-a-Service-like experience (or Spark-as-a-service) that is a tool for curating and processing massive amounts of data and developing, training and deploying models on that data, and managing the whole workflow process throughout the project. It is for those who are comfortable with Apache Spark as it is 100% based on Spark and is extensible with support for Scala, Java, R, and Python alongside Spark SQL, GraphX, Streaming and Machine Learning Library (Mllib). It has built-in integration with many data sources, has a workflow scheduler, allows for real-time workspace collaboration, and has performance improvements over traditional Apache Spark.

Architecting an Enterprise API Management StrategyWSO2

The document discusses strategies for architecting an enterprise API management strategy. It covers factors to consider like whether to treat APIs as a product or tactic. It also discusses API management components like the API publisher and store. The document outlines reference architectures like using API management within an orthogonal toolset. It provides examples of API management for use cases like within a telecommunications ecosystem.

Azure Synapse Analytics Overview (r1)James Serra

Azure Synapse Analytics is Azure SQL Data Warehouse evolved: a limitless analytics service, that brings together enterprise data warehousing and Big Data analytics into a single service. It gives you the freedom to query data on your terms, using either serverless on-demand or provisioned resources, at scale. Azure Synapse brings these two worlds together with a unified experience to ingest, prepare, manage, and serve data for immediate business intelligence and machine learning needs. This is a huge deck with lots of screenshots so you can see exactly how it works.

Demystifying Data Warehousing as a Service - DFWKent Graziano

This document provides an overview and introduction to Snowflake's cloud data warehousing capabilities. It begins with the speaker's background and credentials. It then discusses common data challenges organizations face today around data silos, inflexibility, and complexity. The document defines what a cloud data warehouse as a service (DWaaS) is and explains how it can help address these challenges. It provides an agenda for the topics to be covered, including features of Snowflake's cloud DWaaS and how it enables use cases like data mart consolidation and integrated data analytics. The document highlights key aspects of Snowflake's architecture and technology.

Integrating Security into DevOpsCloudPassage

This document discusses integrating security into DevOps practices. It notes that while DevOps embraces cloud automation and agility, security can slow things down. Traditional security approaches are ill-suited for cloud environments. The document introduces CloudPassage Halo as a security-as-a-service platform that provides automated security controls like firewall management, intrusion detection and vulnerability scanning across cloud infrastructure in a self-service manner. It also describes the CloudPassage Halo architecture and demostrates some of its features. Finally, it promotes the CloudPassage Halo API toolbox and offers six months of free developer access to the platform.

SAP-Cloud-Platform_official-solution-diagrams-and-icons_v09 (1).pptxAlexandrePachini1

This document provides guidelines for creating SAP Cloud Platform solution diagrams using standard icons, design elements, and colors. It includes: - SAP Cloud Platform service icons and other SAP icons that can be used in diagrams. - Colors, areas, and other design elements for creating diagrams in Microsoft PowerPoint. - Instructions for downloading icon packages and template slide decks for building diagrams. - Terms of use for the icons and guidelines to follow when sharing or publishing diagrams.

Devops Devops DevopsKris Buytaert

This document discusses DevOps and the movement towards closer collaboration between development and operations teams. It advocates that operations work should start early in the development process, with developers and operations communicating about non-functional requirements, security, backups, monitoring and more. Both developers and operations staff should aim to automate infrastructure and deployments. The goal is reproducible, reliable deployments of applications and their supporting systems.

Cloud Cost Optimization WhitepaperDevPro3

API Management Within a Microservices Architecture Nadeesha Gamage

Apigee Edge Overview and RoadmapApigee | Google Cloud

apidays Australia 2023 - API Strategy In The Era Of Generative AI,Shreshta Sh...apidays

apidays Australia 2023 - Platforms, Products, and People: The Power of APIs October 11 & 12, 2023 https://www.apidays.global/australia/ API Strategy In The Era Of Generative AI Shreshta Shyamsundar, Distinguished Technologist at Infosys ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

User Experience Balanced ScorecardSean Tyne

The document discusses using a balanced scorecard approach to measure user experience. It provides an overview of balanced scorecards and their four perspectives: financial, customer, internal processes, and learning and growth. It then shows how user experience strategies and objectives can be mapped to each of the four perspectives in a user experience balanced scorecard. For example, under the financial perspective, objectives could include increasing revenue and reducing costs, while under customer it could focus on increasing conversions, retention, and loyalty. The document provides examples of objectives, measures, targets, and initiatives that could be included in a user experience balanced scorecard.

Leveraging Azure DevOps across the EnterpriseAndrew Kelleher

Auckland API & Microservices Meetup 1: API led designDamian Harvey

This document summarizes a presentation on API-led design. It discusses starting the design process with APIs and crafting them to meet customer needs rather than just exposing code. The benefits of API-led design include increased agility, composability, and parallel development. A 5 step methodology is presented: create a domain model, model the state, create an API outline, verify specification, and flesh out details. RAML is introduced as a specification language that can be used to define and document APIs.

Building a REST API for LongevityMuleSoft

One of the greatest challenges to developing an API is ensuring that your API lasts. After all, you don’t want to have to release and manage multiple versions of your API just because you weren’t expecting users to use it a certain way, or because you didn’t anticipate far enough down the roadmap. In this session, we’ll talk about the challenge of API Longevity, as well as ways to increase your API lifecycle including having a proper mindset, careful design, agile user experience and prototyping, best design practices including hypermedia, and the challenge of maintaining persistence.

More Related Content

What's hot (20)

VILT - Archiving and Decommissioning with OpenText InfoArchiveVILT

Amazon Connect & AI - Shaping the Future of Customer Interactions - GenAI and...CloudHesive

Sap hana tutorialSridhar Kasthuri

Disaster Recovery for SAP HANA with SUSE LinuxDirk Oppenkowski

Introduction to MuleSoftSalesforce Developers

[AI] ML Operationalization with Microsoft AzureKorkrid Akepanidtaworn

How do OpenAI GPT Models Work - Misconceptions and Tips for DevelopersIvo Andreev

Introduction to Azure DatabricksJames Serra

Architecting an Enterprise API Management StrategyWSO2

Azure Synapse Analytics Overview (r1)James Serra

Demystifying Data Warehousing as a Service - DFWKent Graziano

Integrating Security into DevOpsCloudPassage

SAP-Cloud-Platform_official-solution-diagrams-and-icons_v09 (1).pptxAlexandrePachini1

Devops Devops DevopsKris Buytaert

Cloud Cost Optimization WhitepaperDevPro3

API Management Within a Microservices Architecture Nadeesha Gamage

Apigee Edge Overview and RoadmapApigee | Google Cloud

apidays Australia 2023 - API Strategy In The Era Of Generative AI,Shreshta Sh...apidays

User Experience Balanced ScorecardSean Tyne

Leveraging Azure DevOps across the EnterpriseAndrew Kelleher

VILT - Archiving and Decommissioning with OpenText InfoArchiveVILT

Amazon Connect & AI - Shaping the Future of Customer Interactions - GenAI and...CloudHesive

Sap hana tutorialSridhar Kasthuri

Disaster Recovery for SAP HANA with SUSE LinuxDirk Oppenkowski

Introduction to MuleSoftSalesforce Developers

[AI] ML Operationalization with Microsoft AzureKorkrid Akepanidtaworn

How do OpenAI GPT Models Work - Misconceptions and Tips for DevelopersIvo Andreev

Introduction to Azure DatabricksJames Serra

Architecting an Enterprise API Management StrategyWSO2

Azure Synapse Analytics Overview (r1)James Serra

Demystifying Data Warehousing as a Service - DFWKent Graziano

Integrating Security into DevOpsCloudPassage

SAP-Cloud-Platform_official-solution-diagrams-and-icons_v09 (1).pptxAlexandrePachini1

Devops Devops DevopsKris Buytaert

Cloud Cost Optimization WhitepaperDevPro3

API Management Within a Microservices Architecture Nadeesha Gamage

Apigee Edge Overview and RoadmapApigee | Google Cloud

apidays Australia 2023 - API Strategy In The Era Of Generative AI,Shreshta Sh...apidays

User Experience Balanced ScorecardSean Tyne

Leveraging Azure DevOps across the EnterpriseAndrew Kelleher

Similar to Pain Points In API Development? They’re Everywhere (20)

Auckland API & Microservices Meetup 1: API led designDamian Harvey

Building a REST API for LongevityMuleSoft

Rebooting APIs at scaleRahul Dighe

PayPal operates in 200+ countries. The complexity of region specific requirements and a disjointed offering led to a situation where PayPal Checkout API product suite got polluted with many overlapping capabilities and an API documentation that was hard to comprehend, incomplete and inconsistent making the integration experience much harder than it needed to be. There was a strong desire to act upon the feedback that we have been hearing from our merchants and developer community to make a turn for the better. This talk aims to explore > When is the right time for organization to rethink their API and launch a new version. > Considerations that go into creating a new version of an API that is so central to the way thousands of developers and merchants integrate with PayPal. > Explore challenges in design, adoption, migration both internally and externally within the organization.

API-Consumption compressed (1)Rahul Ghai

This document outlines a 4-step process for developing an API consumption strategy: 1) Identify your APIs' customers, 2) Design for implementation simplicity, 3) Receive and act on feedback, 4) Measure your APIs' key performance indicators (KPIs). It discusses identifying internal/external API users, designing comprehensive yet simple APIs, collecting feedback, and tracking metrics like API calls, time to first use, and error rates to maximize API value. Integrating with Azuqua can help simplify implementations, link APIs to tools like JIRA, and improve KPIs like time to first use. The strategy helps ensure APIs are meeting business goals by understanding users and continuously optimizing based on data.

API Product Management - Driving Success through the Value ChainApigee | Google Cloud

Patterns for automating API delivery. API conferencessuser9e7c64

Automating API product delivery is about automating workflows to improve the quality and delivery speed for APIs by applying APIOps principles. In this talk, I discuss patterns for API consistency checks: Enforcing API design standards with linting tools like Spectral, Redocly and Vacuum. API breaking change checks: Automating breaking-change checks with OpenAPI diff tools like Oasdiff API conformance checks: Ensuring accuracy of your API reference documents using API conformance tools like Schemathesis. API code generation: Generate server and client code using SDK generators like OpenAPI Generator

How to design effective APIsBansilal Haudakari

The document discusses principles of effective API design. It begins by defining an API as providing a way for developers to interact with and consume a service. Some key principles discussed include: 1. Designing the API first before implementing backend logic to focus on usability. 2. Choosing an appropriate runtime that allows for scalability, reliability and hybrid cloud/on-premise deployment. 3. Using API contracts to define and enforce policies and service level agreements with consumers. 4. Monitoring API usage over time to understand usage patterns and improve the consumer experience. 5. Iteratively improving APIs through continuous feedback to optimize them over time. 6. Socializing APIs by creating developer port

Your API Sucks! Why developers hang up and how to stop that.Apigee | Google Cloud

This document summarizes a presentation on how to improve APIs by focusing on the developer experience. The presentation outlines four simple rules for better APIs: 1) Give developers reasons to build on the API, 2) Make developers successful faster, 3) Don't violate developers' trust, and 4) Listen to developers. It discusses common frustrations developers have such as a lack of purpose or documentation, difficulty getting started, and lack of support. The presentation urges API providers to put themselves in developers' shoes and treat them and their APIs as products to improve adoption.

WaveMaker API SuccessWaveMaker, Inc.

WaveMaker helps enterprises develop, publish, manage, and consume APIs to create successful API programs and ecosystems. It provides a full end-to-end API solution that allows enterprises to quickly generate REST APIs from data and legacy systems, publish and securely manage APIs, and enable rapid application development for internal and external consumption of APIs. Key benefits include automated API generation, mock data creation, enterprise-grade security, detailed monitoring, and support for building an application ecosystem around published APIs.

Scaling API DesignJason Harmon

Contract {Collaboration} Driven Development - APIdays Interface 2020Alianna Inzana

In the API space, much of the conversation around Contract Driven Development has centered on the question “Did we build the API right?“. By using the contract as the foundation for a common understanding of the API, we can answer not only that question, but the equally important - but more elusive - “Did we build the right API?“. In /Contract/{Collaboration}/DrivenDevelopment, we will discuss how API Specifications and consumer-driven contracts can form the basis for cross-team collaboration in delivering quality services.

Elevating Developer Experiences with AI-Powered API Testing & DocumentationPostman

In the modern era, APIs have exploded in their popularity, powering absolutely everything we interact with on a daily basis (whether we know it or not). Maintaining their coherence and functionality has become, to say the least, a difficult task for developers and engineering leaders. As the API landscape continues to grow increasingly complex, the absence of robust testing and comprehensive documentation can lead to a cascade of issues, resulting in downstream pain for both developers and end-users alike. However, there is a silver lining on the horizon: harnessing the power of AI to help write API tests and documentation, ensuring seamless integration, improved developer experiences, and ultimately, greater efficiency in API-driven development workflows. Join us as we delve into the transformative potential of AI in shaping the future of API testing and documentation, paving the way for a more streamlined and effective development ecosystem.

Scaling API Design - Nordic APIs 2014Jason Harmon

Effective API DesignBansilal Haudakari

This document discusses principles for effective API design. It defines an API as providing a way for developers to interact with and consume a service. It outlines six principles for API design: design first, choose the right runtime, define contracts, monitor usage, continuously improve, and socialize APIs. The principles emphasize designing for developers and specific use cases, ensuring scalability and reliability of the runtime, and engaging with developers through documentation and community. Well-designed APIs that follow these principles can become valuable products and ecosystems, while mediocre APIs that don't engage stakeholders may fail to meet business objectives.

APIs as a Product StrategyRavi Kumar

Documentation, APIs & AIPronovix

This document discusses challenges with API integration and proposes augmented approaches using AI. It notes that API integration takes a long time on average of 700 days due to difficulties understanding documentation, requirements, and ecosystems. Common obstacles include domain modeling, use cases, documentation quality, and access issues. The document advocates improving documentation to explain business and product aspects beyond technical references. It envisions next-gen integration using AI like NLP to help analyze APIs and generate integration code on demand. This could enhance documentation with interactive capabilities and help applications autonomously discover and connect APIs.

Oscon2014 Netflix API - Top 10 Lessons LearnedSangeeta Narayanan

02 API Academy - path to successCHARLES Frédéric

The document discusses best practices for API design and implementation. It emphasizes starting with user-centered design principles like defining goals, identifying users, and designing interfaces with empathy. It recommends iterating the design early through sketching, prototyping and testing assumptions with users. For implementation, it suggests focusing on architectural qualities like availability, security and performance as well as maintainability, testability and integrability. The key takeaways are to define organizational value, prioritize positive user experiences, and produce effective implementations through an iterative and holistic design process.

API Economy - Cuomo Prolifics

INTERFACE, by apidays - The 8 Key Components of a Modern API Stack by Iddo G...apidays

Auckland API & Microservices Meetup 1: API led designDamian Harvey

Building a REST API for LongevityMuleSoft

Rebooting APIs at scaleRahul Dighe

API-Consumption compressed (1)Rahul Ghai

API Product Management - Driving Success through the Value ChainApigee | Google Cloud

Patterns for automating API delivery. API conferencessuser9e7c64

How to design effective APIsBansilal Haudakari

Your API Sucks! Why developers hang up and how to stop that.Apigee | Google Cloud

WaveMaker API SuccessWaveMaker, Inc.

Scaling API DesignJason Harmon

Contract {Collaboration} Driven Development - APIdays Interface 2020Alianna Inzana

Elevating Developer Experiences with AI-Powered API Testing & DocumentationPostman

Scaling API Design - Nordic APIs 2014Jason Harmon

Effective API DesignBansilal Haudakari

APIs as a Product StrategyRavi Kumar

Documentation, APIs & AIPronovix

Oscon2014 Netflix API - Top 10 Lessons LearnedSangeeta Narayanan

02 API Academy - path to successCHARLES Frédéric

API Economy - Cuomo Prolifics

INTERFACE, by apidays - The 8 Key Components of a Modern API Stack by Iddo G...apidays

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.

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.

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.