Top all-time · #1520
Encore
Company blog · encore.dev/blog · on HN as eandreprogrammingweb
Encore is the company blog at encore.dev, writing about programming and web. Since 2020, 47 different Hacker News readers have linked it 135 times, most often “Encore – Back end framework for type-safe distributed systems”. It is still writing: the last post was on 2026-10-06, and you can follow it by feed.
Encore runs your app with real infrastructure locally, then automatically provisions and deploys it to your own AWS or GCP.
Most-linked posts?
- Encore – Back end framework for type-safe distributed systems10 people · 10 mentions · first linked 2021-05-17
- Encore CloudOps7 people · 22 mentions · first linked 2020-02-17
- Retries – An interactive study of request retry methods5 people · 5 mentions · first linked 2023-10-10
- Last Year of Terraform4 people · 4 mentions · first linked 2026-02-25
- Go Modules Cheat Sheet3 people · 4 mentions · first linked 2021-04-30
- Building a Rust Runtime for TypeScript3 people · 4 mentions · first linked 2026-04-08
- Queueing3 people · 3 mentions · first linked 2024-05-22
- Encore: Distributed systems runtime for TypeScript, written in Rust3 people · 3 mentions · first linked 2024-05-06
- Scrubbing sensitive data at 180MiB/sec/core2 people · 4 mentions · first linked 2023-06-08
- Putting an event loop in your event loop2 people · 4 mentions · first linked 2024-06-17
What Hacker News says?
I've been working on something that might be interesting to you [1]. It gives you the full flexibility of a programming language while removing all the boilerplate surrounding your business logic through static analysis. Have a look at the Encore Playground [2] to see a real-world example. [1] https://encore.dev [2] https://play.encore.dev/vHZHuXf2zca3dg
Comment linking /
on “Ask HN: What are your favorite low-coding apps / tools as a developer?”Submitted Go Modules Cheat Sheet as a story · 138 points
HN discussionwow very very interesting. I think we can discuss about it on hours. 1.) What would you think of things like hetzner / linode / digitalocean (if stable work exists) 2.) What do you think of https://sst.dev/ or https://encore.dev/ ? (They support rather easier migration) 3.) Could you please indicate the split of that 1 million $ in devops time and google cloud costs unnecessarily & were there some outliers (like oh…
Comment linking /
on “We're Leaving Kubernetes”Submitted The Thundering Herd Problem as a story · 80 points
HN discussionThanks for the feedback! (I'm the founder of Encore) Your thoughts are very much in line with where we're going. We're working on natively supporting queues, pubsub, object storage, etc. Our roadmap is available at https://encore.dev/roadmap which should give you an idea. We definitely intend on supporting more storage options. We already do provide end-to-end integration testing out of the box that integrates with…
Comment linking /roadmap
on “Next.js 12”Submitted Encore: Distributed systems runtime for TypeScript, written in Rust as a story · 55 points
HN discussionMaybe something like https://encore.dev ? Looks like a similar mindset.
Comment linking /
on “Next.js 12”Submitted Retries – An interactive study of request retry methods as a story · 45 points
HN discussionGreat article. Working on my own startup ( https://encore.dev ) I also feel the urge to measure my progress in terms of output, not outcomes. I have to constantly remind myself that what matters is the outcome. Focus on producing a concrete, visible artifact every day and use that as your measure of progress instead. And make sure to stay sane; startups are not a balanced lifestyle but that just means we need to pus…
Comment linking /
on “Post YC Depression”Submitted Queueing as a story · 32 points
HN discussionThis is good advice. I've been working on a side project for almost a year now [1]. It's a constant struggle with the pressure to reach a certain amount of users or impact, when at the end of the day I've just been building it to scratch my own itch. This article is a helpful reminder of that. [1] https://encore.dev
Comment linking /
on “What eight years of side projects have taught me (2019)”Submitted How we used Go 1.18 generics when designing our Identifiers at Encore as a story · 12 points
HN discussionEncore.ts is doing something similar for TypeScript backend frameworks, by moving most of the request/response lifecycle into Async Rust: https://encore.dev/blog/event-loops Disclaimer: I'm one of the maintainers
Comment linking /blog/event-loops
on “Using Rust in non-Rust servers to improve performance”Submitted Encore – Back end framework for type-safe distributed systems as a story · 11 points
HN discussionEncore | Engineers + UX Designers | Remote | Open-source | Full-time | https://encore.dev Encore is the cloud development platform of the future. Modern software has moved to the cloud, but developer tools haven't adapted. We’re building the must-have dev tools of the future, to help developers create better products, faster. Help us redesign the day to day lives of developers to be more enjoyable and more productiv…
Comment linking /
on “Ask HN: Who is hiring? (November 2021)”Submitted Designing an algorithmic cloud infrastructure provisioning system as a story · 11 points
HN discussionEncore | Go + Backend Engineers | Remote | Open-source | Full-time | https://encore.dev Encore is the cloud development platform of the future. Modern software has moved to the cloud, but developer tools haven't adapted. We’re building the must-have dev tools of the future, to help developers create better products, faster. Help us redesign the day to day lives of developers to be more enjoyable and more productive.…
Comment linking /
on “Ask HN: Who is hiring? (August 2021)”Submitted Testscript, a hidden gem the Go team kept locked away as a story · 10 points
HN discussionEncore | Go + Backend Engineers | Remote | Open-source | Full-time | https://encore.dev Encore is the cloud development platform of the future. Modern software has moved to the cloud, but developer tools haven't adapted. We’re building the must-have dev tools of the future, to help developers create better products, faster. Help us redesign the day to day lives of developers to be more enjoyable and more productive.…
Comment linking /
on “Ask HN: Who is hiring? (October 2021)”Submitted How we used Go 1.18 generics when designing our Identifiers as a story · 10 points
HN discussionThis might be too basic, but I found this blog post to be an incredible introduction to queues: https://encore.dev/blog/queueing
Comment linking /blog/queueing
on “Ask HN: What do you monitor on your servers?”Submitted Encore.ts: A New Type of Framework as a story · 8 points
HN discussionI could really recommend Encore https://encore.dev/ that works best when you use their PaaS offering https://encore.cloud/ (think of NextJS & Vercel combo). One can argue it goes against some of the Go principles, but it's a really nice stack for solos or small teams without dedicated SREs. And as you grow you can BYOC & deploy it yourself or completely rewrite your API layer using Go stdlib. You would still need Ne…
Comment linking /
on “Rails for everything”Submitted Building a Rust Runtime for TypeScript as a story · 7 points
HN discussionFWIW, that's not what Go does. In your scenario, a Go binary ends up with a single copy of library X -- the 1.0.1 version. That's because library A is stating "I require at least v1.0.0 of X", and library B is stating "I require at least v1.0.1 of X". The minimal version that satisfies both of those requirements is v1.0.1, and that's what ends up in the binary. That behavior is Go's "Minimal Version Selection" or "M…
Comment linking /guide/go.mod
on “How Go mitigates supply chain attacks”Submitted How we got 1500 GitHub stars in 1 week as a story · 7 points
HN discussionWhether you build microservices or just services, distributed systems are undeniably here to stay. In today’s world there are very few products that can run on a single machine, whether it is for latency or availability or redundancy. That said, the challenges of building such systems are real, and the developer experience is universally quite awful compared to our monolithic, single-server past. It’s for that reaso…
Comment linking /
on “Microservices: Why Are We Doing This?”Submitted Last Year of Terraform as a story · 6 points
HN discussionThe difficult with backend is dealing with state. It's easy enough to provide a simple experience when dealing with stateless frontends, backends are a very different story. You're right that we need better tools. I'm the founder of Encore [1] which is all about bringing the simplicity of Vercel/Netlify to backend development. Not by substituting the backend for a BaaS but by building a developer experience hand-cra…
Comment linking /
on “Docker, Kubernetes, Terraform, and AWS crash course series”Submitted Encore the Go platform/framework now has MCP as a story · 6 points
HN discussion
