PayPal's APIs had become complex over time, making integration difficult for developers. To address this, PayPal redesigned their APIs based on basic principles focused on end users and developers. This included establishing clear API standards, following a design process involving use cases and resource modeling, and improving the developer experience with documentation, tools, and support. The goal was to simplify their APIs and platform to increase business agility while extending their reach through developers.
Craft Conference 2015 - Evolution of the PayPal API: Platform & CultureDeepak Nadig
PayPal provides a faster, safer way to pay and get paid online, via mobile devices and in stores. With 143 million active accounts in 193 markets and 26 currencies around the world, PayPal enables global commerce, processing more than 9 million payments every day. From its initial product which enabled consumers to exchange money via PDA devices, PayPal has been enabling online merchants to accept secure payments via PayPal, helping users access money in their PayPal accounts via ATM machines and enabling consumers to pay at POS terminals in stores.
From enabling simple HTML buttons for the web, PayPal APIs evolved over the last 14 years, and enabled integrations across a variety of channels including mobile, POS, ATMs and other connected devices like televisions and gaming consoles. Through the years, PayPal’s external APIs became increasingly inconsistent, complex and difficult to use, and its internal SOA built on proprietary approaches became tightly coupled and was crippling development.
To address these issues, PayPal began developing a new API and Services Platform in 2012 basing it on principles such as API as a Product, API First and loosely coupled services. The new API Platform was initially launched in 2013 to external developers and partners, and is now being used by PayPal’s own developers to build PayPal’s new products and experiences in hours instead of weeks.
In this talk, you will learn about how PayPal’s API Platform has evolved both internally and externally, as well as how the company’s culture has changed along with the new API Platform.
In this presentation, you will learn about how PayPal’s API Platform has evolved both internally and externally, as well as how the company’s culture has changed along with the new API Platform.
Designing API Platforms that Developers Love - New York Life Build Blue May 2017Deepak Nadig
Consumers today are increasingly using a variety of applications across web, mobile, cars and devices to find information and/or to perform their tasks. In addition, Consumers are also using multiple modes of interactions - including touch and voice - with these applications. To deliver these variety of applications and natural interaction paradigms, companies need to develop API and service platforms that can be used by their internal developers as well as external developers and partners. In order to survive and be competitive, companies need to move quickly to deliver such platforms and features. It's Not the Big that Eat the Small... It's the FAST that Eat the Slow!
Successful platforms, from companies such as eBay, PayPal, Amazon and Intuit, embody attributes such as delightful integration experience, flexibility and extensibility along with implicit developer expectations - security, quality, response time and availability.
This talk will share a recipe for building and delivering platforms that developers love - principles, best practices and approaches - across architecture, organizational and cultural - used in companies such as eBay, PayPal and Intuit.
Journey to APIs and Microservices: Best PracticesDeepak Nadig
Agility is enabled by systems that are flexible and extensible.
IEEE Standard Glossary of Software Engineering Technology defines Flexibility as the ease with which a system or component can be modified for use in applications or environments other than those for which it was specifically designed. and Extensibility as the ease with which a system or component can be modified to increase its functional capacity.
As customer needs evolve, flexibility helps with composing features and applications rapidly from using API, and extensibility helps in introducing the required changes quickly by making changes in services.
The challenge many companies have today is that they have built systems primarily as monoliths during a stage of their evolution, or have several services but they are tightly coupled. Satisfying a customer need even though the functionality already exists can take significant effort and cost.
Companies are therefore moving to APIs and microservices to address this business imperative. While many initiate this journey, most of them don’t end up with the intended outcomes - they falter or fail and go through many iterations.
This talk will share principles, best practices and approaches - across architecture, organizational and cultural - that have been applied in transforming companies such as eBay, PayPal and Intuit to APIs and Microservices.
Architecting an Enterprise API Management StrategyWSO2
A good internal and external API management strategy and architecture is key to building ecosystem platforms that lead to successful API economies in the enterprise. This workshop will look at best practices in API management using the WSO2 API Manager and Integration Platform products, which are used to rapidly implement RESTful design, enforce governance policies, safely scale solutions, orchestrate complex interaction sequences, and re-use assets. The session will also look at reference architectures and architectural recommendations of building large scale API ecosystems.
Director - Solutions Architecture at WSO2, Mifan Careem presented this session at APIdays Sydney 2015.
Craft Conference 2015 - Evolution of the PayPal API: Platform & CultureDeepak Nadig
PayPal provides a faster, safer way to pay and get paid online, via mobile devices and in stores. With 143 million active accounts in 193 markets and 26 currencies around the world, PayPal enables global commerce, processing more than 9 million payments every day. From its initial product which enabled consumers to exchange money via PDA devices, PayPal has been enabling online merchants to accept secure payments via PayPal, helping users access money in their PayPal accounts via ATM machines and enabling consumers to pay at POS terminals in stores.
From enabling simple HTML buttons for the web, PayPal APIs evolved over the last 14 years, and enabled integrations across a variety of channels including mobile, POS, ATMs and other connected devices like televisions and gaming consoles. Through the years, PayPal’s external APIs became increasingly inconsistent, complex and difficult to use, and its internal SOA built on proprietary approaches became tightly coupled and was crippling development.
To address these issues, PayPal began developing a new API and Services Platform in 2012 basing it on principles such as API as a Product, API First and loosely coupled services. The new API Platform was initially launched in 2013 to external developers and partners, and is now being used by PayPal’s own developers to build PayPal’s new products and experiences in hours instead of weeks.
In this talk, you will learn about how PayPal’s API Platform has evolved both internally and externally, as well as how the company’s culture has changed along with the new API Platform.
In this presentation, you will learn about how PayPal’s API Platform has evolved both internally and externally, as well as how the company’s culture has changed along with the new API Platform.
Designing API Platforms that Developers Love - New York Life Build Blue May 2017Deepak Nadig
Consumers today are increasingly using a variety of applications across web, mobile, cars and devices to find information and/or to perform their tasks. In addition, Consumers are also using multiple modes of interactions - including touch and voice - with these applications. To deliver these variety of applications and natural interaction paradigms, companies need to develop API and service platforms that can be used by their internal developers as well as external developers and partners. In order to survive and be competitive, companies need to move quickly to deliver such platforms and features. It's Not the Big that Eat the Small... It's the FAST that Eat the Slow!
Successful platforms, from companies such as eBay, PayPal, Amazon and Intuit, embody attributes such as delightful integration experience, flexibility and extensibility along with implicit developer expectations - security, quality, response time and availability.
This talk will share a recipe for building and delivering platforms that developers love - principles, best practices and approaches - across architecture, organizational and cultural - used in companies such as eBay, PayPal and Intuit.
Journey to APIs and Microservices: Best PracticesDeepak Nadig
Agility is enabled by systems that are flexible and extensible.
IEEE Standard Glossary of Software Engineering Technology defines Flexibility as the ease with which a system or component can be modified for use in applications or environments other than those for which it was specifically designed. and Extensibility as the ease with which a system or component can be modified to increase its functional capacity.
As customer needs evolve, flexibility helps with composing features and applications rapidly from using API, and extensibility helps in introducing the required changes quickly by making changes in services.
The challenge many companies have today is that they have built systems primarily as monoliths during a stage of their evolution, or have several services but they are tightly coupled. Satisfying a customer need even though the functionality already exists can take significant effort and cost.
Companies are therefore moving to APIs and microservices to address this business imperative. While many initiate this journey, most of them don’t end up with the intended outcomes - they falter or fail and go through many iterations.
This talk will share principles, best practices and approaches - across architecture, organizational and cultural - that have been applied in transforming companies such as eBay, PayPal and Intuit to APIs and Microservices.
Architecting an Enterprise API Management StrategyWSO2
A good internal and external API management strategy and architecture is key to building ecosystem platforms that lead to successful API economies in the enterprise. This workshop will look at best practices in API management using the WSO2 API Manager and Integration Platform products, which are used to rapidly implement RESTful design, enforce governance policies, safely scale solutions, orchestrate complex interaction sequences, and re-use assets. The session will also look at reference architectures and architectural recommendations of building large scale API ecosystems.
Director - Solutions Architecture at WSO2, Mifan Careem presented this session at APIdays Sydney 2015.
SOA and API Convergence Strategy and TacticsChris Haddad
APIs encourage connected business interactions that lead to increased revenue growth, faster time to market, and increased customer engagement. When attempting to reconcile agile API tactics with enterprise SOA guidelines, teams tune governance practices and integrate API development with back-end service life-cycles.
In this session, Chris Haddad VP - Platform Evangelism at WSO2 will describe:
Why SOA services and RESTful APIs are complementary
What architecture patterns and governance techniques align API and service development lifecycles
How to converge SOA and API strategies and implement tactics that accelerate connected business projects
The API Management journey of the British Broadcasting Corporation (BBC), a public service organisation that serves audiences around the world. From no API intelligence to a distributed solution supporting dozens of autonomous teams.
Our engineers will talk about how they have delivered our custom proxy software at scale, how they work towards not being a single point of failure and how being at the centre of the API traffic enables them to provide extra value services like SLA Monitoring for our engineering teams.
We’ll explore how new authentication mechanisms are emerging and how we as a team facilitate the expanding API management landscape, considering the independent nature of our products.
The API Economy is exploding, and this presentation explains how to extend your brand, accelerate new channel adoption and operate with API best practices.
Digital transformation is on its way and the industry is required to adopt new concepts and techniques, like the Internet of things (IoT), Cloud and Enterprise Mobility. As a matter of that, new business models arise, which need to be evaluated by companies to not lose market shares and stay in touch with the competitors.
Gartner’s vision of Bi-modal IT seems to become more and more the reality, which besides all chances, also brings a lot of challenges companies have to deal with. One essential topic for implementing the ideas of Bi-modal IT is API Management – at least from our point of view. In addition, it is also a key enabler to define a solid strategy, in order to meet the challenges with respect to digital transformation.
API Management 101: The New API Experience with WSO2WSO2
API Management is one of the most heavily discussed topics in the enterprise integration industry. As the industry progresses to deploying more microservices, adopting serverless, and embracing containers and container orchestration platforms, the need to have APIs and API management systems are increasing.
This webinar will explore the importance of APIs and API management in modern and legacy enterprise architectures.
This deck covers the why’s and how’s of:
- Creating, deploying, and managing APIs
- Versioning, documenting, and consuming APIs
- Securing, controlling, and monitoring APIs
- Engaging CI/CD and rolling out APIs into production
INTERFACE, by apidays - API Design is where culture and tech meet each other...apidays
INTERFACE, by apidays 2021 - It’s APIs all the way down
June 30, July 1 & 2, 2021
API Design is where culture and tech meet each other
Aleksei Akimov, Head of API at Adyen
Are APIs really that different from SOA? Join Alistair Farquharson, CTO, SOA Software and Sachin Agarwal, VP Product Marketing, SOA Software to learn more about how to build out a combined API and SOA strategy for your business, and understand the real differences between APIs and SOA, and lay down a common long-term unified infrastructure for all your services – past, present and future.
To view recording of this webinar please use the below URL:
http://wso2.com/library/webinars/2015/08/wso2-api-platform-vision-and-roadmap/
WSO2 API platform adopters are driving digital business and creating innovative business models. API platforms create a secure, self-service, managed, and monetized environment that increases safe connected business interactions.
In this presentation, Chris and Shiro will describe:
Key goals and challenges driving API platform adoption
WSO2 API Platform capabilities and advantages
Visionary platform use cases
Innovative customer success stories
API Introduction - API Management Workshop Munich from Ronnie MitraCA API Management
Ronnie Mitra's slides from the Layer 7 Munich API Management Workshop. This workshop will included talks from Softcon CTO Michel Dorochevsky and Layer 7 API Architect Ronnie Mitra.
The workshop Covered:
• Discover the latest trends in the API economy
• Understand why API Management is important
• Learn best practices for securely exposing your APIs
• Find out what other organizations are doing to manage their APIs
Changing the game in hospitality integrationsluisw19
The hospitality industry is undergoing the greatest transformation in its contemporary history. An industry known for its ‘high-touch’ nature and not necessarily famous for embracing the latest / greatest tech, has been forced to adapt and embrace modern technologies or risk becoming irrelevant in a post-pandemic world.
Join this talk to learn how Oracle Hospitality’s Open API strategy is changing the game in hospitality integrations by not only enabling innovation at an unprecedented rate, but also by changing the API-value chain to ensure that all participants of the Hospitality API economy benefit from this move.
apidays LIVE Paris 2021 - Spatially enabling Web APIs through OGC Standards ...apidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Spatially enabling Web APIs through OGC Standards
Dr.Gobe Hobona, Director of Product Management, Standards at Open Geospatial Consortium
Transition from SOA to APIs for the App Economy - Bending the SpoonApigee | Google Cloud
Does your business need to deploy functionality to mobile devices? To multiple channels simultaneously? At a faster pace than ever before? You have a solid SOA but it's just not flexible enough to fulfill the requirements of today's projects. You need a path to evolve your SOA.
Join Brian Pagano and David Andrzejek to discuss the imperative for APIs. Walk away an approach to extend SOA with APIs to meet the demands of business in the growing app economy.
We'll Cover:
- Complex, stateful transactions and other things SOA is good at
- Agility, scalability, transformations, and other things APIs are good at
- Expose functionality not services & use APIs to be relevant and successful in the app economy
Co-Founder and CTO, Paul Fremantle and Solutions Architect, Senaka Fernando facilitated this workshop at Jax London 2014. The workshop illustrated how API management helps organizations participate in the API Economy; with the first half of the workshop looking at the overall landscape and approaches, while the second half focusing on using Open Source API Management tooling to expose, monitor and manage APIs.
Lean Method for Building Good APIs for Business – APIOps CyclesNordic APIs
APIs are a piece of technology, but they do have a business purpose and a user, or rather a developer experience which makes them either good or horrible to use and develop. Without great business-oriented APIs, there can be no API economy. In general lean architecture methods exist but are not used enough. They are useful for DevOps and Agile development, but APIs need special attention. There is a need for a “double loop” of DevOps with APIs, that’s one thing. The more important thing is to use methods which help you to treat your API as a product while covering all important business model and architecture areas. Discussions and collaboration is the key to any successful architecture. Still, many of us design our APIs and software in endless meetings or alone, using no methods at all or methods and language known only by IT professionals. The world could do with a lot of better API designs which translate into better business. These were all reasons to develop the creative-commons licensed open and lean APIOps Cycles method (www.apiopscycles.com). This talk tells the basics of the method, plus some examples of how companies have used it.
SOA and API Convergence Strategy and TacticsChris Haddad
APIs encourage connected business interactions that lead to increased revenue growth, faster time to market, and increased customer engagement. When attempting to reconcile agile API tactics with enterprise SOA guidelines, teams tune governance practices and integrate API development with back-end service life-cycles.
In this session, Chris Haddad VP - Platform Evangelism at WSO2 will describe:
Why SOA services and RESTful APIs are complementary
What architecture patterns and governance techniques align API and service development lifecycles
How to converge SOA and API strategies and implement tactics that accelerate connected business projects
The API Management journey of the British Broadcasting Corporation (BBC), a public service organisation that serves audiences around the world. From no API intelligence to a distributed solution supporting dozens of autonomous teams.
Our engineers will talk about how they have delivered our custom proxy software at scale, how they work towards not being a single point of failure and how being at the centre of the API traffic enables them to provide extra value services like SLA Monitoring for our engineering teams.
We’ll explore how new authentication mechanisms are emerging and how we as a team facilitate the expanding API management landscape, considering the independent nature of our products.
The API Economy is exploding, and this presentation explains how to extend your brand, accelerate new channel adoption and operate with API best practices.
Digital transformation is on its way and the industry is required to adopt new concepts and techniques, like the Internet of things (IoT), Cloud and Enterprise Mobility. As a matter of that, new business models arise, which need to be evaluated by companies to not lose market shares and stay in touch with the competitors.
Gartner’s vision of Bi-modal IT seems to become more and more the reality, which besides all chances, also brings a lot of challenges companies have to deal with. One essential topic for implementing the ideas of Bi-modal IT is API Management – at least from our point of view. In addition, it is also a key enabler to define a solid strategy, in order to meet the challenges with respect to digital transformation.
API Management 101: The New API Experience with WSO2WSO2
API Management is one of the most heavily discussed topics in the enterprise integration industry. As the industry progresses to deploying more microservices, adopting serverless, and embracing containers and container orchestration platforms, the need to have APIs and API management systems are increasing.
This webinar will explore the importance of APIs and API management in modern and legacy enterprise architectures.
This deck covers the why’s and how’s of:
- Creating, deploying, and managing APIs
- Versioning, documenting, and consuming APIs
- Securing, controlling, and monitoring APIs
- Engaging CI/CD and rolling out APIs into production
INTERFACE, by apidays - API Design is where culture and tech meet each other...apidays
INTERFACE, by apidays 2021 - It’s APIs all the way down
June 30, July 1 & 2, 2021
API Design is where culture and tech meet each other
Aleksei Akimov, Head of API at Adyen
Are APIs really that different from SOA? Join Alistair Farquharson, CTO, SOA Software and Sachin Agarwal, VP Product Marketing, SOA Software to learn more about how to build out a combined API and SOA strategy for your business, and understand the real differences between APIs and SOA, and lay down a common long-term unified infrastructure for all your services – past, present and future.
To view recording of this webinar please use the below URL:
http://wso2.com/library/webinars/2015/08/wso2-api-platform-vision-and-roadmap/
WSO2 API platform adopters are driving digital business and creating innovative business models. API platforms create a secure, self-service, managed, and monetized environment that increases safe connected business interactions.
In this presentation, Chris and Shiro will describe:
Key goals and challenges driving API platform adoption
WSO2 API Platform capabilities and advantages
Visionary platform use cases
Innovative customer success stories
API Introduction - API Management Workshop Munich from Ronnie MitraCA API Management
Ronnie Mitra's slides from the Layer 7 Munich API Management Workshop. This workshop will included talks from Softcon CTO Michel Dorochevsky and Layer 7 API Architect Ronnie Mitra.
The workshop Covered:
• Discover the latest trends in the API economy
• Understand why API Management is important
• Learn best practices for securely exposing your APIs
• Find out what other organizations are doing to manage their APIs
Changing the game in hospitality integrationsluisw19
The hospitality industry is undergoing the greatest transformation in its contemporary history. An industry known for its ‘high-touch’ nature and not necessarily famous for embracing the latest / greatest tech, has been forced to adapt and embrace modern technologies or risk becoming irrelevant in a post-pandemic world.
Join this talk to learn how Oracle Hospitality’s Open API strategy is changing the game in hospitality integrations by not only enabling innovation at an unprecedented rate, but also by changing the API-value chain to ensure that all participants of the Hospitality API economy benefit from this move.
apidays LIVE Paris 2021 - Spatially enabling Web APIs through OGC Standards ...apidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Spatially enabling Web APIs through OGC Standards
Dr.Gobe Hobona, Director of Product Management, Standards at Open Geospatial Consortium
Transition from SOA to APIs for the App Economy - Bending the SpoonApigee | Google Cloud
Does your business need to deploy functionality to mobile devices? To multiple channels simultaneously? At a faster pace than ever before? You have a solid SOA but it's just not flexible enough to fulfill the requirements of today's projects. You need a path to evolve your SOA.
Join Brian Pagano and David Andrzejek to discuss the imperative for APIs. Walk away an approach to extend SOA with APIs to meet the demands of business in the growing app economy.
We'll Cover:
- Complex, stateful transactions and other things SOA is good at
- Agility, scalability, transformations, and other things APIs are good at
- Expose functionality not services & use APIs to be relevant and successful in the app economy
Co-Founder and CTO, Paul Fremantle and Solutions Architect, Senaka Fernando facilitated this workshop at Jax London 2014. The workshop illustrated how API management helps organizations participate in the API Economy; with the first half of the workshop looking at the overall landscape and approaches, while the second half focusing on using Open Source API Management tooling to expose, monitor and manage APIs.
Lean Method for Building Good APIs for Business – APIOps CyclesNordic APIs
APIs are a piece of technology, but they do have a business purpose and a user, or rather a developer experience which makes them either good or horrible to use and develop. Without great business-oriented APIs, there can be no API economy. In general lean architecture methods exist but are not used enough. They are useful for DevOps and Agile development, but APIs need special attention. There is a need for a “double loop” of DevOps with APIs, that’s one thing. The more important thing is to use methods which help you to treat your API as a product while covering all important business model and architecture areas. Discussions and collaboration is the key to any successful architecture. Still, many of us design our APIs and software in endless meetings or alone, using no methods at all or methods and language known only by IT professionals. The world could do with a lot of better API designs which translate into better business. These were all reasons to develop the creative-commons licensed open and lean APIOps Cycles method (www.apiopscycles.com). This talk tells the basics of the method, plus some examples of how companies have used it.
WSO2Con EU 2015: Securing, Monitoring and Monetizing APIsWSO2
WSO2Con EU 2015: Securing, Monitoring and Monetizing APIs
Businesses today are rapidly moving from being service enabled to being API enabled. Moving into the world of APIs brings together its own set of complexities and challenges that are tough to tackle. API security, performance, scalability, monitoring and notifications are key areas to be focusing your engineering efforts on. The WSO2 Carbon platform is a complete open source enterprise middleware platform which includes products catering to your various different enterprise needs.
This talk will focus on leveraging the extensive feature set and extensible nature of the WSO2 platform to secure, monitor and monetize your APIs. It will also touch upon some of WSO2’s experiences with customers in building API ecosystems that suit modern day enterprises.
Presenter:
Nuwan Dias
Technical Lead,
WSO2
Slide deck from a panel on Payments at the API Strategy & Practice Conference in NYC - discussing about how Payment APIs evolved at PayPal and what lessons we've learned from it. Please see the comments below for the notes for each slide (for some reason slideshare is not able to pick up the notes as the transcript - so this is the only way I could do it)
API Gateways are going through an identity crisisChristian Posta
API Gateways provide functionality like rate limiting, authentication, request routing, reporting, and more. If you've been following the rise in service-mesh technologies, you'll notice there is a lot of overlap with API Gateways when solving some of the challenges of microservices. If service mesh can solve these same problems, you may wonder whether you really need a dedicated API Gateway solution?
The reality is there is some nuance in the problems solved at the edge (API Gateway) compared to service-to-service communication (service mesh) within a cluster. But with the evolution of cluster-deployment patterns, these nuances are becoming less important. What's more important is that the API Gateway is evolving to live at a layer above service mesh and not directly overlapping with it. In other words, API Gateways are evolving to solve application-level concerns like aggregation, transformation, and deeper context and content-based routing as well as fitting into a more self-service, GitOps style workflow.
In this talk we put aside the "API Gateway" infrastructure as we know it today and go back to first principles with the "API Gateway pattern" and revisit the real problems we're trying to solve. Then we'll discuss pros and cons of alternative ways to implement the API Gateway pattern and finally look at open source projects like Envoy, Kubernetes, and GraphQL to see how the "API Gateway pattern" actually becomes the API for our applications while coexisting nicely with a service mesh (if you adopt a service mesh).
An overview of 5 new API design trends. For each, I briefly summarize, show sample code, insert community opinions, showcase open source tooling, and find examples.
- Developer Experience
- GraphQL
- AsyncAPI
- OpenAPI Specification
- OAuth & OpenID Connect
apidays LIVE Paris - The Business of APIs by Jed Ngapidays
apidays LIVE Paris - Responding to the New Normal with APIs for Business, People and Society
December 8, 9 & 10, 2020
The Business of APIs: Lessons from building the world's largest API Marketplace
Jed Ng, Tech & API Investor
apidays LIVE Hong Kong 2021 - Enterprise Integration Patterns for OpenAPI Ini...apidays
apidays LIVE Hong Kong 2021 - API Ecosystem & Data Interchange
August 25 & 26, 2021
Enterprise Integration Patterns for OpenAPI Initiatives
Hieu Nguyen Nhu, Cloud Native Senior Technical Specialist at Microsoft
Introduction to The 6 Insights of API Practice (Bill Doerrfeld)Nordic APIs
This is a session given by Bill Doerrfeld at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
At Nordic APIs, our goal is to help businesses make smart tech decisions using APIs. To that end, via events and content Nordic APIs has treaded the business and technical sides to consider holistic best practices for providing an API. In this introductory Summit keynote talk, I’ll introduce what we’ve learned in the form of 6 core tenants of API practice which we’ve also designed this conference to address. Together they define a functional and evolving API:
Platformification: Becoming an API-first company means undergoing a platformification process. This represents a global trend that many argue needs to be adopted to keep your business competitive within the digital economy.
Strategy: Even before development begins, it’s important to consider your core API strategy. This is a defensible position that aligns your tech with platform goals, strategically exposing internal assets catered to an industry niche.
Business Models: APIs have the power to improve efficiency, reduce overhead cost, open up complementary revenue streams, extend R&D, or even alter an existing business model entirely. Thus, you’ll want to determine the right monetization method that improves overall business and leads to end profitability.
Security: With new major data breaches reaching the public ear every month, the importance of digital security can never be underestimated. For APIs, much of that lies in monitoring usage, access management, and identity control.
Design: No developer wants to use an API with an ugly developer portal, unintuitive URL structures, outdated technology, or terrible lag time. In order to keep your developer consumer happy, paint the API portal and overall developer experience with an aesthetic brush.
Marketing: In order to spark adoption, you need to have more than awesome functionality. I’ll review evangelism and discovery techniques you can use to get an API in the hands of more developer users.
We’ll look at specific successful implementations of these philosophies in the wild, and mention examples from our blog and eBook content that have brought in industry experts to share their insights. I’ll initiate dialogue and open the conference up to see where we’re heading. What you can get out of embracing the core tenants of API practice?
This talk was held during the Magento Developers Paradise 2012. It describes the possibilities of PayPal's Adaptive Payments and how to use them in combination with Magento.
Mashery Presents: The Evolution of Distribution - Edwin Aoki, Chief Architect...Mashery
Whether you are in retail, media, publishing, technology or travel, the ability to distribute information onto the multitude of internet connected devices has become a challenge for even the most nimble of companies. Everyone is vying for the attention and eyes of the consumer. It is a new world and consumer expectations have changed when it comes to the way content/data/inventory is distributed, discovered and consumed. This change in distribution, in part, is due to the adoption of APIs (Application Programing Interfaces). Businesses who have leveraged APIs have made it more than just a "database of stuff", but rather, have created a platform by which they are now basing their business strategy. Speakers from Mashery, Best Buy, eBay/PayPal and Netflix joined to explore the "Evolution of Distribution" and examined the notion of "why every brand needs an API".
Introduction to the Globus Platform for DevelopersGlobus
We will provide a brief introduction to the Globus platform-as-a-service for developers, with emphasis on understanding the security model; and will demonstrate how to access Globus services via APIs for integration into custom research applications.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
2. THE PAYPAL CONTEXT
PayPal …
– 137 million active accounts
– 193 markets in 26 currencies
–
2012: Total Payment Volume was $145 billion
–
–
–
–
–
–
Q3 2013
Total Payment Volume of $44 Billion
At $5580 TPV / second
Growing 25% YoY
729 million transactions
8 million payments every day
In a dynamic environment
– 300+ features per quarter
– We roll 100,000+ lines of code every two weeks
3. PAYPAL PLATFORM EVOLVED
TO SUPPORT INTEGRATION NEEDS
2001 Instant Payment Notification
2004 Transaction, Mass Pay API
2005 Direct Payment API, Express Checkout
PayPal API
2007 Payment APIs (NVP)
2009 Adaptive APIs (SOAP/XML, NV, JSON)
PayPal Capabilities
2013 Payment APIs (REST)
4. REALITY WAS…
Async APIs
Client Apps
Client APIs
Mobile Apps
Backend
Web APIs
PayPal
Platform
Other
Platforms
SOAP
APIs
Web Apps
Batch
APIs
Shopping
Carts
Hosted
Solutions
7. REDEFINED DEVELOPER PLATFORM
Reestablish credibility with the external developer community by building
simple & consistent APIs with easy discovery and integration
that extend our reach into the richer industry ecosystem
Multiple developer portals
https://developer.paypal.com
Overlapping, inconsistent APIs
Clear, consistent APIs
Learn from large documents
Learn from simple HTML, Tools
Complex sign-up
Simple as-needed sign-up
Incomplete, unreliable Sandbox
Complete, reliable Sandbox
7
8. STARTED FROM BASIC PRINCIPLES …
Who are the end users?
• customer segments, expectations
Who are the developers ?
• developers, merchants, system integrators
How should we design our API ?
• sync, async, batch, errors
How should we ease learning ?
• docs, API explorers, HATEOAS console, …
How should we simplify integration ?
• familiar standards, SDKs, support, …
10. API STANDARDS
API Standards
External & Internal
• Resource model
• REST semantics
• URI format
• Environments
• Versioning
• Namespaces
• Extensibility
• Response codes
• Patterns
• Idempotency
• Web linking
• Filters
• Deletion of resources
• Pagination
• Message formats
• Data model
• Common data types
• Serialization
• Security
• Application identification
• Errors
• Error codes
• Identification of PayPal SDK's calls
based on http://restcookbook.com/
11. REPRESENTATION & PATTERNS
• Using the JSON data model
• JSON serialization right now
• Specifying common, standard, I18Nready data types
{
"intent": ”sale",
"payer":{
"payment_method":"urn:payment_method:credit_card",
"first_name":"",
"last_name":"",
"funding_instrument":{
"credit_card":{
"number":1234123412341234,
"type":"",
"exp_month":12,
"exp_year":2015,
"cvv2":123
}
}
},
”transactions":[
{
"amount":{
"total":1.0,
"currency":"USD"
},
"payee":{
"id":""
}
}
]
}
• Relying on standard patterns as
much as possible
• Specifying standard patterns to
complement those:
• Transaction processing and
avoiding duplication
• Selection of subset for item lists
• Error message format
• (DRY) Don’t repeat yourself in your
implementation, but don’t worry
about repeating yourself in your API
design.
13. THE API DESIGN PROCESS
Use-case
analysis
Feedback
API
Specification
Capability
Mapping
Resource
Modeling
REMARKABLE SIMILARITIES WITH
USER EXPERIENCE DESIGN PROCESS
14. USE CASE ANALYSIS
• Actors, roles, relationships, scenarios
• System boundaries
• Functional and non-functional
requirements
• Error conditions and Contingencies
• Coarse grained or Fine grained
• Expected behaviors
15. RESOURCE MODELING
• Split business into functionality
• Modeling to identify:
• Entities
Resource
• Actions on those:
HTTP methods and controller resources
• Relationships and transitions
• Events (web hooks)
Examples:
https://api.paypal.com/v1/payments/payment/{id}
https://api.paypal.com/v1/payments/authorization/{id}
…
17. AUTHENTICATION & AUTHORIZATION
• OAuth 2.0
• User Approval/Consent
• Token Granting
•
•
Public Clients
Confidential Clients
• OAuth scopes to represent ability for an
application to:
• Use certain functionality
• Access and operate on a resource
•
E.g, capture funds authorized previously, read
financial instrument from wallet,…
• OAuth != Security
• Always use SSL
• Data at rest is always encrypted!
18. API SPECIFICATION
• Human & machine
readable format
• Several options:
• Google Discovery
Document
• Swagger
• IODocs
• WADL
• API Blueprint
• RAML
• JSON Schema
• GenIO:
https://github.com/paypal/
genio
19. FEEDBACK
• Mechanisms
• Hackathons with internal and
external developers
• Developer council
• Measure
• TTFHW
• Integration effort
• Errors
22. SUMMARY
• APIs are an important way for a company, like PayPal, to extend reach
• Our APIs gathered entropy, which we addressed through good patterns
• Basic principles to deliver a great developer experience
• end users, developers, API design, learning, integration
• Successful APIs come from
• Familiar API standards
• Good API design process
• Simple and complete developer experience
• While transformation of PayPal’s external platform is underway
• The internal platform is going through a similar transformation
• Goal is about business agility
• Internal developer concerns are not that different