Amazon AWS Reviews

1. macloughlin

   · AV engineer · almost 3 years ago
   The best cloud platform out there

   You could say a lot of things about AWS, but among the cloud platforms (and I've used quite a few) AWS takes the cake. It is logically structured, you can get through its documentation relatively easily, you have a great variety of tools and services to choose from [from AWS itself and from third-party developers in their marketplace]. There is a learning curve, there is quite a lot of it, but it is still way easier than some other platforms. I've used and abused AWS and EC2 specifically and for me it is the best.

   👍 Pros:    Great documentation|Website structure visualization|You have control over everything|Flexibility

   👎 Cons:    Learning curve|A lot of dashboards for different things

Temporal Reviews

Amazon AWS mentions (484)

• My Experience Moving from AWS to Sevalla

  Not because infrastructure isn't important. It is. Not because Amazon Web Services (AWS) is a bad platform. It isn't. - Source: dev.to / 21 days ago

• How to Use Pre-Signed S3 URLs for Direct Browser-to-Storage Uploads

  The AWS S3 documentation covers all of these in detail. The configuration takes about an hour to get right the first time and rarely needs changes after. - Source: dev.to / about 1 month ago

• Why Your File Upload Endpoint Times Out at 4GB

  The first pattern is direct-to-storage. The client uploads chunks directly to an object storage service like Amazon S3 using pre-signed URLs. The application server creates the upload session and grants permission but never sees the file bytes. This pattern scales well because the application servers do not handle the upload bandwidth. - Source: dev.to / about 1 month ago

• 7 Free Tools for Managing Secrets and Environment Variables in Web Projects

  AWS Secrets Manager provides managed secrets storage with automatic rotation for RDS databases, Redshift clusters, DocumentDB, and other common services. For applications running on AWS infrastructure, Secrets Manager integrates directly with Lambda, ECS, EKS, and EC2 at the platform level, injecting secrets into the application environment without requiring files on disk or manual retrieval code. - Source: dev.to / 2 months ago

• Why Your SaaS Product's "Warranty Void If Regenerated" Policy Might Be Killing Your User Trust

  This approach, popularized by platforms like AWS, helps users make informed decisions about how far to push the boundaries while maintaining realistic expectations about support. - Source: dev.to / 4 months ago

Temporal mentions (15)

• 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 / 18 days 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 / about 1 month 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

• Best ChatGPT Alternatives in 2026: Evaluated on Automation, Persistence, and Data Ownership

  A typical production stack for teams using Claude or Gemini as the reasoning layer includes an LLM provider API, an orchestration layer (n8n, Temporal, or a custom Python service), application infrastructure (a server running the orchestration code), and a data layer (a database for storing results). Each boundary introduces a failure point. When the LLM provider changes its rate limits, as OpenAI did repeatedly... - Source: dev.to / 3 months ago

• 50 Lines of TypeScript to Automate Any Website with AI

  The core is a browserclaw agent loop wrapped in a Temporal workflow. The AI navigates to your provider's payment page, identifies form fields from the snapshot, fills in your payment details, and submits. Every successful payment generates a "biller skill" — a playbook that makes subsequent payments to the same provider faster and more reliable. - Source: dev.to / 4 months ago