์Šคํ‚ฌ golang-samber-hot
๐Ÿ“ฆ

golang-samber-hot

v1.1.2 ์ฝ˜ํ…์ธ  ๋ฆฌ๋น„์ „ r1 ์•ˆ์ „ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด๐ŸŒ ๋„คํŠธ์›Œํฌ ์ ‘๊ทผ

Build Reliable Go Caches with samber/hot

Repeated backend reads can increase latency and overload services. This skill guides samber/hot cache design with workload-based eviction, expiration, loaders, concurrency controls, and monitoring.

์ง€์›: Codex Code(CC)
Maintain this Skill? Claim it ๐Ÿฅ‰ 78 ๋ธŒ๋ก ์ฆˆ

๋‚ด ์—์ด์ „ํŠธ๋กœ ์„ค์น˜

์ด ์š”์ฒญ์„ ์—์ด์ „ํŠธ์— ๋ณต์‚ฌํ•˜์„ธ์š”. ๊ณต์‹ Skill ํŽ˜์ด์ง€์™€ ๋งค๋‹ˆํŽ˜์ŠคํŠธ๊ฐ€ ํฌํ•จ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ ์š”์ฒญ
Review the Skillstore skill "golang-samber-hot" from https://skillstore.io/skills/samber-golang-samber-hot.md and its manifest at https://skillstore.io/api/skills/samber-golang-samber-hot/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

์—์ด์ „ํŠธ๋Š” ๊ณ„์†ํ•ด์„œ ๊ณ„ํš์„ ํ‘œ์‹œํ•˜๊ณ  ๋ณด์•ˆ ์ •์ฑ…์—์„œ ์š”๊ตฌํ•˜๋Š” ํ™•์ธ์„ ์š”์ฒญํ•ด์•ผ ํ•ฉ๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ๊ฐ€ ์ฝ๊ธฐ ์‰ฌ์šด ๋ฆฌ์†Œ์Šค

AI ์—์ด์ „ํŠธ, ํฌ๋กค๋Ÿฌ, ์Šคํฌ๋ฆฝํŠธ๊ฐ€ ์ „์ฒด ํŽ˜์ด์ง€ ๋Œ€์‹  ์ •๋ฆฌ๋œ ์ปจํ…์ŠคํŠธ๋งŒ ํ•„์š”ํ•  ๋•Œ ์ด ๋งํฌ๋ฅผ ์‚ฌ์šฉํ•˜์„ธ์š”.

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"golang-samber-hot" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Which policy fits stable, heavily skewed DNS cache lookups?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • LFU is a candidate because a small, consistently popular key set dominates requests.
  • Changing popularity can leave outdated items favored, so compare alternatives if the workload shifts.
  • Benchmark representative lookups and choose TTL independently from eviction policy.

"golang-samber-hot" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Can I combine disabled locking with background TTL cleanup?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • The skill identifies disabled locking and janitor cleanup as incompatible options that can panic.
  • Keep locking when using background cleanup or concurrent access.
  • For a single-goroutine design, omit the janitor and plan explicit cleanup.

"golang-samber-hot" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. How should I monitor a samber/hot cache?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Enable the library's Prometheus metrics and register the cache as a collector.
  • Track hit ratio, eviction rate, and cache occupancy relative to capacity.
  • Set alert thresholds from workload requirements and investigate changes before increasing memory.

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „

All 43 static findings are false positives involving Markdown formatting, cache terminology, documentation links, or normal development tool declarations. The installation example uses standard Go dependency tooling, not shell substitution. No evidence found of credential theft, exfiltration, destructive behavior, or prompt injection in the reviewed files.

5
์Šค์บ”๋œ ํŒŒ์ผ
945
๋ถ„์„๋œ ์ค„ ์ˆ˜
0
๊ฒ€ํ†  ํ•ญ๋ชฉ
0
์˜คํƒ ๋ฌด์‹œ๋จ
๊ฐ€์žฅ ์ตœ๊ทผ์— ์™„๋ฃŒ๋œ ์ •์ ยท์˜๋ฏธ๋ก ์  ๊ฐ์‚ฌ์—์„œ ํ™•์ธ๋œ ๋ณด์•ˆ ๋ฐœ๊ฒฌ ์‚ฌํ•ญ์ด ๊ฐ์ง€๋˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค. ์ด๋Š” ์Šคํ‚ฌ์— ๋ถ€์ž‘์šฉ์ด ์—†์Œ์„ ์ฆ๋ช…ํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.
๊ฐ์‚ฌ์ž: codex
์ด ๋ณด๊ณ ์„œ ๊ณต์œ  ๋ฐ ์ธ์šฉ

๋ฒ„์ „์ด ์ง€์ •๋œ ํ‰๊ฐ€ ๋ณด๊ณ ์„œ, ์ค‘๋ฆฝ ๋ฐฐ์ง€, ์ž„๋ฒ ๋“œ ์นด๋“œ ๋ฐ ์ธ์šฉ์„ ๊ณต์œ ํ•˜์„ธ์š”. Skillstore๋Š” ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ•˜์ง€๋งŒ ์ด Skill์˜ ์•ˆ์ „ ์—ฌ๋ถ€๋ฅผ ํŒ๋‹จํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.

