Introducing: Encore for TypeScript

Encore for TypeScript is the simplest way of building event-driven and distributed systems in TypeScript.
It's designed around a new Open Source Backend SDK, which makes it really simple to create backend services and APIs, and use cloud infrastructure resources, such as:
- SQL Databases
- Pub/Sub topics and subscriptions
- Caches
- Cron jobs
- Secrets
Encore also provides a Cloud Platform to fully automate DevOps and infrastructure management in your own cloud on AWS/GCP.
Check out the Open Source project on GitHub: github.com/encoredev/encore
Try it yourself: encore.dev
00:00 - Intro
00:40 - Key Benefits
00:56 - Declarative Backend SDK
01:08 - Hello World example
01:20 - encore run
01:31 - Local Development Dashboard
01:45 - Extended runtime type-safety
02:05 - Declaring cloud infrastructure
02:17 - SQL Database example
02:37 - Event-driven example with Pub/Sub
03:12 - Rust runtime
03:35 - How Rust runtime integrates with Node.js
05:00 - Cloud DevOps Platform
05:25 - Cloud Platform features
06:41 - Try it yourself
#backend #typescript #launchweek #coding #programming #cloud #cloudnative #microservices #pubsub #opensource #postgres #devops

[@GrittyMaholmes]

Try putting the script close to the camera so its not obvious you are reading from script BUT A LOVELY JOB YOU GUYS HAVE DONE AWESOME !

[@encoredev]

Good tip. Yeah we tried, but with a little janky setup, maybe we can get some bloopers out so you can laugh with us. Thanks for the support! :)

[@Y2Kvids]

*TYPESCRIPT

[@encoredev]

@@Y2Kvids LOL!

[@uchennaofoma4624]

Looks amazing. Was excited about effect (and still am) but I'm excited about this too

[@encoredev]

Give it a spin and tell us what you think!

[@TheFocusedCoder]

Fantastic! I've been waiting for this

[@encoredev]

Glad to hear it!🎉

[@metaroonlabstech]

This is so cool! 🎉 Forwarding to our team

[@encoredev]

Thank you!

[@aaronfree6796]

Huge news!!! Congrats!!

[@encoredev]

Thank you Aaron!

[@nyashachiroro2531]

Low key looks like Kevin De Bruyne

[@encoredev]

You're not wrong

[@epicmap]

It would be even cooler if the rust app could run multiple nodejs instances and balance the load between them(when configured). It would be truly amazing in terms of mitigating the nodejs single threaded nature

[@davien001]

I thought V8 isolates fixed that?

[@mikopiko]

I had a feeling you guys where from Sweden, and looking it up, yepp your office is in Stockholm. Cool!

[@marcuskohlberg5780]

Yessir, ex-Spotify crew here in the deep north.

[@cjthedeveloper]

this looks awesome guys :)

[@cjthedeveloper]

0 deps is crazy. and 7x faster? need me some benchmarks

[@encoredev]

@@cjthedeveloper Yeah, the 7x is based on all our real world testing to date. We're going to publish something more in-depth as soon as we can!

[@encoredev]

Thanks for the support!

[@Voltra_]

It's really cool that it's fully compatible with node! For the types part, is it a superficial parser, or an alternative front-end to the transpiler that actually gets the fully resolved types?

[@encoredev]

It does type resolution, resolving references to other types, imports, etc. It's not fully-featured enough to support all of TypeScript's features, but it's a large enough subset that you don't feel constrained. (The type resolver only cares about the types you use in API endpoints and Pub/Sub messages, so outside of those types you can do whatever you want.)

[@JoseSouza-nc2yg]

Congrats!

[@encoredev]

Thanks Jose!

[@_js]

🚀

[@nested9301]

This looks promising 🤠

[@encoredev]

Give it a spin and tell us what you think!

[@codeitlikemiley]

encore built with rust? but i dont see any rust sdk? or any tutorial how to use it with rust?

[@ckpioo]

yeah what's the issue?

[@encoredev]

Encore's TypeScript runtime is built with Rust, but there's not currently any Backend SDK for Rust. Next we'll add support for Python, but Rust is on the table after that.

