@@ -586,8 +586,8 @@ ul.references li p a.back-anchor {
Sergey Konstantinov. The API.
yatwirl@gmail.com · linkedin.com/in/twirl · patreon.com/yatwirl
API-first development is one of the hottest technical topics nowadays since many companies started to realize that API serves as a multiplicator to their opportunities—but it also amplifies the design mistakes as well.
-This book is written to share the expertise and describe the best practices in designing and developing APIs. It comprises six sections dedicated to:
+API-first development is one of the hottest technical topics nowadays since many companies have started to realize that APIs serves as a multiplier to their opportunities — but it amplifies the design mistakes as well.
+This book is written to share expertise and describe best practices in designing and developing APIs. It comprises six sections dedicated to the following topics:
- The API design
- API patterns
- Backward compatibility @@ -598,7 +598,7 @@ ul.references li p a.back-anchor {
This book is distributed under the Creative Commons Attribution-NonCommercial 4.0 International licence.
Source code available at github.com/twirl/The-API-Book
-API-first development is one of the hottest technical topics nowadays since many companies started to realize that API serves as a multiplicator to their opportunities—but it also amplifies the design mistakes as well.
-This book is written to share the expertise and describe the best practices in designing and developing APIs. It comprises six sections dedicated to:
+API-first development is one of the hottest technical topics nowadays since many companies have started to realize that APIs serves as a multiplier to their opportunities — but it amplifies the design mistakes as well.
+This book is written to share expertise and describe best practices in designing and developing APIs. It comprises six sections dedicated to the following topics:
- — The API design
- — API patterns
- — Backward compatibility @@ -79,7 +79,7 @@
[Work in Progress] Section II. The API Patterns
+Section II. The API Patterns
- Chapter 15. On Design Patterns in the API Context
- Chapter 16. Authenticating Partners and Authorizing API Calls @@ -159,9 +159,9 @@
Sergey Konstantinov has been working with APIs for more than a decade. He started his career as a software engineer in the Maps API division at Yandex and eventually became the head of the service, being responsible for both technical architecture and product management.
-During this tenure, Sergey got a unique experience in building world-class APIs with a daily audience of tens of millions, planning roadmaps for such a service, and giving numerous public speeches. He also worked for a year and a half as a member of the W3C Technical Architecture Group.
-After nine years in Maps, Sergey switched to technical-lead roles in other departments and companies, leading integration efforts and being responsible for the technical architecture of entire business units. Today, Sergey lives in Tallinn, Estonia, and works as a staff software engineer at Bolt.
Sergey Konstantinov has been working with APIs for over a decade. He began his career as a software engineer in the Maps API division at Yandex and eventually became the head of the service. In this role, he was responsible for both technical architecture and product management.
+During this tenure, Sergey gained unique experience in building world-class APIs with a daily audience of tens of millions, planning roadmaps for such a service, and delivering numerous public speeches. Additionaly, he served as a member of the W3C Technical Architecture Group for a year and a half.
+After being nine years in Maps, Sergey transitioned to technical lead roles in other departments and companies. In these positions, he led integration efforts and was responsible for the technical architecture of entire business units. Currently, Sergey resides in Tallinn, Estonia, and works as a staff software engineer at Bolt.
Книгу «API» можно читать по-русски.