Increased Analytics at the API Client and SDK Level
API providers are including more analytics services...but are the features more about data generation than they are about analytics?
Join the DZone community and get the full member experience.Join For Free
I am seeing more examples of analytics at the API client and SDK level, providing more access to what is going on at this layer of the API stack. I'm seeing API providers build them into the analytics they provide for API consumers and more analytic services from providers for the web, mobile, and device endpoints. Many companies are selling these features in the name of awareness, but in most cases, I'm guessing it is about adding another point of data generation which can then be monetized (IoT is a gold rush!).
As I do, I wanted to step back from this movement and look at it from many different dimensions, broken down into two distinct buckets:
- More information. There will be more data that can be analyzed.
- More awareness. We will have visibility across integrations.
- Real-time insights. Data can be gathered on a real-time basis.
- More revenue. There will be more revenue opportunities here.
- More personalization. We can personalize the experience for each client.
- Fault tolerance. There are opportunities for building in API fault tolerance.
- More information. If it isn't used, it can become a liability.
- More latency. This layer slows down the primary objective.
- More code complexity. This introduces added complexity for devs.
- More security consideration. We just created a new exploit opportunity.
- More privacy concerns. There are new privacy concerns facing end-users.
- More regulatory concerns. In some industries, it will be under scrutiny.
I can understand why we want to increase the analysis and awareness at this level of the API stack. I'm a big fan of building in resiliency in our clients and SDKs, but I think that we have to weigh the positive and negatives before jumping in. Sometimes I think we are too willing to introduce unnecessary code, data gathering, and potentially opening up security and privacy holes chasing new ways we can make money.
I'm guessing it will come down to each SDK and the API resources that are being put to work. I'll be aggregating the different approaches I am seeing as part of my API SDK research and try to provide a more coherent glimpse at what providers are up to. By doing this, I'm hoping I can better understand some of the motivations behind this increased level of analytics being injected at the client and SDK level.
Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.