Flexiple Reviews

Temporal Reviews

Flexiple mentions (5)

• This startup made $3 million with a no-code tech stack of $100/month

  How Flexiple made $3 million with a no-code tech stack of $100/month. Source: over 3 years ago

• Ask HN: Examples of SaaS companies that use SEO as their main traction channel

  Think https://flexiple.com/ is one example, a marketplace more than a SaaS, though. - Source: Hacker News / almost 4 years ago

• I built a $3M startup with a $60/month NoCode stack. And, now I want to tell the story of your NoCode journey!

  My co-founders and I started buildd-ing our startup, Flexiple — a platform that connects companies with top tech freelancers — while we were in college. Source: almost 4 years ago

• Converting String to Float in Python

  This tutorial is a part of our initiative at Flexiple, to write short curated tutorials around often used or interesting concepts. - Source: dev.to / about 5 years ago

• Building $1K-$10K MRR Marketplaces - various domains and niches

  Flexiple: Hire Pre-Screened Freelance Developers & Designers Flexiple is a network of top freelance developers and designers with hourly rates ranging from $30 to $100. Making $1 million/year in revenue. Source: over 5 years ago

Temporal mentions (17)

• Temporal in Production: Sharp Edges & Good Practices

  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 / 15 days ago

• Your Agent Bills While It Waits. Here's the Fix.

  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 / 21 days ago

• Compiler as Custodian

  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

• How we turned our workflow editor into a real SDK

  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 / 2 months ago

• Three days debugging a missing trace

  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