APIs: A Strategy Guide

APIs: A Strategy Guide
Author :
Publisher : "O'Reilly Media, Inc."
Total Pages : 149
Release :
ISBN-13 : 9781449308926
ISBN-10 : 1449308929
Rating : 4/5 (29 Downloads)

Book Synopsis APIs: A Strategy Guide by : Daniel Jacobson

Download or read book APIs: A Strategy Guide written by Daniel Jacobson and published by "O'Reilly Media, Inc.". This book was released on 2012 with total page 149 pages. Available in PDF, EPUB and Kindle. Book excerpt: "Creating channels with application programming interfaces"--Cover.


APIs: A Strategy Guide Related Books

APIs: A Strategy Guide
Language: en
Pages: 149
Authors: Daniel Jacobson
Categories: Computers
Type: BOOK - Published: 2012 - Publisher: "O'Reilly Media, Inc."

DOWNLOAD EBOOK

"Creating channels with application programming interfaces"--Cover.
API Management
Language: en
Pages: 209
Authors: Brajesh De
Categories: Computers
Type: BOOK - Published: 2017-03-17 - Publisher: Apress

DOWNLOAD EBOOK

Maximize the impact of your assets and business services by providing APIs for developers and other users. The journey described in this book starts with identi
Designing Web APIs
Language: en
Pages: 180
Authors: Brenda Jin
Categories: Computers
Type: BOOK - Published: 2018-08-29 - Publisher: "O'Reilly Media, Inc."

DOWNLOAD EBOOK

Using a web API to provide services to application developers is one of the more satisfying endeavors that software engineers undertake. But building a popular
Enterprise API Management
Language: en
Pages: 294
Authors: Luis Weir
Categories: Computers
Type: BOOK - Published: 2019-07-23 - Publisher: Packt Publishing Ltd

DOWNLOAD EBOOK

A strategy and implementation guide for building, deploying, and managing APIs Key FeaturesComprehensive, end-to-end guide to business-driven enterprise APIsDis
Continuous API Management
Language: en
Pages: 287
Authors: Mehdi Medjaoui
Categories: Computers
Type: BOOK - Published: 2018-11-14 - Publisher: O'Reilly Media

DOWNLOAD EBOOK

A lot of work is required to release an API, but the effort doesn’t always pay off. Overplanning before an API matures is a wasted investment, while underplan