* VIRTUAL API WORLD WORKSHOP STAGE A
Tuesday, November 1, 2022
You can provision a cloud native GraphQL API layer and start serving applications within minutes. However, readying this layer for production workloads has its challenges. For starters, what if the number of requests grows 2x, 10x, or 100x? Or, what if the data volume goes from 10GB to 100GB and then 1TB? And what if a cloud availability zone that hosts the API layer experiences outages? Lastly, what if your API layer needs to serve user requests with low latency across distant countries and continents.
Join this hands-on session where we’ll build a geo-distributed GraphQL API layer that tolerates major cloud outages, serves user requests with low latency regardless of whereabouts, and easily complies with data residency requirements when expanding to new territories.
Graphql live queries and subscriptions have a strong case while thinking about creating real time web apps. While both approaches converge to trying to keep the client state in sync with the server, they differ in ways in which they are implemented and give rise to new patterns altogether. By understanding how they behave under the hood, we can decide the best approach based on our use case.
Building APIs that support multiple user experiences in a complex domain often means using microservices — but while microservices are great for developing, they can be more challenging for your API users and for cross-platform integrations. This is how we use BFFs (Backend-For-Frontend) and BAEs (Backend-Async-Events) at Jetty to alleviate this problem
Wednesday, November 2, 2022
This session will present the concept of integrationless. It represents a parallel with serverless, where the complexity of integrating with multiple sources will hide in a unique API that internally will orchestrate the connections with the multiple data sources. Leaf is a company of this type. We created an API for agriculture that hides the complexity of integrating multiple sources normally present in an AgTech application.
[#VIRTUAL] PRO TALK (API): The Evolving Developer Lifecycle: Best practices for API Builders and Consumers
The API industry is undergoing tremendous changes - driven by a generational shift in the technologies powering APIs and a transformation in enterprise buying patterns. While APIs have been around for a while, the way they look, work, operate and are consumed is changing rapidly. This change challenges current design patterns and developer tools and necessitates creating a more contextual approach to API development.
In his talk, Iddo examines the evolution of the API development lifecycle and the current best practices engineered to support API builders and consumers. The speaker will examine the key technologies required to build, consume, and collaborate on APIs across the entire software development lifecycle.
There are lots of API security myths that keep teams in stasis, using traditional tools to combat new problems, specifically assumptions about attackers and attack traffic. After standing up a public-facing honeypot to gather test data, we learned a few things, and what to do about the new API reality.
[#VIRTUAL] PRO TALK (API): Happy Agents = Happy Customers: Empower Your Customer Service Team to Lead the Way
Keeping on top of your organization’s technical platforms as well as customer experience is a daunting task, and it can't be done by siloed teams. Your Customer Service team and the insight they gain from users is critical to the incident identification and response process, and your development teams can use this insight as data to speed up their ability to resolve the problem. As the team closest to the customer, incorporating your customer service team into the DevOps lifecycle will reduce silos, shorten feedback loops, empower agents, grow careers and delight your customers.
Come to this session to learn about bringing customer service teams in line with development teams, organizational goals, and improving agent experience to improve the customer experience. In this talk, you will learn the importance of aligned customer service ops, and how to help your customer service and dev teams establish strong practices of collaboration as one team in service of your customers.
APIs have become one of the cornerstones of digital transformations. As more and more businesses open up their APIs for public consumption, the concept of developer experience becomes crucial for the successful rollout of the APIs. Good developer experience with APIs depends on good principles of API governance, API management, and API design.
In this presentation, we explain how the principles of domain-driven design help us design APIs that are easier to understand and to consume. APIs are not just an HTTP interface to a database, and we’ll see how to use DDD to define the domain of an API and to model its resources. We’ll use strategic design to narrow down the scope of an API, and to avoid mixing properties from different domains. We’ll also discuss various heuristics that we can use to translate domain models and actions into the more restricted representational capabilities of REST APIs and CRUD operations.
The result of this exercise will be a well-structured API with consistent paths and resources that developers will love to use to and to build integrations with.
Everyone is jumping on the API-first bandwagon. For most organizations, an API-first approach is the key to scaling software development. But the journey to API-first is not always smooth sailing.
In 2022, I interviewed five well-known organizations for a sneak peek at how they implemented an API-first workflow among their teams. We’ll uncover why they began their transition, their biggest hurdles, and what is next on their roadmap. Learn from these shared experiences and recommendations to pave the way in your own API-first journeys. This is a session about managing organizational change.
[#VIRTUAL] PRO TALK (API): API as Products: Best Practices for Using APIs to Achieve your Digital Business Goals
Organizations that want to create internal momentum and adoption around their APIs, offer APIs externally to third-parties, or create new revenue streams through monetization, you need to think about your APIs as products. This talk examines the key guidelines needed to define your APIs as products, build the framework to operationalize your API program, and design and execute an implementation plan. Specifically, the presenters will cover:
- Best practices for assessing and resourcing the people and tooling to support API products.
- Strategies for establishing objectives for your internal and external API programs and the metrics to evaluate them.
- Guidance on building and implementing internal rollout and external GTM plans.
[#VIRTUAL] PRO TALK (API): Transitioning to an API First Approach: Refactoring a Museum Interactive Platform
New to API design and development, I decided to start small in order to gain experience (this is what the experts advise). I decided to tackle a low-ish priority project: the redesign of the in-gallery interactive platform.
I mean - I read all the right books and attended the industry conferences (and took notes). I followed this up by watching the appropriate four (4) plus star-rated tutorials AND my task lists worked as designed. I'm the jump-in kinda person and really, how hard could this be?
Find out as I share the joys and challenges of taking the baby-steps to transition our way of thinking to an API-First approach.
APIs are great. However, API architectures have not significantly evolved. With GraphQL, designed for stitching data together, a new way of forming a graph of graphs is emerging. This architecture leads to a simpler design, better performance, simpler governance and graceful migration to the cloud. It is the way forward.
I will be drawing from my over a decade of experience as the CTO of Apigee, and seeing the impact of GraphQL, I will demonstrate how evolving your API architecture with a layer of GraphQL leads to leveraging your years of REST investment into a more flexible future proof architecture.
Design principles for modeling API contract. Best practices for API security. How to address scaling challenges like latency, fault tolerance and throughput. When to use rest, gRPC or GraphqL.
Thursday, November 3, 2022
For developers interested in the decentralized Web, or Web3, infrastructure-as-a-service (IaaS) platforms can pave the way to a frictionless and scalable developer experience. Opting for an open API standard encourages integration due to ease of implementation while facilitating interoperability.
In this session, E.G. Galano will discuss those best practices when developing the infrastructure for blockchain APIs, how to battletest API infrastructure at scale and how to build a reliable API that appeals to both developers and enterprises. This session will explore open API capabilities that will drive adoption.
We've all built internal APIs, and at some point we decide to expose this out externally / build external APIs. This is a session designed to talk about the best practices and pitfalls when product managers and engineers design external facing APIs after having built mainly internal APIs.
What should we be more mindful of, why we need to rethink our data model, and how important is technical documentation for folks trying to integrate with your systems?
The success of a public facing API isn't just how many qps's you can handle, and security concerns -- its all about the ease for developers (like yourself!). I'll talk about my learnings, and what can help you design robust systems that developers will love integrating with. The easier it is for developers to integrate with your external API, the more successful your API becomes automatically.
I'll most importantly talk about how I've had to change my mindset after having built only internal product APIs (almost exclusively) previously, and how I've managed to move from APIs that were used for a few hundred updates into ones that can do billions of updates each day.
Picsart built a 150M monthly creators strong consumer business with its app that offers hundreds of individual tools for fast editing. And now the company is exploring new territory with their new API program designed to make their most popular consumer creative tools available to enterprises and platforms via API. Learn how Picsart’s API team built a new revenue stream from existing tech but with a completely new business approach.
Nothing strikes fear into the hearts of developers like the terms no-code and low-code (except maybe AI). DevOps has us wanting to move fast and automate everything, but we don’t want low-code platforms to replace developers' jobs! A survey of 600 engineers had them reflect on what they wish they could spend less time on: 37% spent on manual testing of changes/writing scripts; 35% spent on refactoring old code; and only 33% spent on writing code for new features. In this talk we will discuss how low-code API management can increase developer productivity and raise developer potential by allowing them to focus on creative problem-solving. All through a single, organization-wide view.
[#VIRTUAL] PRO TALK (AI): Leveraging Automated Machine Learning to Enable Anyone to Develop Machine Learning Solutions
Nowadays, several business owners know that leveraging Artificial Intelligence capabilities, on their systems and applications, can enable their businesses to achieve better results. But building Artificial Intelligence solutions may be a time-consuming and complex process, so consequently, some of these people give up of building such solutions, since they or their team do not have the expertise and capacity required, or sometimes they end-up paying to third-party companies to build these solutions and as a consequence, they end-up doing a significant investment on building these solutions. Azure Automated Machile Learning is the solution to enable anyone to build the Artificial Intelligence and Machine Learning solutions at low cost and with the best quality possible.
Recent trends in web development have enabled us to build websites that are entirely static, where all dynamic interaction is done in the browser. How do you deploy these static sites without hard-coding backend server details? Feature flags to the rescue! Join us in this session as we explore how even static sites can become fully dynamic with the addition of OpenFeature apis. In this session we’ll extend a statically hosted JAMstack application with OpenFeature apis solving the crucial question of how we can deploy static sites that aren’t hard-coded to a given back-end.
When Marsh McLennan established a core APIs team in April of 2021, one of the first priorities was to create a set of API standards for the organization. But after blending together industry exemplars, RFCs, internal best practices and the occasional meme or two, the forty-six page document that resulted didn’t lead to the API revolution we’d expected. Focusing on closely integrating the standards with OpenAPI specification led to increased adoption across the internal developer community. Come and learn how the team used the OpenAPI Specification to drive standards compliance, improve collaboration and allow for easy maintenance and iteration of the standards over time.
You wrote an API specification, documented your endpoints, and published SDKs. Here’s a question, though: Does your API actually solve your users’ problems?
API providers often fail to address common use cases to solve users’ needs, or their assumptions don’t match the reality. This may end up in frustration and loss of users.
In this talk, we will take a peek into developers’ mindset. I will show how to better understand the developers’ needs by researching the usage patterns, existing libraries and 3rd party experience layers, provide examples of good and bad practices, and suggest actionable steps to improve developer experience for your API.
Are you blocked by manual processes, inefficiencies, and knowledge silos? Are developers happy or frustrated? Join me and we’ll explore some of the ways you can enable developers to do their best work and improve the developer experience through a focus on tools, processes, and collaboration.
With the increased cloud adoption, smaller autonomous development teams, and microservices we need a way to ensure consistency and productivity. In this talk we’ll explore topics like: boilerplate templates, development environments, CI/CD, code reviews, and effective documentation.
If you’re a developer trying to improve your work day-to-day or an engineering leader trying to empower your teams, this talk has something for you.
Style guides are one of the most effective tools to build consistent APIs that follow best practices. Automated style guides increase the effectiveness of style guides by making it easy for developers/designers to do the right thing. In this session, we'll go through best practices for creating API style guides and making them part of the CI/CD process.