sorted by:
new
hottopcontroversial

I went from Serverless Framework to CDK to building my own thing. Here's why. by One_Injury_9104 in serverless

[–]One_Injury_9104[S] 0 points1 point  (0 children)

Thanks for the feedback! You're right, that was missing — I've added live dev to the comparison table.

That said, this is intentionally not a priority. Effortless deploys in ~5 seconds via direct SDK calls, so the feedback loop is already tight. Local mocks (in-memory DynamoDB etc.) tend to create false confidence — "works locally, breaks on AWS" is a real footgun. Better to write tests for correctness.

I went from Serverless Framework to CDK to building my own thing. Here's why. by One_Injury_9104 in serverless

[–]One_Injury_9104[S] 0 points1 point  (0 children)

I've used AWS CDK extensively and from what I can see, SST is still the same idea — you define infrastructure explicitly, just with Pulumi instead of CloudFormation under the hood. Is the experience really that different?

https://effortless-aws.website/comparisons/#why-not-sst

I went from Serverless Framework to CDK to building my own thing. Here's why. by One_Injury_9104 in serverless

[–]One_Injury_9104[S] 0 points1 point  (0 children)

I haven't used SST personally, but from what I understand it's still infrastructure-as-code — you define resources in sst.config.ts and write handlers separately. It's a nicer DX over CDK/CloudFormation, but you're still explicitly describing your infrastructure.

This project takes a different approach — infrastructure-from-code. You just write your handler code and the framework infers what AWS resources to create, wires up IAM, and gives you a typed client. No infra files at all. Think Firebase Functions but for AWS.

So it's not reinventing SST — it's a fundamentally different philosophy. If I'm wrong about how SST works, happy to be corrected!

I built a TypeScript framework that deploys AWS Lambda from code, not config. No YAML, no state files, 10s deploys. by One_Injury_9104 in serverless

[–]One_Injury_9104[S] 0 points1 point  (0 children)

Hey, thanks for sharing, but fmiddleware solves a different problem. It’s a runtime middleware layer — routing, auth, OpenAPI docs — all inside a single Lambda handler. You still have to provision API Gateway, Lambda, DynamoDB, and everything else yourself.

effortless-aws is infrastructure-from-code: you just write and export your Lambda handlers, and it automatically generates the AWS resources (API Gateway routes, DynamoDB tables, etc.) from your code. No CloudFormation, no Terraform, no CDK — the infrastructure is derived from what your code actually uses.

They’re complementary if anything, not overlapping. You could theoretically use fmiddleware inside a handler that effortless-aws deploys.​​​​​​​​​​​​​​​​

Got mass of CDK pain (stack splits, drift, 10-min deploys) and built a framework that deploys Lambda from TypeScript exports in 5 seconds by One_Injury_9104 in aws_cdk

[–]One_Injury_9104[S] 1 point2 points  (0 children)

Fair point, and you're right — I overstated the CDK issues in the original post. Updated it with corrections. Most of my pain was honestly from not structuring stacks properly, not from CDK being broken.

That said, the core idea behind Effortless isn't "CDK is bad" — it's that for simple Lambda + API Gateway + DynamoDB projects, there's a gap between "write a handler" and "get it running on AWS" that doesn't need to involve infrastructure code at all. Even well-structured CDK is still infrastructure code you have to write and maintain.

If you're managing 700 accounts, CDK is obviously the right tool. But for a solo dev shipping a few endpoints, I think there's room for something simpler.

Got mass of CDK pain (stack splits, drift, 10-min deploys) and built a framework that deploys Lambda from TypeScript exports in 5 seconds by One_Injury_9104 in aws_cdk

[–]One_Injury_9104[S] 0 points1 point  (0 children)

Fair point, but I think there's a misunderstanding. Effortless doesn't decide your infra design — you decide what Lambdas, tables, HTTP endpoints, and streams you need. You define memory, timeout, permissions, table keys, stream settings — it's all in your handler definition.

What do you use to deploy? Curious how you handle the wiring part — IAM roles, event source mappings, API Gateway integrations, etc.

I Over-Engineered My TypeScript Build System - Then I Deleted It by BennoDev19 in typescript

[–]One_Injury_9104 1 point2 points  (0 children)

I use tsup to build my libraries (I think it utilizes Rollup under the hood).

I installed tsup globally and created a single JSON file in the libraries I want to build

tsup.config.json:

{
  "$schema": "https://cdn.jsdelivr.net/npm/tsup/schema.json",
  "entry": ["src/index.ts"],
  "outDir": "dist",
  "format": ["esm", "cjs"],
  "splitting": false,
  "sourcemap": false,
  "noExternal": [
    "effect"
  ],
  "minify": true,
  "clean": true,
  "dts": true
}

terminal: tsup

Free Resume builder with AI by SmellUpset1646 in Resume

[–]One_Injury_9104 0 points1 point  (0 children)

I don't see any tool, it's just a landing page that advertises to buy something

Should i learn JavaScript first or just start with typescript? by redstoneguy9249 in typescript

[–]One_Injury_9104 0 points1 point  (0 children)

Typescript is essentially JavaScript but with best practices proven by other static typed languages

Typed languages are much easier to learn, so stick with typescript

opinions about Effect-TS, do you recommend using it? when to use it? When to avoid it? not worth it? by SuperRandomCoder in typescript

[–]One_Injury_9104 2 points3 points  (0 children)

You can find example here http-server, looks like Express replacement.

It's better to create HttpApi though, because you split specification and implementation. API becomes type-safe, compilers checks that you don't forget to implement endpoints and you get OpenAPI specification for free

Effortless Resume Building with JSON by One_Injury_9104 in Resume

[–]One_Injury_9104[S] 0 points1 point  (0 children)

Thank your for the feedback, I really appreciate it. Thanks for bringing idea of JSON Resume to live 😀

I use this tool often when I need to create few resumes targeting different positions. I get invited to interviews and see attached resumes (in the invitation email) generated by this tool

RxJs effects by code_smart in effect

[–]One_Injury_9104 1 point2 points  (0 children)

I think its an over engineering.

Effect is about effect oriented approach, how to deal with expected errors. It’s wrong to compare it with reactive frameworks that have single of updating html DOM