If you've never seen Adonis in the wild, or you've only ever reached for Next.js / Nuxt / a decoupled SPA, this article is the gentle tour I wish I'd had. - Source: dev.to / about 2 months ago

Batteries included backend frameworks exists in the JS ecosystem, just look at https://adonisjs.com/ . The problem is that the nodejs ecosystem started off with micro-frameworks as the antithesis to what they believed were “overbearing” frameworks, like rails and Django, at the time. I remember express’s selling point was to build quick and dirty. - Source: Hacker News / 10 months ago

I'm currently building out an app using AdonisJS. Its billed as a Rails like experience but in node. https://adonisjs.com/ I did a comparison between Rails, Adonis and Fiber (a Go "framework") before settling on Adonis (mostly due to node ecosystem and type safety). It's been excellent so far, and the creator has an excellent series of tutorial videos that can get you up to speed quickly... - Source: Hacker News / over 1 year ago

Database Migration files and Models: For my backend, my go to NodeJs framework is AdonisJS. I love it because it comes with libraries for building production ready applications out of the box such as auth, emails, CORS, migrations, seeders, etc. It also uses Typescript. So, I create a basic AdonisJS app, and using my Database design, I prepare database migration files and models that match, This is easy because... - Source: dev.to / over 1 year ago

Vine is a data validation library developed by Harminder Virk for the Adonis framework. - Source: dev.to / over 1 year 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 / 5 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 / 11 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 / 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