httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
Comparison · DevOps
Appwrite vs promises
A side-by-side editorial comparison of Appwrite and promises — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:performance
Appwrite vs promises: at a glance
| Feature | Appwrite | promises |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 10.0 | 0.0 |
| Sparks · 30d | 3 | 0 |
| Top themes | performance, cold-starts, developer-tooling, mcp | async, observability, performance, shiny |
| Last editorial update | 3h ago | 47m ago |
| Website | — | Visit → |
What is Appwrite?
Appwrite is spending this quarter on latency: the CLI, cold starts, and now builds.
Appwrite Cloud is being tuned end to end for speed. The CLI was rewritten from Node to a single Go binary, function cold starts now mount a compressed SquashFS artifact instead of extracting files, and builds cache the package manager's store between runs. Alongside that, the MCP thread went both ways in a fortnight: Appwrite's own MCP server moved to a hosted remote endpoint, and a Functions template turned the platform into somewhere to host your own. Cloud economics are tightening in the background, with build and deployment storage billed from September 1 and scheduled executions jittered on Free and Education plans.
What is promises?
promises drops R6 for plain environments and wires async work into OpenTelemetry
promises supplies the async primitives behind Shiny and plumber. After years of small domain and future() fixes, the last two releases changed both what a promise costs and what it can report: 1.4.0 corrected nested domain ordering and added the first OpenTelemetry integration, and 1.5.0 replaced the R6 promise class with a classed environment while stabilizing the tracing API.
Appwrite vs promises: editorial side-by-side
Appwrite
10.0DEVOPS
Appwrite is spending this quarter on latency: the CLI, cold starts, and now builds.
◆ Current state
Appwrite Cloud is being tuned end to end for speed. The CLI was rewritten from Node to a single Go binary, function cold starts now mount a compressed SquashFS artifact instead of extracting files, and builds cache the package manager's store between runs. Alongside that, the MCP thread went both ways in a fortnight: Appwrite's own MCP server moved to a hosted remote endpoint, and a Functions template turned the platform into somewhere to host your own. Cloud economics are tightening in the background, with build and deployment storage billed from September 1 and scheduled executions jittered on Free and Education plans.
◆ Where it's heading
Every performance entry in this window targets the same path: the loop between a code change and a running deployment. Install time, extraction time, process start time — each is being removed in turn, with real before-and-after numbers rather than claims. That path matters most when something invokes it repeatedly, which is where the CLI rewrite and the MCP work point: CI pipelines and coding agents driving a project through its own tooling. The pricing changes run on a parallel track, drawing the line between what is free and what is guaranteed.
◆ Prediction
The cold-start work is currently limited to new deployments and favours larger artifacts, so extending it — or automating the redeploy it requires — is the obvious follow-up. The September 1 storage enforcement is dated and will land; expect deployment retention controls to get more attention as it approaches.
promises
0.0DEVOPS
promises drops R6 for plain environments and wires async work into OpenTelemetry
◆ Current state
promises supplies the async primitives behind Shiny and plumber. After years of small domain and future() fixes, the last two releases changed both what a promise costs and what it can report: 1.4.0 corrected nested domain ordering and added the first OpenTelemetry integration, and 1.5.0 replaced the R6 promise class with a classed environment while stabilizing the tracing API.
◆ Where it's heading
Two things are being fixed at once. Promise domains - the mechanism that carries context across async boundaries - have been the source of nearly every bug in this window, and they are now being used deliberately as the vehicle for tracing rather than just for error handling. Meanwhile the object itself is being made cheap enough to create in volume.
◆ Prediction
Expect the OpenTelemetry surface to lose its experimental label and pick up the same span coverage Shiny would need end to end; the deprecated ospan function names should be removed in a following release.
Alternatives to Appwrite and promises
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Appwrite or promises.
withr
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
htmltools
htmltools spends three releases walking back its own fill-layout opinions
xml2
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
httr
httr's last releases are housekeeping - the package now points users at httr2
magrittr
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
See all Appwrite alternatives → · See all promises alternatives →
Recent activity from Appwrite and promises
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15h agoAppwriteUp to 4x faster dependency installs with the build cache
- 1d agoAppwriteFaster cold starts for Appwrite Sites and Functions with SquashFS
- 2d agoAppwriteThe Appwrite CLI is now written in Go ⚡
- 6d agoAppwriteScheduled executions shift slightly on Free and Education plans
- 7d agoAppwriteDeploy your own MCP server with the new Functions template ⚡
- 10d agoAppwritePricing update: storage costs for builds and deployments will be enforced ⚡
- 9mo agopromisesOpenTelemetry spans across async work; R6 dropped for environments ⚡
- 9mo agopromisesNested promise domains fixed; then() gains a tee argument
- 1y agopromisesRealigns future object creation with the future package
- 1y agopromisesFixes stack overflow on long promise chains
- 1y agopromisesFixes domains forgotten inside nested handlers
- 3y agopromisesfuture_promise() returns early when workers are exhausted
Frequently asked questions
What is the difference between Appwrite and promises?
Both compete on the same themes — performance — within DevOps. Appwrite is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Appwrite better than promises?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Appwrite is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to Appwrite?
Top Appwrite alternatives in DevOps are ranked by recent ship velocity. Browse the "Appwrite alternatives" section above for the current picks, or visit /alternatives/appwrite for the full list with editorial commentary on each.
What are the best alternatives to promises?
Top promises alternatives in DevOps are ranked by recent ship velocity. Browse the "promises alternatives" section above for the current picks, or visit /alternatives/promises for the full list with editorial commentary on each.