Epic Mikey

  • Hazelcast Write-Behind MapStore: Durable Event Sourcing

    Hazelcast’s write-behind MapStore persists events to PostgreSQL off the hot path: sub-ms IMap writes, LRU eviction, zero service code changes.

  • Claude Code Memory: Context, CLAUDE.md, and When to Clear

    A four-tier memory model for Claude Code: what belongs in the conversation, CLAUDE.md, and persistent memory—and when clearing context helps, not hurts.

  • Saga Orchestration vs Choreography on Hazelcast

    Two saga patterns in one framework: choreography chains async events; orchestration drives synchronous HTTP steps. When to pick each — and how to run both.

  • Claude Code Custom Skills & fastlane for iOS Releases

    The five custom Claude Code skills and fastlane lane behind a shipping iOS app — why the boring, repeatable workflows are the real leverage.

  • Dead Letter Queue + Idempotency: Exactly-Once on Hazelcast

    A dead letter queue captures events that fail permanently; an idempotency guard blocks duplicates — exactly-once processing on Hazelcast.

  • Claude Code for iOS: Shipping a Real App in 18 Days

    First commit to a usable App Store release in 18 days: building an iOS app with Claude Code, SwiftUI, and SwiftData — with an honest credit split.

  • Hazelcast Transactional Outbox: Guaranteed Delivery

    Fire-and-forget publishing loses events when the shared cluster is down. The transactional outbox writes to a durable local IMap and retries until delivered.

  • Circuit Breakers and Retry: Resilient Hazelcast Sagas

    One slow service shouldn’t sink the whole saga. Circuit breakers and Resilience4j retry isolate failures and stop cascades in Hazelcast sagas.

  • MCP Server for Microservices: AI-Powered Debugging

    Build an MCP server that lets an AI assistant operate your event-sourced microservices — ten tools, a thin REST proxy, and debugging in one sentence.

  • On the Vector Store I Didn’t Ask For

    I asked Claude for Hazelcast’s VectorCollection and got a from-scratch brute-force vector store instead. It became the Community Edition fallback.