When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / 26 days ago

Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / about 1 month ago

Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / about 2 months ago

We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / 3 months ago

The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 4 months ago

Every commit has a message. Every PR has a title and description. The status update already exists. It's just locked in GitHub. Who this is for: - Founders updating investors - PMs writing release notes - CEOs who want visibility without standups - Anyone who asks "what shipped?" and waits for an engineer to respond What it does: Connect your repos. Ask questions: - "What shipped this month?" - "Who... - Source: Hacker News / 7 months ago

Gitmore (https://gitmore.io) – natural language queries across GitHub, GitLab, and Bitbucket. Instead of filtering PRs, scanning commit logs, or asking engineers for updates: - "What shipped last week?" - "Who's been working on the API?" - "Which PRs have been open longest?" - "Summarize this month's releases" Plain English in, plain English out. How it works: Connect your repos via OAuth. We register... - Source: Hacker News / 7 months ago

If you're a founder who doesn't code, you probably rely on engineers to tell you what's shipping. That works until investors ask for updates, customers want a changelog, or you just need to know where things stand. What it does: Connect your repos. Ask questions: "What shipped last week?" "What's in progress?" "Who worked on what?" Get plain English answers from your commit history. Automated reports: Schedule... - Source: Hacker News / 7 months ago

Gitmore (https://gitmore.io) One feature I built that's been useful: a Slack bot that queries your Git history. Connect your repos. Add the bot to Slack. Ask:. - Source: Hacker News / 7 months ago

- 2FA support GitHub, GitLab, Bitbucket – one dashboard. Free for 1 repo: https://gitmore.io How do you currently handle investor questions about engineering progress? - Source: Hacker News / 7 months ago