2. The February 2015 blogging battle
If it has an http:// in front of the address,
it is a public APIâsorry
2
Kin Lane
3. If it has an http:// in front of the address,
it is a public APIâsorry
3
The nomenclature of "public APIs" vs. "private
APIs" are, in fact, a critical part of the
conversation [...] It's about the target developerKin Lane
David Berlind
ProgrammableWeb
The February 2015 blogging battle
4. If it has an http:// in front of the address,
it is a public APIâsorry
4
"If it has an http:// in front of the
address, it is a public APIâsorry.â,
which is total bullshit
Kin Lane
Kin Lane
David Berlind
ProgrammableWeb
The nomenclature of "public APIs" vs. "private
APIs" are, in fact, a critical part of the
conversation [...] It's about the target developer
The February 2015 blogging battle
5. If it has an http:// in front of the address,
it is a public APIâsorry
5
The nomenclature of "public APIs" vs. "private
APIs" are, in fact, a critical part of the
conversationâ âIt's About The Target Developer
I believe there are two axes which can
be considered: internal vs external,
open vs registration vs dark
Kin Lane
Kin Lane
David Berlind
ProgrammableWeb
Mark OâNeill
Axway
The nomenclature of "public APIs" vs. "private
APIs" are, in fact, a critical part of the
conversation [...] It's about the target developer
The February 2015 blogging battle
"If it has an http:// in front of the
address, it is a public APIâsorry.â,
which is total bullshit
6. If it has an http:// in front of the address,
it is a public APIâsorry
6
The nomenclature of "public APIs" vs. "private
APIs" are, in fact, a critical part of the
conversationâ âIt's About The Target Developer
I believe there are two axes which can
be considered: internal vs external,
open vs registration vs dark
[...] the point of internal or private APIs is that
they are building blocks that can be re-used.
Eventually someone is going to want to reuse
[an internal API] with an external entity
Kin Lane
Kin Lane
David Berlind
ProgrammableWeb
Mark OâNeill
Axway
Steven Willmott
3Scale
The nomenclature of "public APIs" vs. "private
APIs" are, in fact, a critical part of the
conversation [...] It's about the target developer
The February 2015 blogging battle
"If it has an http:// in front of the
address, it is a public APIâsorry.â,
which is total bullshit
9. 9
âthe API provider (that is, the team that produces and maintains the API) has a very
different set of concerns than API consumers (that is, internal and/or external developers,
UI teams and partners [...]â
Daniel Jacobson (Netflix)
10. Private APIs
10
âThere is a common misconception that
an API is something that everyone can
consumeâ
Travis Spencer (Nordic APIs)
âWhile public programs often get more attention,
the vast majority of API traffic is actually generated
through private programs.â
Mark Loewenstein (Mashery)
âInternal use may be the biggest API use
case of all.â
John Musser (ProgrammableWeb)
28. References
â You need a status page, Donn Felker, http://bit.ly/1ObKR4D
â I like to be able to verify a developer is real âŚ, Kin Lane, http://bit.ly/1TOFop7
â In the future there will be no public vs private APIs, Kin Lane, http://bit.ly/1Dt0vXQ
â Long live the private API, David Berlind, http://bit.ly/1KCP9AG
â How seperation of concerns can benefit your APIâŚ, Daniel Jacobson, http://bit.ly/1NCyWvX
â When you are ready for a nuanced discussionâŚ, Kin Lane, http://bit.ly/1NCzkuq
â Categorizing APIs, Mark OâNeill, http://bit.ly/1m5mKxW
â Public vs Private vs Internal APIs, Steven Willmott, http://bit.ly/1INDfDI
â Private APIs vs Open APIs, API Academy, http://bit.ly/1INHXRY
â Public vs Private: which API programâŚ, Loewenstein, http://bit.ly/1Q8XFPf
â Private Partner or PublicâŚ, Mark Boyd, http://bit.ly/1Nch0cn
â The myth of the private API, George Reese, http://oreil.ly/1NzzJCg
â How we built partypedia, J.Michaux & P.Reliquet, http://bit.ly/1XQuu81
28