Versioning APIs

•Als PPTX, PDF herunterladen•

1 gefällt mir•267 views

Marcelo Cure

Talk about Versioning APIs and contracts

Technologie

Be cautious
● Too many versions;
● Complexity;
● Bugs;

Version as path/query
parameter
https://host/api/v1/bands/1/albuns
https://host/api/bands/albuns?version=
1 ● Explicit
● Cleaner for consumers
● Intrusive

Version as a header
Accept: application/json; version=1.0
● Less intrusive
● Does not polute URL
● No specification for that

Take care of your contracts
● It’s your front door
● Care about your design
● Discuss contract changes, do it cautiously
● Test your contracts

Bad design -> contract break -> versioning

You need to get used...
Contracts break, it’s
natural

Weitere ähnliche Inhalte

Ähnlich wie Versioning APIs

How to Version your API

Vance Faulkner

Apidays Paris 2023 - Software and APIs for Smart, Sustainable and Sovereign Societies December 6, 7 & 8, 2023 Real-Life REST API Versioning: Strategies and Best Practices Alexandre Touret, Software Architect at Worldline ------ 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/

Apidays Paris 2023 - Real-Life REST API Versioning, Alexandre Touret, Worldline

apidays

Collaborative Contract Driven Development

Billy Korando

Designing a json/rest api for your mobile app

Olivier Destrebecq

API presentation

Carlos Justiniano

The next generation of google APIs (Ade Oshineye)

Ontico

These are the slides from the "Continuous Updating with VersionEye" talk at code.talks 2014 in Hamburg. Nowadays modern software development without open source is almost impossible. In average a modern software project has 100 open source components. How do you keep track of these open source dependencies? How do you know that they are still alive? How do you manage the licenses for these dependencies? These are all important questions which get answered in this talk.

Continuous Updating with VersionEye at code.talks 2014

Robert Reiz

Approaching APIs

Ross Singer

Versioning rest api's

Gabriel Passos

Python monorepos what, why and how (shared)

benjyw

Api tools overview

Olivier Thomann

Let us begin by admitting that API Versioning is a difficult task. For APIs like Newsdata.io news API Development teams can make a variety of changes to an API throughout its lifecycle (enhancements, bug fixes, adding new capabilities, etc.). How would you know whether a particular change necessitates a new API version? How would you convey this to customers? How much time would consumers have to make the switch? All of these questions can be answered with careful planning.

Versioning Best Practices for API Architecture.pdf

Aparna Sharma

Who Took The Cookie From The Cookie Jar?

Olivier Thomann

Simple Web Services with PHP

John Paul Ada

The motivation on why and when to use API-First service design. What are the real-life poblems in application development with regard to API's ? And how to solve these using tools like Swagger Editor , Swagger UI and Swagger-codegen. And how can an API Manager tool help to manage the Apllication Lifecycle of your API ( publishing , versioning, registration of consumers , quota's and rate-limiting )

Api-First service design

Stefaan Ponnet

APIs, APIs and more APIs

Anand Sawant

Eclipse and API tooling

Eclipse Day India

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.

Pain Points In API Development? They’re Everywhere

Nordic APIs

VersionEye for PHP User Group Berlin

Robert Reiz

Versioning Best Practices for API Architecture.pdf

Aparna Sharma

Ähnlich wie Versioning APIs (20)

How to Version your API

Apidays Paris 2023 - Real-Life REST API Versioning, Alexandre Touret, Worldline

Collaborative Contract Driven Development

Designing a json/rest api for your mobile app

API presentation

The next generation of google APIs (Ade Oshineye)

Continuous Updating with VersionEye at code.talks 2014

Approaching APIs

Versioning rest api's

Python monorepos what, why and how (shared)

Api tools overview

Versioning Best Practices for API Architecture.pdf

Who Took The Cookie From The Cookie Jar?

Simple Web Services with PHP

Api-First service design

APIs, APIs and more APIs

Eclipse and API tooling

Pain Points In API Development? They’re Everywhere

VersionEye for PHP User Group Berlin

Versioning Best Practices for API Architecture.pdf

Mehr von Marcelo Cure

Api design

Marcelo Cure

Zero mq

Marcelo Cure

Dev ops engineering and chatbots

Marcelo Cure

Building restful ap is with harvester js

Marcelo Cure

Cqrs, event sourcing and microservices

Marcelo Cure

Immutability and immutable js

Marcelo Cure

Functional programming with python

Marcelo Cure

Polymer

Marcelo Cure

Hexagonal Architecture

Marcelo Cure

What's the value of the metrics

Marcelo Cure

Scala

Marcelo Cure

SciPy - Scientific Computing Tool

Marcelo Cure

Test driven development

Marcelo Cure

Usability testing

Marcelo Cure

Corona

Marcelo Cure

Apache lucene - full text search

Marcelo Cure

Mehr von Marcelo Cure (16)

Api design

Zero mq

Dev ops engineering and chatbots

Building restful ap is with harvester js

Cqrs, event sourcing and microservices

Immutability and immutable js

Functional programming with python

Polymer

Hexagonal Architecture

What's the value of the metrics

Scala

SciPy - Scientific Computing Tool

Test driven development

Usability testing

Corona

Apache lucene - full text search

Kürzlich hochgeladen

