We live in a competitive world. That competition forces change. It has always forced change. Change is normal. The question is not whether our organisations will change, that’s a given, but can we see this change before it hits us, do we know where we’re heading or are we simply floating aimlessly being carried by a river? It certainly feels that way sometimes. To answer the question we need to understand our landscape, the economic forces at play, the context we operate within and our situational awareness of this. Can we navigate the waters, can we see a storm coming or are we being battered by rocks because we refuse to look?
During this talk we will examine the level of situational awareness within business, why it matters and whether we can anticipate and exploit change before it hits us. We look into the changes that are occurring with the development of serverless, why now, what’s important to it, how it will change the way we do business and how this interacts with the API economy. There’s a lot of fuss about serverless and in this session will try to paint a clearer picture or at the very least a map of where it is going.
RESTful web services have been around for quite some time and are very popular. Many of the known public web APIs claim to be RESTful. However, many current APIs do not fulfill an important element of REST: Hypermedia as the Engine of Application State (HATEOAS). This session gives an overview of the topic and shows many concrete examples why RESTful Hypermedia APIs are useful. Kai will introduce various hypermedia formats, like HAL and Siren, as well as their integration into existing infrastructures, such as the Spring Stack. Kai also provides practical tips for creating API documentation. The goal of this session is that all attendees can decide whether hypermedia offers advantages for their own REST API.
Successful API programs need to navigate technical, organisational, and cultural obstacles to
achieve success. These obstacles have the potential to derail your journey and consume API efforts
unnecessarily if not anticipated. They may also impact the business results you seek from your API
program. Attend this informative session and learn how to navigate the path to success with APIs
whether you are in the design phase, implementation, or just thinking about the APIs in your future. We will share best practices and learnings from customers in the banking, automotive, healthcare and
It shows interfaces to security access systems (BOSCH) to access a network of (currently) 9 storage facilities and dispensing machines and how data is handled. It dives into team management issues and asynchronous data handling spanning 4 data realms, 5 countries and 2 languages from user sign-up to invoicing the drink across tax, language and legal borders.
As the microservice architecture pattern gains more and more popularity people are also finding the complexities running such a set of services. Using an API gateway can mitigate some of the complexity as it provides a single-point-of-contact for clients and a layer to handle cross-cutting concerns such as authorization and rate limiting.During this talk we’ll introduce the concept of an API Gateway and the audience will learn the benefits it can bring, both architecturally and from DevOps point of view. We’ll also see some deployment techniques how to easily manage an API Gateway in the deployment pipelines.
Microservices present a new way of scaling API deployments, where each component is an island, performing a small but well defined task. These systems are quicker to develop and allow for a more agile way of working. As in most designs, security is not part of the original blueprint, which can lead to expensive and hard to manage security solutions. In this talk, Travis Spencer will illustrate how OAuth and OpenID Connect can be leveraged to created a unified distributed framework for Microservices. He will show how this can be used to deliver Microservices’ promise of agility and scalability while also ensuring security.
Microservices have been a topic for years now. Traditional micro services architectures often choose the UI as it’s platform for integrating the services, which often results in small, decoupled backend services, but a tightly coupled, hard to maintain, monolithic frontend application.Micro frontends are the obvious solution to that problem: we take the learnings from the backend to the frontend. We will discuss different micro-frontend approaches, their up- and their downsides.
With the massive usage of APIs, and the exposure of private and confidential data, companies
have become targets of sophisticated cyber-attacks including brute force login attacks, data theft,
account takeover, and API DoS/DDoS attacks which require Artificial Intelligence for reliable detection.
This presentation from Elastic Beam and Axway will explore how the integration of an Artificial
Intelligence engine with a strong API platform automatically detects and blocks new cyberattacks on
Remember when setting up an auth system was easy? Me neither. From the signup form, the login form, password reset form, and all the validation in between it can easily take weeks if not months to get something basic up and running. Then you have to deal with all the security considerations. No thanks. During this presentation, the attendees will be introduced to OpenID and OAuth. They will learn how to leverage these technologies to create secure applications, but most importantly, they will learn why and how to delegate authorization and authentication so they can focus on their real work and forget about all that security stuff.
Are you using RESTful web services to provide data for your apps? "Sure, what else?" Well, then you should take a closer look at GraphQL. GraphQL is a query language for your API and is used by Facebook, GitHub and others as an alternative to RESTful web services. In this session you will find out what GraphQL is and how it can improve your daily work. Furthermore, you will see how GraphQL works on the client and on the server side. You love REST? You “hate” REST? You are somewhere in between or you think “REST, what else?”. Take a look over the rim of the tea cup and maybe fall in love with GraphQL.
Hypermedia and REST are alive and well. The JSONAPI.org specification is a wire protocol for incrementally fetching and updating a graph over HTTP. This presentation will demonstrate how JSON API provides the developer ergonomics of GraphQL with the performance benefits of caching atomic data.
Liferay is an open source platform started in 2000, long before the term “Web API” existed. One early characteristic of Liferay has been its great extensibility, which included providing a featureful HTTP API to access its functionalities since the very beginning. Initially this API used SOAP (as well as other less used protocols). Later a new “RESTful” option was added, leveraging HTTP+JSON and it became much more popular (even though it was at Level 0 in Richardson Maturity Model). However, both approaches lead users of the API to have a high coupling that makes the evolution of the APIs a challenging task. So we started wondering, isn’t there a better way to build APIs in 2017?
This session explains our search to find a better alternative and what we learned along the way.
It focuses on how we have adopted Hypermedia and Shared Vocabularies to create a new breed of APIs that we believe form the secret ingredients that solve the most important challenge we have in the API Economy: evolvability. We are now successfully applying this type of APIs in all of our products, one premise, cloud based, … even internal. We hope to inspire others to do the same.
Do you ever wake up in a cold sweat, thinking that your mobile apps are both boring and stupid? When this happens, you start to question yourself, asking why your apps aren’t more empathetic, why they don’t respond better to your users’ needs. Even if you have built a performant app with a great UI, you can improve it by leveraging new methods of adding machine learning to your apps to create a really useful and enticing mobile app experience. In this talk, you’ll learn some basics of machine learning and how to integrate it into your mobile app, first with some clever APIs, and then with custom trained models using TensorFlow. Come learn how to send your apps back to school and level up their innate ‘intelligence’!
Our job is hard. We build things that does everything from makepeoples lives simpler, to changing the world and also let’s face to make someone else rich. Regardless of which, there are a lot of things we need to care about to hammer out the best possible solution:
Architecture, patterns, 3rd party vendors, frameworks, tools, libraries. Did someone say users?
Sometimes we lay awake at night wondering if we can save another CPU cycle or wether we tested everything. Then, if we are “lucky enough” to work on the frontend, we have to say goodbye to one framework a week, by 6 months everything we know is almost guaranteed to be obsolete.
We spend our career in a hamster wheel of continuous learning and retraining while someone throws tasks or bugs at us. It’s easy to feel stressed out, even though we might love our craft. In all that chaos we need to find our inner voice, what we feel passionate about, what makes us bring our A-game.
There are different ways to become awesome, different ways to keep your sanity. Let’s explore what those are and hopefully you will feel inspired enough to look forward to that morning commute.
By now I bet your company has hundreds, maybe thousands of services, heck you might even consider some of them micro is stature! And while many organizations have plowed headlong down this particular architectural path, your spidey sense might be tingling...how do we keep this ecosystem healthy? In this talk, I will go beyond the buzzwords into the nitty gritty of actually succeeding with a service based architecture. We will cover the principles and practices that will make sure your systems are stable and resilient while allowing you to get a decent night's sleep!
Redesigning a public web service API is a major undertaking: 3 years, thousands of hours of work, new clients, new documentation, a series of releases... This is the story of the DNSimple API v2, a project that started with a single, innocuous GitHub pull request with the title "Proposal for versioned API" in December 2013, and which came to a successful general availability launch at the end of 2016. Simone will explain some of the decisions that the team took over the last 3 years that shaped the development of the API as well as challenges the team faced, and provide you with tips and techniques that may help you in your next major API project. Finally, the important question: what's next?
One of the main issues we have encountered when scaling teams and projects is to keep standard APIs among clients and services. OpenAPI, JSONAPI, custom APIs… each team usually has their own standards and preferences, but when providing public APIs is crucial to keep a common interface. In order to support that, elaborate acceptance criterias at organization level and ensure them in your software lifecycle is a must. Extracting and sharing unit-tests among teams has been our approach.
GraphQL is new and exciting query language from Facebook. It's a new way to query data from multiple resources that puts the consumer of the API in charge. Using it you will have happier Developers, less memory consumption and less orchestration. Come learn how this will revolutionise API development as you know it.
REST-APIs are today’s foundation of many modern software projects. Whether simple web-services, more complex web-apps,mobile-clients or rich client applications, all of them can simply be integrated to server side business logic published via REST endpoints.
This presentation proposes an alternative approach to the development of REST APIs in Java, Ruby or Python: The development of REST APIs in Go. Go is a statically typed, compiled and performant Programming language that is well suited for building REST-APIs without using an additional web framework. Go is easy to learn, has a simple and powerful concurrency model and outstanding HTTP, REST- und JSON-support. Go compiles to statically linked binaries that are cross-plattform enabled and therefore easy deployable without the need of any external dependency on the target platform.
This talk targets server side web developers and introduces the major aspects of REST development in Go followed by a simple example from an e-commerce context. Return fun to backend programming!
2. Go’s standard library packages net/http and encoding/json
3. Domain-Model, Ressources and URIs
6. Optional: Deployment
The talk prepares participants to form their own opinion whether Go will be an alternative to their traditional REST API development.
Google wants to rank your sites better, your users want to use your pages more often and the rise of the smartphone made it necessary: Making pages load fast and right on a great variety of devices is not really complicated, but there is a lot to consider. This presentation gives you a detailed step-by-step guide to squeeze the milliseconds out of your internet pages. Starting at the server level and covering everything up to the application layer and HTML5 know-how.
More and more web applications using Angular today need a kind of map, either to just display their location, or visualize their data. These data can be from points/locations of services/places/etc, or a user input, to more complex visuals like heatmaps or paths. These visualizations can easily be achieved with the Google Maps JS API. However, the integration with Angular and the use of its tools is not always straightforward. In this presentation I will show examples of how to integrate Google Maps easily into your Angular application without the use of any external libraries. Part of the presentation will also show some techniques for visualising spatial data on these maps.
The biggest challenge of Deep Learning technology is the scalability. As long as using single GPU server, you have to wait for hours or days to get the result of your work. This doesn't scale for production service, so you need distributed training on the cloud eventually, or take advantage of pre-trained models. Google has been building infrastructure for training the large scale neural network on the cloud for years, and started to share the technology with external developers.
In this session, we present pre-trained ML services such as Cloud Vision API and Speech API that works without any training. In addition, we introduce Cloud AutoML, which helps customizing our pre-trained models with your data. Also, we look at how TensorFlow and Cloud Machine Learning can accelerate custom model training with Google's distributed training infrastructure.
As we move beyond a world of using just a handful of internal and external APIs, to a reality where we operate thousands of microservices, and depend on hundreds of 3rd party APIs, modern API infrastructure begins to look as complex as a municipal transit system. Realizing that API operations is anything but a linear life cycle, let’s begin to consider that all APIs are in transit, evolving from design to deprecation, while still also existing to move our value bits and bytes from one place to another. I would like to share with you a look at how API operations can be mapped using an API Transit map, and explored, managed, and understood through the lens of a modern, Internet enabled "transit system".
APIs are positioned as an answer in a lot of cases; the wave bringing the future. Not so long ago, these were Mobile Apps - where the quest of making an app trumped the need for it. APIs are the new business and brand strategy. In this hype of creating APIs, important questions tend to get lost; questions that allow for focus and educated decisions during your API journey. In this talk, we deconstruct these less obvious questions behind APIs, and equip you to seek answers at this conference. We present an API inception deck of questions!
A bit of a back story. We interact with lot of teams creating APIs where most discussions exist in the technical realm. They include the battles of opinions like "object oriented versus functional", "versioning in the URL versus the header", or "to micro or to macro". The API inception deck is an effort to bring your team on the same page, and keep focus. It is a deck of questions that are broader than first impressions or quick thinking. They are fundamental to why you're here and making this API. That allows your team to structurally discover, research and validate aspects of your API.
Come explore 100 stops along the modern API life cycle, from definition to deprecation. Taking the learnings from eight years of API industry research, extracted from the leading API management pioneers, I would like to guide you through each stop that a modern API should pass across, mapped out using a familiar transit map format, providing an API experience I have dubbed API Transit. This new approach to mapping out, and understanding the API life cycle as seen through the lens of a modern municipal transit system allows us to explore and learn healthy patterns for API design, deployment, management, and other stops along an APIs journey. Which then becomes a framework for executing and certifying that each API is following the common patterns which each developer has already learned, leading us to a measurable and quantifiable API governance strategy that can be reported upon consistently. This workshop will go into detail on almost 100 stops, and provide a forkable blueprint that can be taken home and applied within any API operations, no matter how large, or small.