Repository navigation

Define substrate HA story #181

Closed

Assignees

Labels

area/api-machinerykind/featureprio/P0

Milestone

Julian Gutierrez Oschmann (juli4n)

opened

This includes how we will run ate-apiserver in HA mode. This includes not just the grpc server but also whatever database we decide to use. How will ate-apiserver scale horizontally? Do we care about vertical scaling? How do we scale the underlying database? Are all replicas active? Is there any sharding mechanism? Any leader election? etc...

Zheng Lammerts (zlammerts-svg)
added
prio/P0Highest priority / required for next milestone

area/api-machinery
on Jun 4, 2026
Dmitry Berkovich (dberkov)
added this to the Alpha (technical viability) milestone on Jun 10, 2026
Zheng Lammerts (zlammerts-svg)
assigned
Julian Gutierrez Oschmann (juli4n)
on Jun 15, 2026
Zheng Lammerts (zlammerts-svg)
added this to Substrate Milestones (go/substrate-milestones)on Jul 9, 2026
github-project-automation
moved this to Todo in Substrate Milestones (go/substrate-milestones)on Jul 9, 2026
Zheng Lammerts (zlammerts-svg)
modified the milestones: M1 (technical viability), M2 on Jul 23, 2026
Benjamin Elder (BenTheElder)
added a commit that references this issue on Jul 24, 2026
Instrument ate-apiserver so that it can shutdown gracefully. (#523)
04aee6c
Aditya Shantanu (aditya-shantanu)
added
kind/featureAn enhancement / feature request or implementation
on Aug 13, 2026
Julian Gutierrez Oschmann (juli4n)
closed this as completed on Oct 6, 2026

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Julian Gutierrez Oschmann (juli4n)

Labels

area/api-machinerykind/featureprio/P0

Type

No type

Projects

Substrate Milestones (go/substrate-milestones)
Status
Done

Milestone

M2

Relationships

None yet

Development

No branches or pull requests