| section | sortOrder | label | pageName |
|---|---|---|---|
Developer Guides |
2 |
Selecting Service Providers |
selecting-service-providers |
The Stateless protocol offers developers the unique ability to select and manage blockchain nodes that service their requests. This capability allows for tailoring services to specific needs, ensuring optimal performance and reliability.
Provider buckets refer to a list of chosen blockchain nodes that application
can send requests to. Each bucket can contain multiple providers, the selection
of which can be based on supported blockchains, regions, latency, and other
factors. When an application dispatches a request, it's not broadcasted arbitrarily.
Instead, Stateless routes the request to the nearest provider present in the
bucket. This proximity-based routing ensures minimal latency, enhancing the
speed and responsiveness of the application. Application developers can construct these buckets via the Stateless CLI, using
the following commands:
Viewing and Adding New Providers
To view and add providers to a bucket, use the create bucket command.
stateless-cli buckets create
This command displays an interactive list of providers, allowing a fine-tuned
selection of blockchain nodes. The provider's ID, name, and supported
blockchains will be displayed to help developers make informed decisions when
selecting providers to service their requests.
For additional details about a providers services, you can view all available
offerings:
stateless-cli offerings list
This command will return additional details such as a providers available regions and average latency by chain.
Updating Existing Providers
Developers can view their current active providers in a specific bucket using
the following command
stateless-cli buckets list
To update the list of providers in a bucket, use the bucket update command.
stateless-cli buckets update
Deleting Providers
To remove a provider from the bucket, use the bucket delete command.
stateless-cli buckets delete
For more information about managing providers via the API, please see the API reference