Secureframe | Remote (Canada) | https://secureframe.com | 150-200k CAD Secureframe helps company get compliant and build trust with their customers. We do this by integrating in a companies core SaaS tools, ingesting data, and then displaying all misconfigurations that need to be remediated for a given security framework. Stack is Rails/React/Typescript/Postgres/Elasticsearch We've got three open engineering roles... - Source: Hacker News / over 1 year ago

My org is in a position where we'll need to get SOC II or ISO 27001 certified in the next year. I've been doing some research on the easiest way to go about this, and discovered secureframe (https://secureframe.com/). It looks like it is a platform that helps you automate/track some of the compliance tasks, but doesn't actually do the audit (they have partners that work through the platform). I'm wondering if... Source: over 3 years ago

Hi, founder of Secureframe (https://secureframe.com) here. Secureframe helps streamline compliance across SOC 2, ISO 27001, HIPAA, PCI DSS, and more. There are so many accurate responses in this thread. Like many have mentioned, SOC 2 is indeed not a prescriptive framework. Much of the confusion behind SOC 2 stems from that fact. It allows you to customize your InfoSec program to your company's needs. As we know,... - Source: Hacker News / over 4 years ago

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 / 2 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 / 7 days 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 1 month 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 / about 2 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 / 3 months ago