LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
- Term in use for a long time Originally meant application programming interface Some may feel it’s synonymous with “SDK” We all understand it’s a way to handle disconnected or remote calls
If we look at a monolith web app that may be using an api the API is what’s allowing that webapp to talk to the app server
But the A in API should really stand for APPS and and Application… And in this sense it’s evolved from old school rich clients to the web clients we knew in the early two thousands and back to rich clients like what we see on mobile now.
So .. What’s an app… mobile app? A web app... In the J2E days we had all kinds of assemblies with Apps... Web “application” archive, Enterrpise application archive?
One type of app, referring back to the monolithic web app from above, is that first entry point into the internal network. That WebApp is the APP here in this context and is what the browser is consuming….
An app is quite simply something that consumes services
But an APP could be itself consuming a backend
And traditionally these “apps” did more integration things…. DB, Email, FTP... But increasingly we’re seeing these as decidedly API oriented in nature
These are already in use everywhere as SaaS solutions today and they expose APIs for mass consumption
That mass of consumption patterns from the internet is being applied internally now as well.
Mobile developers may use SDK’s generated from API descriptions for their entire backend operations… Quickly becoming a pattern in it’s own right
This is good and can mean massive expansion capabilities in terms of increased functionality…. Patterns involving location services via google in concert with other services are a great example of this
And this is, in general, a microservices style approach
The larger APPs for consumption may themselves be comprised of microservices all handling internal comm via APIs
Now .. Let’s talk about an API first approach to the world we’ve discussed up until now.
Architecture for the API-enterprise
Architecture for the API-first
Geir Sjurseth, Sales Engineering, Apigee
API CITY TOUR 9
Modern server-side app
• Often runs in an app server
• Monolithic presentation and business logic
• Hosted in an environment
(often a virtualized container)
• Increasingly lightweight
API CITY TOUR 29
API mass customization
API “B”API “A” API “C”
API CITY TOUR 30
API tier analytics
A/B & multivariate
API CITY TOUR 31
API tier with analytics
• API adaptations needed for apps
• Enable developers for business
• Security for app-to-API
• App and behavior analytics
• APIs architected for abstraction
• Enable developers for API use
• Security for API-to-backend
• API analytics
App consumption API exposure
App server ServicesApp
API CITY TOUR 32
• “A” is for Apps
• APIs are not SOA++
• How to get to an API-centric architecture