© 2018 Mertech Data Systems, Inc. | All rights reserved.
An endpoint is a specific combination of transport, default protocol and port that your application is being served at. An Application Process Pool can have multiple endpoints, although in most standard use cases each Pool will only have one endpoint. An endpoint can be “terminated” locally (available on your server and your network only) or it can be “terminated” on one of the Thriftly Gateway Servers which is how you can publish your API out onto the Internet with no network configuration needed.
A Process Pool is a collection of processes that serves a single Thriftly application. Your applications executable is loaded by Thriftly into an Application Process Pool to serve your API. So a single Process Pool will normally have multiple copies of your applications executable loaded so that multiple simultaneous API calls can be made to your application.
Your applications executable is loaded by Thriftly to serve your API. Each load (or process) allows for more API calls to be made simultaneously. So for instance, in the Basic version of Thriftly only 2 processes can be loaded. This means that only 2 API calls can be made simultaneously. Any more API calls that are made will be queued until one of your 2 processes is freed up.
Max Data Transfer via the Thriftly API Gateway