• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Web APIs - Versioning, Security and Frameworks

 
Ranch Hand
Posts: 75
Mac Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm curious to know if your book gets into the pros and cons around API frameworks such as Apigee and others.  Also, we have a lot of legacy technologies - are there certain ones that you suggest get "retired"
 
Author
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

The Design of Web APIs focus on the design of interface contracts not they are actually implemented, therefore  I do not talk about frameworks. By the way Apigee is not a framework, it is an API gateway solution. The main purposes of an API gateway are vitualization, security and logging and absolutely NOT implementation. Do not listen to API gateways vendors if they tell you that you can put API implementation in their gateways :-).

Arnaud
 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Arnaud Lauret wrote:Hi,

The Design of Web APIs focus on the design of interface contracts not they are actually implemented, therefore  I do not talk about frameworks. By the way Apigee is not a framework, it is an API gateway solution. The main purposes of an API gateway are vitualization, security and logging and absolutely NOT implementation. Do not listen to API gateways vendors if they tell you that you can put API implementation in their gateways :-).

Arnaud



How about API management tools that stores API docs? Don´t you think they are usefull to reuse and spread of good practices of API design?
 
Arnaud Lauret
Author
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Indeed, API Portals providing API documentation are valuable, even for private APIs. Without them nobody is aware that APIs exist. Some API management solutions may provide API portals, they may be OK for private APIs, but when it comes to public ones, there is usually some work to achieve something good. It may be better sometimes to start from scratch. Also when you want to provide API documentation for APIs that do not exist yet, you may have to do some modifications yourself, these out of the box solutions usually do not handle such case.
 
Why is the word "abbreviation" so long? And this ad is so short?
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic