Welcome!

Machine Learning Authors: Pat Romanski, Yeshim Deniz, Liz McMillan, Elizabeth White, Zakia Bouachraoui

Related Topics: Java IoT, Industrial IoT, Microservices Expo, Machine Learning , Agile Computing, Cloud Security

Java IoT: Blog Feed Post

The Goldilocks Question and Your API Analytics

This question is "Who's been using my APIs?"

When I think about API Analytics, I like to think about the "Goldilocks Question". This question is "Who's been using my APIs?". One of the tests of an API Analytics solution is how easy it makes it to answer this question.

In the case of the Axway/Vordel API Server's Analytics solution, you can slice the data two ways. You can:

  1. Look at an API and see what clients are using it.
  2. Look at a client and see what APIs they are using.

Let's look at these two scenarios. I've used a vehicle telematics scenario, where two clients ("SUV" and "Sports Car") are accessing two different APIs ("Vehicle Control API" and "Engine Metrics API").

Report of client usage per API:
The screenshot below shows an API ("Vehicle Control API") during a time period: 3pm to 4pm on January 31 2013. We see the number of request to this API from each client. The client "SUV" has made 173 to the Vehicle Control API. 165 were successes. 8 were failures.

I also clicked on the "PDF" button to create a PDF of this same report. This can also be automatically generated on a regular scheduled basis and emailed.

Report per API Client:
The screenshot below shows how many API requests a particular client ("SportsCar" in this case) makes to each API. In this case, it is between 3pm and 4pm on Jan 31. The client made 194 requests to the "Engine Metrics API" during this time. 192 were successes and 2 were failures.

Again, can also click on the "PDF" button to generate a PDF of this information. Or, you could schedule this PDF to be created (e.g. for the previous 24 hour period) and automatically emailed.

In this using the Axway/Vordel API Analytics, which comes with the API Server, you can answer the "Goldilocks Question" and see exactly how your APIs are being used.

Read the original blog entry...

More Stories By Mark O'Neill

Mark O'Neill is VP Innovation at Axway - API and Identity. Previously he was CTO and co-founder at Vordel, which was acquired by Axway. A regular speaker at industry conferences and a contributor to SOA World Magazine and Cloud Computing Journal, Mark holds a degree in mathematics and psychology from Trinity College Dublin and graduate qualifications in neural network programming from Oxford University.

CloudEXPO Stories
With more than 30 Kubernetes solutions in the marketplace, it's tempting to think Kubernetes and the vendor ecosystem has solved the problem of operationalizing containers at scale or of automatically managing the elasticity of the underlying infrastructure that these solutions need to be truly scalable. Far from it. There are at least six major pain points that companies experience when they try to deploy and run Kubernetes in their complex environments. In this presentation, the speaker will detail these pain points and explain how cloud can address them.
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-centric compute for the most data-intensive applications. Hyperconverged systems already in place can be revitalized with vendor-agnostic, PCIe-deployed, disaggregated approach to composable, maximizing the value of previous investments.
When building large, cloud-based applications that operate at a high scale, it's important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. "Fly two mistakes high" is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee Atchison, Principal Cloud Architect and Advocate at New Relic, discussed how this same philosophy can be applied to highly scaled applications, and can dramatically increase your resilience to failure.
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by sharing information within the building and with outside city infrastructure via real time shared cloud capabilities.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.