Every StaxInvesting article tagged self-hosted · 5 posts.
5 articles
The tastytrade order format is simple enough to get subtly wrong in ways that never throw an error. Per-unit pricing, the debit and credit sign convention, accepted versus filled, and what to do when a submission times out and you do not know whether it landed.
There is no published tastytrade requests-per-minute limit, which makes most advice on this topic invented. What is documented is more dangerous: an IP block for repeated failed logins, typically eight hours, delivered as a timeout rather than an error code. Here is how automated clients trigger it and how to build so they do not.
Session-token authentication is gone, but most tastytrade integration guides still teach it. Here is the current OAuth2 model, why the fifteen-minute session token is the easy part, how to avoid a refresh stampede under concurrency, and the specific failure modes that show up in production.
Most explanations of trading software are either marketing abstraction or engineering documentation. This is the middle: what actually runs where, which of the three parties can do what, what an API key really is, how the software updates itself without you redeploying, and — the part nobody writes — exactly what happens when your instance dies, your broker goes down, or you revoke access.
Self-hosted trading clients create a deployment problem: how do you ship interface changes without making every user redeploy and interrupting live automation? Module Federation 2.0 with a Vue micro-frontend is the answer — the shell stays put while remotes update from the CDN. Here's how it works, and the shell-to-remote contract problems that make it hard.
