Backend engineer with a passion for developer productivity. Ex-
Spotify. Now building https://encore.dev to make it easy and fun to build great backends.
@_eandre on Twitter
Submissions
We compiled our TypeScript parser to WASM
encore.dev
8 points·by eandre··0 comments
We put a Redis server inside our runtime
encore.dev
39 points·by eandre··13 comments
Benchmarking AI agents across five TypeScript back end frameworks
encore.dev
3 points·by eandre··1 comments
Last Year of Terraform
encore.dev
8 points·by eandre··2 comments
Handling long-running LLM streams in a stateful backend
blog.leap.new
2 points·by eandre··0 comments
Handling long-running LLM streams in a stateful backend
blog.leap.new
9 points·by eandre··0 comments
Putting an event loop in your event loop
encore.dev
3 points·by eandre··1 comments
Putting an event loop in your event loop
encore.dev
3 points·by eandre··1 comments
Encore: Distributed systems runtime for TypeScript, written in Rust
encore.dev
55 points·by eandre··15 comments
Understanding Go 1.21 generics type inference
encore.dev
2 points·by eandre··1 comments
Long term ownership of event-driven systems
encore.dev
2 points·by eandre··0 comments
Scrubbing sensitive data at 180MiB/sec/core
encore.dev
2 points·by eandre··0 comments
Scrubbing sensitive data at 180MiB/sec/core
encore.dev
1 points·by eandre··1 comments
Scrubbing sensitive data at 180MiB/sec/core
encore.dev
5 points·by eandre··1 comments
Full-Stack Preview Environments
encore.dev
2 points·by eandre··0 comments
Building an Uptime Monitor
encore.dev
1 points·by eandre··0 comments
Software Engineering Tips for Students
catball.dev
4 points·by eandre··0 comments
Designing an algorithmic cloud infrastructure provisioning system
Encore.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
We sell developer productivity and devops automation, and compared to hiring additional engineers Encore is very cheap.
We’ve tried to align our incentives with the needs of our customers, so there are no usage-based or surprise fees when using Encore. The per-seat price may be higher but it’s transparent and predictable.
While some of the underlying functionality is based on Encore’s static analysis, the approach is quite general and can be adapted to lots of situations and programming languages. The overall code ended up being a couple hundred lines, not more.
Author here, happy to answer any questions. While some of the underlying functionality is based on Encore’s static analysis the approach is quite general and can be adapted to lots of situations.
This is one of the core use cases where Encore [1] really shines. It helps you get up and running really quickly by natively supporting common cloud infrastructure components (databases, Pub/Sub, caching, cron jobs, secrets management, etc), and a simple low-boilerplate way of defining APIs.
It automatically provides API docs, architecture diagrams, and infrastructure provisioning, based on static analysis of your code base.
But you need a UK bank account, which requires a officer with a registered address in the UK. We were lucky our investors were UK-based otherwise it would have been a nightmare. Then you need to argue HMRC valuation discounts if you want to issue EMI options, which are only valid for 3 months, so you need to do it repeatedly. And then EMI option schemes are 15+ pages long contracts. Sweden has an equivalent stock option scheme that's ~2 pages, in comparison.
We've set up a UK subsidiary so I can relate, but the process in Sweden was approximately 10x simpler: more automated, less bureaucracy, less ongoing admin work when the company is up and running.
As with all countries there are definitely things you need to learn. We relied on our lawyers to draft employment agreements because we were already using them as part of our seed fundraise. There are companies like Pocketlaw (https://pocketlaw.com) that provide solid, standard agreements that you could use.
The 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-crafted for dealing with cloud infrastructure.
If you want a similar experience to this but more optimized for backend development using Go, I've been building https://github.com/encoredev/encore for the past few years!
We've been using sqlc for the past few months building Encore and it's an incredible tool. If it sounds useful I highly recommend checking it out at https://sqlc.dev.
@_eandre on Twitter