[@GreatTaiwan]

So encore is what again? A framework? Like spring ? Or .net

[@encoredev]

It's a Backend SDK for declaring backend primitives like services, APIs, databases, Pub/Sub, etc. in application code, so you application becomes self-provisioning. The local development tools runs your environment and provides observability. There's also a cloud platform that automates deployment and infrastructure management in your cloud on AWS/GCP.

[@seannewell397]

I know Deno would naturally be a heavier runtime, and y'all obviously have things in place to run rust well, but curious if trying deno failed for some reason?

[@seannewell397]

OOO you extract auto-validators from the public I/O interfaces... interesting.

[@encoredev]

It ended up more complex to support off the bat, but we'll add Deno/Bun support in the future.

[@yassinesafraoui]

What is it with those french named libraries coming out!

[@epicmap]

Does it work with Bun? :)

[@encoredev]

It's not officially tested/supported yet, but it could work. We're planning on adding official support down the line, but given the performance in Node it's not clear it's an urgent need. We'll be responsive to what the community asks for though!

[@cecece775]

Hope that’s not another new runtime that is free now but then we’ll have to pay

[@encoredev]

It's Open Source! github.com/encoredev/encore

[@CuriousSpy]

1 big problem i see with modern tools is they often trying to do everything poorly instead of one thing good. For example encore doesn't give you ability to connect your database, instead you have to stick with their solution. I haven't found encore self-hosting ability so it means your app is alive only if encore is alive. Hey, Encore, great product but eliminate errors at the start: build a platform, not a product, so companies can actually trust you.

[@everyhandletaken]

I was so excited to discover Encore, but then I realised how much it would cost to go the AWS route... wow. With their subscription, plus provisioning cost, plus infrastructure costs, it's 30x more than I can deploy it myself for, in a self-managed way. I wish I could use this & deploy anywhere, myself, but couldn't see that was possible. I see what they are looking to achieve & it is great if you want to have your hand held all the way through.. but I want to be dropped off at the deployment step & find my own way.

[@encoredev]

We have official instructions on how to self-host: encore.dev/docs/how-to/self-host. We also describe in detail how to migrate away from Encore: encore.dev/docs/how-to/migrate-away. Even if you use Encore's platform, it deploys to your own cloud, so you retain full control over all the infrastructure. That infrastructure has zero dependencies on Encore's platform, so "your app is alive only if encore is alive" is not at all the case. Your application wouldn't even notice.

[@encoredev]

​@@everyhandletaken We have official self-hosting instructions: encore.dev/docs/how-to/self-host. And for small-scale hobby use you can use Encore Cloud, completely for free.

[@everyhandletaken]

@@encoredev apologies, I misread the documentation! Thank you for replying

[@AenGex]

Why? What's the point? Did you not have internet access to look for NestJs? Or? Are you some kind of special snowflakes that claim to bring the 'Don't reinvent the wheel', 'Our framework is the best', 'Is the faster'? What is the point, what do you offer to the table? You inspire bad practises (I guess you are all coming from React, which could explain it.), with absolutely random architecture. Just cause you did a wrap around Node Request/Response and SQL driver does not mean you have to release another immature backend framework. NestJS offered microservices, monorepo, protobuff, streams, actual event driven architecture, proper controller/service/repo since you were in liquid form. Why did you even bother starting 1 more instead of contributing? What's the matter with you and projects like the Effect (RxJs wannabe but inferior)?

[@encoredev]

Encore and NestJs don't overlap much. Encore handles much more than NestJs in terms of cloud infrastructure automation, and provides a whole suite of tooling around local development, API documentation, observability, and more. They work great together and complement each other really nicely.

[@azizsafudin]

nestjs is hot garbage when it comes to type safety.

[@nested9301]

Bro chill let people every tool has it's own usecase on top of that if you don't want to use it just don't nobody cares

[@dscham1507]

@@nested9301 I know to little about encore or NestJS to judge. But in principal, he has a point. Why spead resources across many similar projects, rather than improve the one that's most mature?