Horizon ain't deprecated yet #2146
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
LOL um thank you uWu |
johncanneto
reviewed
Dec 19, 2025
"deprecated", to my engineering-trained mind, means "there is a better alternative available that you should now switch to." There is ***no*** viable alternative to Horizon today. We therefore cannot declare it to be deprecated. When I read that it is _already_ deprecated, it makes me think I can avoid using it in a project. If I cannot realistically avoid using it, at least not without great cost in both engineering research time and infrastructure bills, then the assertion that it is already deprecated will cause me distress. Once we have good Portfolio API-style indexing services in place, with freemium models appropriate for the whole gamut of hackathon-startups-to-enterprises, then we can consider Horizon to be deprecated. Until then, there's just no other reasonable way to get a whole host of necessary data, such as token balances and circulating supply. This updates the "Horizon is deprecated" warning to say that it _will_ be deprecated in the future, deep-linking to the "Portfolio APIs" section of the [newly-revamped indexers page][1]. [1]: stellar#2055
chadoh
force-pushed
the
horizon-not-yet-deprecatable
branch
from
b9ccd21 to
bd894d4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"deprecated", to my engineering-trained mind, means "there is a better alternative available that you should now switch to."
There is no viable alternative to Horizon today. We therefore cannot declare it to be deprecated.
When I read that it is already deprecated, it makes me think I can avoid using it in a project. If I cannot realistically avoid using it, at least not without great cost in both engineering research time and infrastructure bills, then the assertion that it is already deprecated will cause me distress.
Once we have good Portfolio API-style indexing services in place, with freemium models appropriate for the whole gamut of hackathon-startups-to-enterprises, then we can consider Horizon to be deprecated. Until then, there's just no other reasonable way to get a whole host of necessary data, such as token balances and circulating supply.
This updates the "Horizon is deprecated" warning to say that it will be deprecated in the future, deep-linking to the "Portfolio APIs" section of the newly-revamped indexers page.