Show HN: Encore – Type-safe back end framework that generates infra from code

(github.com)

76 points andout_ | 2 comments | 14 Nov 25 11:41 UTC | HN request time: 0.399s | source

Show context

wolando ◴[14 Nov 25 12:16 UTC] No.45926074[source]▶

Part of the selling point of terraform is that I can easily switch clouds if I need to. That's only partially true, most of your terraform would need to change to move from e.g. AWS to GCP, but still, your (hard-fought) experience with terraform on one platform will help when moving to another. If I define my infra the encore way, will I be locked in to one cloud, or can I easily migrate if I need to? Furthermore, I only see Go and Typescript, do you have a roadmap for supporting more languages?

replies(3): >>45926090 #>>45926717 #>>45927184 #

1. andout_ ◴[14 Nov 25 12:20 UTC] No.45926090[source]▶

>>45926074 #

Good question! With Encore, your application code is actually more portable than with Terraform because you are defining infrastructure semantically (eg. "I need a Postgres database"), not with cloud-specific config. The same code deploys to AWS, GCP, or even locally with Docker so no Terraform rewrite is needed when switching clouds.

As for the language support; we support Go and TypeScript today. We're focusing on making these rock-solid first, but more languages are on the roadmap. Python is the likely next candidate.

replies(1): >>45931179 #

2. stefanka ◴[14 Nov 25 19:39 UTC] No.45931179[source]▶

>>45926090 (TP) #

Do you consider supporting rust?

↑