eandre

7 ms·

1.
Making My Terraform AI Friendly(ivan.codes)
3 points by eandre 21d ago|2 comments
2.
SQS consumer can hang forever by default(encore.dev)
4 points by eandre 1mo ago|0 comments
3.
We compiled our TypeScript parser to WASM(encore.dev)
8 points by eandre 2mo ago|0 comments
4.
We put a Redis server inside our runtime(encore.dev)
39 points by eandre 3mo ago|13 comments
5.
Benchmarking AI agents across five TypeScript back end frameworks(encore.dev)
3 points by eandre 4mo ago|1 comments
6.
Last Year of Terraform(encore.dev)
8 points by eandre 7mo ago|2 comments
7.
Handling long-running LLM streams in a stateful backend(blog.leap.new)
2 points by eandre 1y ago|0 comments
8.
Handling long-running LLM streams in a stateful backend(blog.leap.new)
9 points by eandre 1y ago|0 comments
9.
by eandre 2y ago
Thanks for submitting this! I'm one of the founders, happy to answer any questions.
10.
by eandre 2y ago
We've published benchmarks against most of these already, see https://github.com/encoredev/ts-benchmarks
11.
by eandre 2y ago
I've published proper instructions for benchmarking Encore.ts now: https://github.com/encoredev/ts-benchmarks/blob/main/README.... . Thanks!
12.
by eandre 2y ago
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 Disclaimer: I'm one of the maintai
13.
Putting an event loop in your event loop(encore.dev)
3 points by eandre 2y ago|1 comments
14.
Putting an event loop in your event loop(encore.dev)
3 points by eandre 2y ago|1 comments
15.
Encore: Distributed systems runtime for TypeScript, written in Rust(encore.dev)
55 points by eandre 2y ago|15 comments
16.
by eandre 3y ago
Encore CEO here. Thanks for the feedback. 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
17.
by eandre 3y ago
Thanks for the shoutout, happy to answer any questions about Encore if anyone's curious. (I'm the founder.)
18.
by eandre 3y ago
If you like the concept but prefer Go over Rust for backends, check out Encore [1]. Disclosure: I'm one of the founders. [1] https://encore.dev
19.
Understanding Go 1.21 generics type inference(encore.dev)
2 points by eandre 3y ago|1 comments
20.
Long term ownership of event-driven systems(encore.dev)
2 points by eandre 3y ago|0 comments
21.
Scrubbing sensitive data at 180MiB/sec/core(encore.dev)
2 points by eandre 3y ago|0 comments
22.
by eandre 3y ago
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 and programming languages. The overall code
23.
Scrubbing sensitive data at 180MiB/sec/core(encore.dev)
1 points by eandre 3y ago|1 comments
24.
by eandre 3y ago
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.
25.
Scrubbing sensitive data at 180MiB/sec/core(encore.dev)
5 points by eandre 3y ago|1 comments
26.
by eandre 3y ago
Looks cool! How does it come up with different architectures when changing from one type of database (e.g.) to another?
27.
by eandre 4y ago
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,
28.
Full-Stack Preview Environments(encore.dev)
2 points by eandre 4y ago|0 comments
29.
Building an Uptime Monitor(encore.dev)
1 points by eandre 4y ago|0 comments
30.
Software Engineering Tips for Students(catball.dev)
4 points by eandre 4y ago|0 comments

More ›