๋ฒ„์ „๋ณ„ ๋ณด๊ณ ์„œ ์—ด๊ธฐ
๋ณด์•ˆ ํ‰๊ฐ€

๋ณด๊ณ ์„œ ๋งํฌ ๋ณต์‚ฌ

https://skillstore.io/skills/samber-golang-samber-hot/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown ๋ฐฐ์ง€

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-samber-hot/security.svg)](https://skillstore.io/skills/samber-golang-samber-hot?utm_source=security_passport_badge)

HTML ๋ฐฐ์ง€

<a href="https://skillstore.io/skills/samber-golang-samber-hot?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-samber-hot/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

์ž„๋ฒ ๋“œ ์นด๋“œ

<iframe src="https://skillstore.io/embed/skills/samber-golang-samber-hot.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
ํ•™์ˆ  ์ธ์šฉ (APA ยท BibTeX ยท CFF)

APA ์ธ์šฉ

samber. (2026). golang-samber-hot security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-samber-hot/audits/1

BibTeX ์ธ์šฉ

@techreport{samber-samber-golang-samber-hot-2026, author = {samber}, title = {golang-samber-hot security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/samber-golang-samber-hot/audits/1}, note = {Author version 1.1.2} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "golang-samber-hot security audit report (audit version 1)" version: "1.1.2" type: report authors: - name: "samber" date-released: "2026-10-18" url: "https://skillstore.io/skills/samber-golang-samber-hot/audits/1" identifiers: - type: other value: "skillstore:samber-golang-samber-hot:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore ์ ์ˆ˜

์ด ์ ์ˆ˜์˜ ์ด์œ  ์ฆ๊ฑฐ ์‹ ๋ขฐ๋„: ์ค‘๊ฐ„
45
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
65
์ปค๋ฎค๋‹ˆํ‹ฐ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Reduce Repeated Profile Queries

Design a typed user cache with expiration, batch loaders, error handling, and negative caching for missing profiles.

Investigate Cache Contention

Review measured mutex contention, evaluate sharding, and choose monitoring signals before changing capacity or eviction policy.

Review Cache Integration Safety

Check janitor cleanup, incompatible builder options, stale-data policies, and shared mutable values during code review.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Create a Basic Cache
Using samber/hot, create a string-to-byte-slice cache with 10,000 entries and a five-minute TTL. Include janitor cleanup and handle retrieval errors.
Choose an Eviction Policy
Compare samber/hot eviction policies for [access pattern]. Use [memory budget] and [estimated entry size] to estimate capacity. Explain what measurements would validate the choice.
Protect a Database Loader
Design a samber/hot cache for [entity] with a batch database loader and negative caching. Address concurrent misses, expiration jitter, loader errors, and janitor cleanup.
Review a Production Cache
Review [cache implementation] against [freshness requirements], [concurrency profile], and [memory budget]. Evaluate sharding, revalidation, mutable values, Prometheus metrics, and shutdown. Propose focused validation tests.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Measure access patterns and entry sizes before selecting an eviction policy or capacity.
  • Set expiration deliberately, handle loader errors, and stop janitor goroutines during shutdown.
  • Validate concurrency and mutable-value handling with tests, then monitor hit ratio and eviction behavior.

ํ”ผํ•˜๊ธฐ

  • Disable locking for concurrent workloads or combine disabled locking with a background janitor.
  • Call negative-cache methods before enabling missing-key cache configuration.
  • Ignore loader errors or let callers mutate shared cached objects without suitable copying.

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

What does this skill provide?
It provides samber/hot usage guidance, algorithm comparisons, API references, production patterns, and evaluation scenarios for Go cache work.
Which AI tools are listed as supported?
The marketplace metadata lists Codex and Claude Code. The skill also describes compatibility with similar coding agent environments.
Does this replace Redis or provide persistence?
No. The guidance targets process-local in-memory caching, although loader examples can retrieve data from Redis or a database.
Which eviction algorithm should I start with?
The skill recommends W-TinyLFU for mixed or unknown access patterns. Use measured workload characteristics to evaluate specialized alternatives.
How does it address simultaneous cache misses?
It explains loader-based singleflight deduplication and expiration jitter. You must still implement appropriate backend access and error handling.
Does it automatically install dependencies or configure monitoring?
The files provide installation and monitoring examples. Applying them requires agent actions or developer changes within the project.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

samber

๋ผ์ด์„ ์Šค

MIT

์ž‘์„ฑ์ž ๋ฒ„์ „

v1.1.2

Skillstore ๋ฆฌ๋น„์ „

r1

์ฐธ์กฐ

6093890d49a212c14c65676829e1af5ee07ab3dc

์œ ์ง€๋ณด์ˆ˜ ์ตœ์‹ ์„ฑ

2026. 10. 18.

์‚ฌ์šฉ๋Ÿ‰

0 ๋‹ค์šด๋กœ๋“œ ยท 0 ์กฐํšŒ

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“ evals/

๐Ÿ“„ evals.json

๐Ÿ“ references/

๐Ÿ“„ algorithm-guide.md

๐Ÿ“„ api-reference.md

๐Ÿ“„ production-patterns.md

๐Ÿ“„ SKILL.md