Wednesday, October 28, 2020
An application programming interface (API)-centric design approach is becoming increasingly popular across industries. Enterprises are unlocking standalone applications and exposing legacy services to share data across different lines of business (LOBs) by using an API management platform (AMP), built with security in mind. AMP allows providers to efficiently release legacy data and share with consumers internally and externally. API providers can rest assured given this API management platform has been built for enterprise security and API governance.
In this webinar, I will discuss and demonstrate the following topics to illustrate how enterprises can use AMP to share the legacy and new services while controlling and monitoring a portfolio of APIs.
Benefit/Value of APIs
Discuss API life-cycle management
Discuss API-first design approach
Design API using API designer
Build and deploy your APIs
Control your APIs via usage policies
Operation your APIs via monitoring, analytics, reporting, and billing
Engage with developers through Developer Portal and interactive API documentation
Make your APIs available via API discovery
PRO SESSION (API): What Do You Prefer Client Libraries or Rest API's in Implementing Azure AI Solutions?
In this session we will discuss how to Use Face Client Library ( Azure cognitive Services) with .Net core Application with real time Examples. Use face client library is the recently released cognitive Service, so I felt to share my knowledge in this to my community. At the end, let's implement AI solutions using Client Libraries than REST API's.
As popular web services extend their developer platforms for partners to integrate directly into their interfaces, design trends are forming from experiences in the world of embedded integrations. With Google Drive connecting tools like Balsamiq and ShiftEdit, Gmail enabling Docusign in their web and mobile UI, and Trello’s PowerUps, custom experiences powered by third parties are proving themselves to be a great way to improve one’s product and grow your business.
After analyzing over 10 years of experiments in this space, seeing past failures and current successes, we can identify what works from successful and unsuccessful platforms, what trends are working, and what UX and technical considerations are needed to launch your own successful embedded integration plan.
Good documentation sells APIs. Content is king and it will make your API site successful. In this presentation, I describe how to design and create richly meaningful API documentation.
In recent surveys, developers rated the types of information they want. On a scale of 1-4, a majority rated complete and accurate documentation at 3.5+. In another survey, developers rated overviews and conceptual information as important as API references and code samples.
Using the design and writing principles I provide, you will be able to architect information that API developers say they want. I review the evolution of various types of API documentation sites that our team created over the last decade.
Based on our lessons learned, I provide simple tips and an API site template that small teams can use to develop meaningful documentation.
In this technical workshop we'll integrate expert.ai NL API with a main enterprise search engine. The audience will be able to:
- understand the richness and quality of the metadata extracted by the API from text in 5 languages
- see how easy and fast the integration can be with one of the most advanced enterprise search platform in the market
- how the richness and the depth of the data returned by the API can significantly enhance the user experience by providing a more accurate information retrieval and by enabling, through a much richer and granular set of metadata, new ways to access the information.
Everyday thousands of people are bullied, blackmailed, silenced and scammed online using fake photos, fake videos and misinformation. It is getting easier to (i) selectively edit photos, videos and audio, (ii) manipulate metadata of media content and (iii) even generate fully artificial videos (Eg: deepfakes). Fakes are used to spread misinformation and create socio-economic and political chaos. This is leading us towards a post-truth dystopia. Also, sometimes malicious people falsely accuse genuine videos (or photos, audio) as fakes, to promote their self-interests.
In this talk, I will present an implementation of a Blockchain-powered 'truth machine' (a mobile app) to enable a global borderless decentralized citizen photo journalism. Our technology incentivizes the spread of truth and controls misinformation before it spreads. Our app lets anyone create, share, buy, sell and trade cryptographically-signed verifiable photos and videos. The users may choose to be anonymous, pseudonymous or use their real identities.
Our Blockchain securely tracks the provenance of the photos and provides a verifiable certificate to prove that they are not fake or photoshopped or deepfaked. The digital rights of the photos are tracked using our blockchain and transferred seamlessly and securely using smart contracts, thus enabling a full-stack photo journalism platform.
Conversational intelligence technology is changing the way knowledge workers operate. In this session, we’ll walk through the rapidly evolving technology frameworks available for adding intelligence to your own B2B products, typical use cases, and experiences - be that on-demand virtual assistants to always-on intelligence; as well as real-time and post conversation summaries.
Symbl is building a new category of Voice Tech Infrastructure that enables existing platforms to add market-leading functionality to your product quickly. You will leave with a clear understanding of the value proposition, the APIs that solve the challenges, and the capabilities that will transform conversational data into business advantage for your customers. We’ll walk through the code live as we cover the intelligence layer so you can see it in action.
Accessing and working with data is not easy with serverless, because traditional methods of database access don't work well. In this talk, I will discuss the key problems around working with databases when building serverless application logic and approaches to solving them. I will motivate problems like connection pooling, cold-starts, handling spiky concurrent loads, database transactions and transient failures. I will then present GraphQL as a possible solution for building a high-performance data API that can scale to serverless workloads. I will talk about the pros & cons of this approach. Finally, I will do some live code demos and make the problems and solutions discussed previously more concrete!
Thursday, October 29, 2020
There is no easy way to connect to vehicles without hardware. It is difficult because of how the mobility landscape is structured. Innovation is getting faster and at Smartcar we are opening the gates with our APIs for developers building mobility applications and companies. During this session, we will show how we can now and forever connect to cars with a live demo of Smartcar’s API.
PRO SESSION (API): Enhanced Platform Protection for API Gateways Through Cognitively Assorted ML Algorithms
Most API gateways, as the first line of defense and policy enforcement point, are responsible for a variety of tasks including security validations, run-time governance and contract enforcements. Besides authentication, authorization and token validations, they must be able to protect enterprise systems from a multitude of security threats like DDoS/XDoS, Code Injection, protocol threats, XML injections and others. Most gateways use static policies that are applied on the inbound API messages to detect these threats. Gateways also use static policies to enforce any user contracts and SLA.
All these static policy-based methods need to be updated periodically to reflect the ever-changing threat vectors. This becomes a hard and cumbersome management activity and always tend to be reactive. Although the existing gateways collect a huge amount of transaction metrics, they surprisingly lack robust analytics to dynamically analyze API consumption behavior and patterns. They also act as a mere pass-through layer in most situations and don’t provide much assistance with managing the behavior of the back-end applications. This is where Artificial Intelligence and Machine Learning can play a crucial role to provide deep insight into how APIs are used, detect anomalies and thereby help prevent bad incidents before they happen. It can produce comprehensive information for cybersecurity, helping with compliance, governance reports and forensics, to uniquely enhance protection of platforms within IT ecosystems. It can augment the capability gaps in the existing API gateways and provide more important analytics on API consumer behavioral patterns and detect anomalies both from consumption as well as API execution perspective.
The entire paper to be submitted later will detail a multitude of supervised and unsupervised learning algorithms that can be used and trained with the metrics already being collected from the API gateway and logging frameworks. Some of the metrics used by the machine learning models include API usage rate patterns, error patterns, payload patterns etc. These machine learning models can then provide a variety of classification operations for rate limiting decisions and SLA enforcements. They can also detect and predict API consumption anomalies like DDoS and other security threats, back-end application behavior anomalies, predictive analysis on performance of backend applications etc. These models can then work in conjunction with robotic process automation systems to take actions on some of these anomalies detected or predicted to perform self-healing before errors occur.
According to Security Boulevard, the industry definition of open banking is the practice of sharing financial data with competitors and third parties via open APIs. But in reality, open banking should go beyond this and be an innovative and secure platform for delivering consumers and businesses a better financial data experience.
By putting consumers in control of their financial data, open banking transforms the way the world experiences money — everything from budgeting, payments, investing and lending, while improving financial literacy and expanding financial inclusion. This ultimately leads to better financial outcomes.
To provide increased insight into how open banking will accelerate innovation in the fintech market, Finicity co-founder Nick Thomas will delve into the core industry principles of financial data and the importance of each of these attributes in product design: control, access, transparency, traceability and security. He will also cover the latest information on regulations around financial data, identity and consumer protections, as well as the latest and greatest within the standards group of the Financial Data Exchange and the Trust over IP Foundation.
As we build more and more APIs, we're bound to run into more and more API changes. And as each API changes, all the client applications need to adapt, too. Even when your client app consumes only one API changes can be a challenge. But when your client app consumes dozens of APIs the rate and impact of change can be daunting.
For the last 20+ years there has been one client app that consistently exhibits the ability to adapt to change and the resilience to keep running even when some things are broken -- that's the HTML browser client. API developers don't need another HTML browser. Instead we need a new API browser. One that exhibits the positive features of the web and steers clear of the problematic features of bespoke API servers. What we need is more Hypermedia APIs
Through a series of working examples, this talk illustrates the advantages of well-crafted hypermedia APIs using standardized hypermedia formats and formalized domain vocabularies to power autonomous and resilient client applications.
Whether you are an API designer, architect, or developer, this talk can help you get autonomy and resilience for free with Hypermedia APis.
Imagine an application that has a web and a mobile, IOS and Android, or that your API is consumed by similar frontends from totally different teams. The functionalities they provide are distinct, hence the need for distinct sets of data and functions. You might think that the solution for this is having an “as generic as possible” backend for all UI’s. From my experience, this kind of backend leads to big issues in matters of performance, entangled user experience as well as extra and unnecessary communication for the development teams in order to align and meet their needs. Fortunately, there is a promising set of approaches taking the stage as they are created with the intention to optimize how front-end applications collaborate with back-ends: BFF (Backend-For-Frontend) pattern and GraphQL. Given these two approaches, which one is the right to consider? Join me in a talk where we will discuss the two approaches, underline both their good and bad sides, and determine which you should consider as the backend technology for your frontend application.
Embedded SIM (eSIM) is expected to connect 2.5 billion smartphones by 2025. eSIM and programmable cellular data API's are offering online businesses new ways to better activate and engage with their customers. After an introduction to eSIM and how it is digitizing access to cellular networks, few use cases will be presented to illustrate how programmable cellular data can help businesses expand online.
As digital resources -- compute, storage, bandwidth, etc. -- increasingly become tokenized and trade-able on tomorrow’s blockchain networks, managing these tokenized resources will become vitally important. This talk outlines this future, characterized by greater composability of applications and the financialization of digital resources.