Sling Reviews

Temporal Reviews

Sling mentions (7)

• Looking for a solution for scheduling across timezones. ex: If I plug in "5pm tomorrow" it shows that time for relevant timezones.

  Using Sling (https://getsling.com/) for a distributed CS team. It's working pretty well. We're spread across six timezones, been using it for five months. Free version's done well enough for us. Source: almost 4 years ago

• Scheduling

  If you want to try a free product, Sling scheduling app is good. You can google the reviews to see if that match your needs. Source: over 4 years ago

• How to Send Email Notification to Yourself

  But I think you might want to look at some more dedicated scheduling software like Sling. Source: over 4 years ago

• Apps for team communication

  I've used Sling with my guard team. It's primarily a scheduling app, but it also has messaging functions. Source: over 4 years ago

• Software to manage hospital shifts?

  I suggest https://getsling.com it's not open source but the free version is really good. Take a shot at it. GL. Source: about 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 / 5 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 / 10 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 1 month 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 / 3 months ago