← Back to home
Comparison · Infra & APIs

Skipper vs usmap

A side-by-side editorial comparison of Skipper and usmap — release velocity, themes, recent moves, and the top alternatives to consider.

Skipper vs usmap: at a glance

FeatureSkipperusmap
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesreverse-proxy, kubernetes, memory-footprint, zone-aware-routingcartography, sf, data-packaging, fips
Last editorial update13h ago1h ago
WebsiteVisit →Visit →

What is Skipper?

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

Read the full Skipper trajectory →

What is usmap?

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

Read the full usmap trajectory →

Skipper vs usmap: editorial side-by-side

S
Skipper
INFRA · APIS
5.0

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

◆ Current state

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

◆ Where it's heading

Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.

◆ Prediction

Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.

U
usmap
INFRA · APIS
0.0

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

◆ Current state

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

◆ Where it's heading

The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.

◆ Prediction

Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.

Alternatives to Skipper and usmap

Other Infra & APIs 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 Skipper or usmap.

See all Skipper alternatives → · See all usmap alternatives →

Recent activity from Skipper and usmap

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoSkipperMove OIDC flow protection from Referer to cookies
  2. 1d agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
  3. 1d agoSkipperEskip predicates and filters accept negative numbers
  4. 2d agoSkipperFix token introspection handling
  5. 2d agoSkipperFix grant auth flow
  6. 2d agoSkipperUpdate outdated golang.org/x dependencies
  7. 11mo agousmapPuerto Rico added across every usmap function and map year
  8. 1y agousmapdata_year parameter threaded through the plotting functions
  9. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  10. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  11. 2y agousmapDocumentation links updated
  12. 2y agousmapMap data extracted to a companion usmapdata package

Frequently asked questions

What is the difference between Skipper and usmap?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Skipper better than usmap?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.

What are the best alternatives to usmap?

Top usmap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "usmap alternatives" section above for the current picks, or visit /alternatives/usmap for the full list with editorial commentary on each.