WebDrive Reviews

1. Hudson L.

   · Systems Engineer · almost 6 years ago
   Can't live without it!

   I started using Webdrive about 5-6 years ago when my company implemented it to connect to our Sharepoint server. I've used it for SFTP, and to automatically backup my files to S3. It just makes getting to your files any where in the cloud the same as getting to them on your PC. I use it all the time, but rarely think about it. Kind of a set it and forget type of thing. I've used their tech support a couple of times over the years and have found them to be helpful.

   👍 Pros:    Fast|Good support|Lots of connectors|Easy to use|Best way to access files in the cloud or on company servers

   👎 Cons:    Mac version is missing a few features

Temporal Reviews

WebDrive mentions (1)

• Best software for mounting cloud service as local/network drive

  Ive been using webdrive for years and its pretty great. Never had any complaints. Source: about 4 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 / 6 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 / 11 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