Erik Wilde – författare

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 underplanning can lead to disaster. This practical guide provides maturity models for individual APIs and multi-API landscapes to help you invest the right human and company resources for the right maturity level at the right time.How do you balance the desire for agility and speed with the need for robust and scalable operations? Four experts from the API Academy show software architects, program directors, and product owners how to maximize the value of their APIs by managing them as products through a continuous life cycle.Learn which API decisions you need to govern and how and where to do soDesign, deploy, and manage APIs using an API-as-a-product (AaaP) approachExamine ten pillars that form the foundation of API product workLearn how the continuous improvement model governs changes throughout an API's lifetimeExplore the five stages of a complete API product life cycleDelve into team roles needed to design, build, and maintain your APIsLearn how to manage your API landscape - the set of APIs published by your organization

This volume provides an overview and an understanding of REST (Representational State Transfer). Discussing the constraints of REST the book focuses on REST as a type of web architectural style. The focus is on applying REST beyond Web applications (i.e., in enterprise environments), and in reusing established and well-understood design patterns when doing so. The reader will be able to understand how RESTful systems can be designed and deployed, and what the results are in terms of benefits and challenges encountered in the process.Since REST is relatively new as an approach for designing Web Services, the more advanced part of the book collects a number of challenges to some of the assumptions and constraints of REST, and looks at current research work on how REST can be extended and applied to scenarios that often are considered not to be a good match for REST.This work will help readers to reach a deeper understanding of REST on a practical as well as on an advanced level.

This book serves as a starting point for people looking for a deeper principled understanding of REST, its applications, its limitations, and current research work in the area and as an architectural style.

This volume provides an overview and an understanding of REST (Representational State Transfer). Discussing the constraints of REST the book focuses on REST as a type of web architectural style. The focus is on applying REST beyond Web applications (i.e., in enterprise environments), and in reusing established and well-understood design patterns when doing so. The reader will be able to understand how RESTful systems can be designed and deployed, and what the results are in terms of benefits and challenges encountered in the process.Since REST is relatively new as an approach for designing Web Services, the more advanced part of the book collects a number of challenges to some of the assumptions and constraints of REST, and looks at current research work on how REST can be extended and applied to scenarios that often are considered not to be a good match for REST.This work will help readers to reach a deeper understanding of REST on a practical as well as on an advanced level.

This book serves as a starting point for people looking for a deeper principled understanding of REST, its applications, its limitations, and current research work in the area and as an architectural style. The authors focus on applying REST beyond Web applications (i.e., in enterprise environments), and in reusing established and well-understood design patterns. The book examines how RESTful systems can be designed and deployed, and what the results are in terms of benefits and challenges encountered in the process. This book is intended for information and service architects and designers who are interested in learning about REST, how it is applied, and how it is being advanced.

Das World Wide Web ist zweifelsohne eine der wichtigsten Entwicklungen des vergangenen Jahrzehnts. Seit den Anfängen 1990 hat es sich von einem zunächst sehr einfachen Modell von Ressource-Namen (URL), einem Übertragungsprotokoll (HTTP) und einer Sprache für die Beschreibung miteinander verbundener Dokumente (HTML) zu einer weit komplexeren Infrastruktur entwickelt.Dieses Buch gibt eine umfassende technische Beschreibung aller relevanten WWW Entwicklungen von den Anfängen bis heute, einschließlich der neuesten Versionen des Hypertext-Transfer-Protokolls (HTTP/1.1) und der Beschreibungssprache (HTML 4.0), der Grundlagen der Beschreibungssprache (SGML und die aufstrebende Variante XML), der Style Sheets (CSS1 und CSS2), der Server-Technik (SSL, CGI und Apache als Beispiel eines Web Servers) sowie einiger Entwicklungen, die in Zukunft an Bedeutung gewinnen werden (MathML, PNG, XPointer, XLink).

What is the difference between a URL and a URI? How does HTTP fulfill its task? Why do we need XML? What is it, and will it eventually replace HTML? This book gives answers to these questions and a chore of others that may be asked by attentive inhabitants of cyberspace. The book is, of course, not just a glossary of abbreviations and frequently used terms. It is rather a comprehensive and still succinct presentation of the technology used in the World Wide Web. It is surprising to note that, even though hundreds of books have been published that discuss the Web, there have been none, so far, to thoroughly explain the inner workings of this popular Internet application, which is so simple to use and yet so complex when it comes to really understand what is going on inside. The target audience of this book is perhaps best described by how it was first used by the author himself: A draft version was chosen as the supporting text for a class of practitioners, who attended a continuing education course on WWW technology. These were people who knew what the Web is, and how it may be used for business, but needed to know how the technology works. During the planning for this course, the author found that no suitable book was on the market, and decided to write one himself.