Tracing the root cause of a performance issue requires a lot of patience, experience, and focus. It’s so hard that we sometimes attempt to guess by trying out tentative fixes, but that usually results in frustration, messy code, and a considerable waste of time and money. This talk explains how to correctly zoom in on a performance bottleneck using three levels of profiling: distributed tracing, metrics, and method profiling. After we learn to read the JVM profiler output as a flame graph, we explore a series of bottlenecks typical for backend systems, like connection/thread pool starvation, invisible aspects, blocking code, hot CPU methods, lock contention, and Virtual Thread pinning, and we learn to trace them even if they occur in library code you are not familiar with. Attend this talk and prepare for the performance issues that will eventually hit any successful system. About authorWith two decades of experience, Victor is a Java Champion working as a trainer for top companies in Europe. Five thousands developers in 120 companies attended his workshops, so he gets to debate every week the challenges that various projects struggle with. In return, Victor summarizes key points from these workshops in conference talks and online meetups for the European Software Crafters, the world’s largest developer community around architecture, refactoring, and testing. Discover how Victor can help you on victorrentea.ro : company training catalog, consultancy and YouTube playlists.

Finding Java's Hidden Performance Traps @ DevoxxUK 2024

Victor Rentea

Exploring Multimodal Embeddings with Milvus

Zilliz

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

The microservices honeymoon is over. When starting a new project or revamping a legacy monolith, teams started looking for alternatives to microservices. The Modular Monolith, or 'Modulith', is an architecture that reaps the benefits of (vertical) functional decoupling without the high costs associated with separate deployments. This talk will delve into the advantages and challenges of this progressive architecture, beginning with exploring the concept of a 'module', its internal structure, public API, and inter-module communication patterns. Supported by spring-modulith, the talk provides practical guidance on addressing the main challenges of a Modultith Architecture: finding and guarding module boundaries, data decoupling, and integration module-testing. You should not miss this talk if you are a software architect or tech lead seeking practical, scalable solutions. About the author With two decades of experience, Victor is a Java Champion working as a trainer for top companies in Europe. Five thousands developers in 120 companies attended his workshops, so he gets to debate every week the challenges that various projects struggle with. In return, Victor summarizes key points from these workshops in conference talks and online meetups for the European Software Crafters, the world’s largest developer community around architecture, refactoring, and testing. Discover how Victor can help you on victorrentea.ro : company training catalog, consultancy and YouTube playlists.

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Victor Rentea

MS Copilot expands with MS Graph connectors

Nanddeep Nachan

Elevate Developer Efficiency & build GenAI Application with Amazon Q

Bhuvaneswari Subramani

Six Myths about Ontologies: The Basics of Formal Ontology

johnbeverley2021

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

💥 You’re lucky! We’ve found two different (lead) developers that are willing to share their valuable lessons learned about using UiPath Document Understanding! Based on recent implementations in appealing use cases at Partou and SPIE. Don’t expect fancy videos or slide decks, but real and practical experiences that will help you with your own implementations. 📕 Topics that will be addressed: • Training the ML-model by humans: do or don't? • Rule-based versus AI extractors • Tips for finding use cases • How to start 👨‍🏫👨‍💻 Speakers: o Dion Morskieft, RPA Product Owner @Partou o Jack Klein-Schiphorst, Automation Developer @Tacstone Technology

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

UiPathCommunity

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

Zilliz

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Edi Saputra

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ 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/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

apidays

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

panagenda

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

MadyBayot

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

FWD Group - Insurer Innovation Award 2024

The Digital Insurer

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

Architecting Cloud Native Applications

WSO2

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

Kürzlich hochgeladen (20)

Finding Java's Hidden Performance Traps @ DevoxxUK 2024

Exploring Multimodal Embeddings with Milvus

Strategies for Landing an Oracle DBA Job as a Fresher

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

MS Copilot expands with MS Graph connectors

Elevate Developer Efficiency & build GenAI Application with Amazon Q

Six Myths about Ontologies: The Basics of Formal Ontology

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

presentation ICT roal in 21st century education

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Why Teams call analytics are critical to your entire business

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

FWD Group - Insurer Innovation Award 2024

Artificial Intelligence Chap.5 : Uncertainty

Architecting Cloud Native Applications

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

Versioning APIs

1. Versioning APIs Marcelo Cure

2. Why do I care?

3. Why contracts break?

4. Consumers set expectations

5. APIs evolve

6. Non breaking changes

7. Breaking changes

8. Breaks consumer :’(

9. And now?

10. Version it!

11. Be cautious ● Too many versions; ● Complexity; ● Bugs;

12. How to version my API?

13. Version as path/query parameter https://host/api/v1/bands/1/albuns https://host/api/bands/albuns?version= 1 ● Explicit ● Cleaner for consumers ● Intrusive

14.

15. Version as a header Accept: application/json; version=1.0 ● Less intrusive ● Does not polute URL ● No specification for that

16.

17. Take care of your contracts ● It’s your front door ● Care about your design ● Discuss contract changes, do it cautiously ● Test your contracts

18. Bad design -> contract break -> versioning

19. Don’t have a lot of versions

20. You need to get used... Contracts break, it’s natural

21. But not so often

22. Thanks

Versioning APIs

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie Versioning APIs

Ähnlich wie Versioning APIs (20)

Mehr von Marcelo Cure

Mehr von Marcelo Cure (16)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Versioning APIs