With Netmaker, you can have greater control and customization by assigning dedicated IP addresses to specific nodes within your network. I just stumble upon it yesterday, check it out. Source: about 3 years ago

These days, I'm trying to deploy full mesh VPN network with netmaker. It is really easy to use and manage. However there are something makes me confused. Source: over 3 years ago

If a TCP based protocol isn't an absolute must have, I'd ditch OpenVPN for Wireguard with some kind of management overlay. e.g netmaker. Source: over 3 years ago

Do the net maker https://github.com/gravitl/netmaker worth trying to use instead of Tailscale? Tailscale is good, but I can watch YouTube over Wi-Fi in another country, but when I try to use Jellyfin to watch movies it’s not loading well. Source: over 3 years ago

Very relatable! At first, I struggled for days trying to make Netmaker or Innernet functional for my personal home server (Raspberry Pi behind multiple routers). But then I stumbled upon ZeroTier, and everything worked seamlessly within a couple of hours. Tailscale was actually the next one on my list because I heard many positive things about it over at r/selfhosted (especially about headscale). However, I did... Source: over 3 years ago

Temporal makes durable workflows, activities, retries, timers, failures, and long-running execution explicit. - Source: dev.to / 20 days 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 / about 2 months 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 2 months 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 / 3 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