From the Back Cover of the Book
Do you use a single API Call Processing Server? Worse yet, do you have all of your web servers making individual API calls all on their own?
Just a single API transaction takes 9 steps to complete through TCP, and your system is getting bogged down with delays from TCP communications. The internet runs on HTTP, and HTTP runs on TCP.
You may have heard of HTTP 2.0, but that only helps to speed up websites with multiple resources. API calls only use a single resource per call.
You could still use websockets to keep some of the overhead low. However, the TCP/IP stack is just one of many bottlenecks in your infrastructure.
Did you know that you don’t need to collect the response from every API call you make? What if you could always speak to every API in your format of choice? I’ll show you how.
In this book, you’ll learn about how implementing an API Call Processing Server or cloud can dramatically reduce the time to transact with an API, reduce your web server overhead, and make programming with APIs so much easier.