- If there is a primitive not currently supported (say running a temporal workflow service) is it possible to define a new primitive for this? Just wondering what it looks like if/when you need something not currently supported.
by danielstocks
2 subcomments
- Happy Encore customer here! I’m kind of surprised they haven’t gotten more attention. It’s like the DX of Vercel for backend and infra, but open source and you can connect it to your existing cloud provider (we use GCP, but also works with AWS). We rarely have to think about about infra or CI/CD things. It just works, and on the rare occasion it doesn’t the team has been super quick to resolve it.
It’s like having a in-house 24/7 dev ops infra team but for a fraction of the cost!
Disclaimer: Our infrastructure needs are not super complex: Web services, SQL, key-value store, pub-sub and few other parts, your mileage may vary depending on your needs.
by sausagefeet
1 subcomments
- How does Encore handle the following scenarios?
1. I want to deploy to a testing environment where I may want to use different users, different sized services, or even mock services so I don't have to pay for them?
2. I want to develop in an isolated environment (maybe without internet or simply I'm trying to develop a narrow feature that doesn't require the rest of the infrastructure)?
3. How does it handle security elements like VPCs, IAM roles, all these things that are the context my application runs in that I don't necessarily want to couple to my application code?
- 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?
- Pretty interesting. I wish this was available for .net. Would love to try this out.
- Curious about how this compares to alchemy - https://alchemy.run/
- Yea really surprised encore isn’t more known and popular. Between it and convex they are the best things right now in building backends.
- Encore user here, support sucks and the Environment Destruction feature does not work properly, I have an environment that was stuck destroying for days (did it manually later on AWS).
Please, improve the support, we would love to pay if you guys were responsive enough.
by thecupisblue
1 subcomments
- 9x faster than express is a bold claim, would be interesting to see how it holds up with real application logic and some real benchmarks/usecases.
- What's the pricing model? Couldn't figure that out neither on Github nor on your webpage.
by stackskipton
1 subcomments
- As Ops guy, all infrastructure declared in application code eventually leads to crying if you get big enough.
That being said, I know we are expensive and "don't add to bottom line" so this looks like good enough hacky kludge as anything else.
by rubenvanwyk
2 subcomments
- Have been watching Encore for a while, excited about prospects of it in other languages like Python!
- Is Azure support on the roadmap?
- cool...
btw, on a tangent, I always thought that infra can be defined in typescript types.... is is strange but no need for custom language
someone please steal this idea and make something out of it
- the type-safe infrastructure primitives are interesting, curious how it compares to something like effect or nestjs for actual production use
- How does it compare with SST?
by ForHackernews
1 subcomments
- This an interesting idea, but I'd be skeptical of having this much coupling between application code and infrastructure. It's like an anti-12 Factor App.
It might make sense for something like a "serverless" app where the units of the business logic are intended to map directly onto cloud provider entities.
It reminds me of https://aws.github.io/chalice/ but cloud-agnostic and Typescript in place of Python
- Opened it, saw I needed to wrap my routes with api(), closed it - sounds like a solution for a problem PaaS has solved 10 years ago.