Cool! You can check out our GraphQL tutorial here: encore.dev/docs/tutorials/graphql Be sure to join our Discord community if you have any questions: encore.dev/discord
Thank you! The project started 7 years ago and the first version for Go has been used in production for about 4 years. We released Encore.ts a few months ago. You can check out the OpenSource repo on GitHub: github.com/encoredev/encore
Thank you! The project started 7 years and the first version for Go has been used in production for about 4 years. We released Encore.ts a few months ago.
I'm excited to try this but I don't want to create an account. It seems there is an option to use app create without an account but I followed the instructions in the video and encore app init won't let me continue without logging in/creating an account. What's up?
Thanks for reporting! This is now fixed in v1.41.7 so you no longer need an account to run `encore app init`. You can upgrade using `encore version update` to get the latest CLI version.
We're working on publishing some tutorials. In the meantime, here's an example app showing how to use Sequelize with Encore.ts github.com/encoredev/examples/tree/main/ts/sequelize
Good for you! Obviously a lot of people are using Express and are ok with it. Whether or not performance is important depends on your use case. If you're building a tiny hobby project, it's largely academic. But if you're shipping a production backend to the cloud, it can have a pretty large impact. Lower latency has a direct impact on user experience. To state the obvious: A faster backend means a snappier frontend, which means happier users.
Would be interesting to do a comparison with Elysia, thanks for the suggestion! Here is a comparison with Fastify v5 that got released last week (Encore.ts is about twice as fast): encore.dev/blog/fastify-v5 Our comparison includes request type validation, that is probably why the numbers differ a lot from the numbers on elysiajs.com.
It's 3x faster than Elysia when using type validation, check out the updated benchmark article (benchmark code linked from article): encore.dev/blog/event-loops
Encore makes it simple to separate concerns by using multiple sub-systems and services using the API framework, and it provides observability and documentation out of the box so all service-to-service calls are clearly visible thanks to both tracing and automatic architecture diagrams. It also ensures the application logic is independent of specific infrastructure services using the cloud-provider independent infrastructure declarations in the framework. Here's an example app consisting of a few different services: github.com/encoredev/examples/tree/main/ts/uptime
As I mention in the video, Encore.ts is unopinionated when it comes to how you structure your code. You can follow the SOLID principles in your business logic if you like, Encore.ts will not stop you.
@@minhhieple6483 No, not necessarily. As shown in the video, you can not just swap out Encore.ts for Express and most middleware created for Express will not work out of the box for Encore.ts. Is there a particular library that you are thinking about using together with Encore.ts?
Update: Encore.ts is 3x faster than Hono with schema validation, and 70% faster without schema validation. See x.com/encoredotdev/status/1839668756878184810
Update: Encore.ts is 3x faster than Hono with schema validation, and 70% faster without schema validation. See x.com/encoredotdev/status/1839668756878184810
Encore is compatible with any external database, there's nothing stopping you from using whatever provider you want. Not all the built-in infra related functionality will work out of the box though.
It's 3x faster than Hono when using type validation, check out the updated benchmark article (benchmark code linked from article): encore.dev/blog/event-loops
Well nice.. but from those numbers I think it's on par with H3 , and u know what uses H3 out of the box ? NUXT JS. So in my case why bother splitting the code even more into another api module, when i can keep it inside the main app as a BFF (backend for frontend). What I like though about presented Encore is the TS integration and the builtin swagger-panel. HOWEVER, let's be honest .. past the dev phase, dont' think you'll waste time analyzing the data. At this point bragging that you made something faster than express.js , should be a standard; not a feature. Check any other alternative. They are all at least x5 faster.
It is a fair point that most modern web frameworks will be faster than vanilla Express but Express is still by far the most used web framework for Node.js with it's 32 million weekly downloads. Also, most Node.js devs are familiar with the Express API, that is why we feel that the comparison with Encore.ts makes sense. Encore.ts is not for everyone, if you feel like your current setup is working for you then that is great! But if you need to build a scalable, robust application with end-to-end type-safe, we believe Encore.ts is a great choice (we are a bit biased of course). In our experience, when having a distributed system with multiple services deployed to the cloud and millions of request per day, having access to tools like metrics and tracing is crucial for quickly finding bugs and bottlenecks.
Update: Encore.ts is 3x faster than Hono and Elysia with schema validation enabled, and 70% faster without. See x.com/encoredotdev/status/1839668756878184810
If nuxt gave the possibility to make auto-documentation of api routers with type-security out of the box with H3, it would be a fairy tale, but as it is, we have to look at the possibility to raise a server separately with less effort but similar metrics.
Update: Encore.ts is 3x faster than Hono and Elysia with schema validation, and 70% faster without schema validation. See x.com/encoredotdev/status/1839668756878184810
looks incredibly nice, migth try it out even today for a small graphql api
Cool! You can check out our GraphQL tutorial here: encore.dev/docs/tutorials/graphql
Be sure to join our Discord community if you have any questions: encore.dev/discord
Gosh this is crazy 😱
I am really stunned and wonder how long it took the team to build this great project
Thank you! The project started 7 years ago and the first version for Go has been used in production for about 4 years. We released Encore.ts a few months ago. You can check out the OpenSource repo on GitHub: github.com/encoredev/encore
Thank you! The project started 7 years and the first version for Go has been used in production for about 4 years. We released Encore.ts a few months ago.
Seems like a nice project to follow. Great job!
This looks pretty dope!
This looks promising. I will definitely try it.
Amazing, great job 😇
I'm excited to try this but I don't want to create an account. It seems there is an option to use app create without an account but I followed the instructions in the video and encore app init won't let me continue without logging in/creating an account. What's up?
Thanks for reporting! This is now fixed in v1.41.7 so you no longer need an account to run `encore app init`. You can upgrade using `encore version update` to get the latest CLI version.
Is it compatible with NestJs?
Yes, here's a how to guide: encore.dev/docs/ts/how-to/nestjs
How do i use ORM with encore?
We're working on publishing some tutorials. In the meantime, here's an example app showing how to use Sequelize with Encore.ts github.com/encoredev/examples/tree/main/ts/sequelize
good job
ExpressJS served us well. btw, what is fast nowadays, it’s not like you build the next facebook for the most 😉
Good for you! Obviously a lot of people are using Express and are ok with it. Whether or not performance is important depends on your use case. If you're building a tiny hobby project, it's largely academic. But if you're shipping a production backend to the cloud, it can have a pretty large impact.
Lower latency has a direct impact on user experience. To state the obvious: A faster backend means a snappier frontend, which means happier users.
Need a tutorial with session auth
Yes please
Great suggestion!
How is speed compared to Elysia? My Elysia DX coming from express was day and night. There's no going back ...
...why most of the frontend meta Framework's name starts with N, and for the backend with E ? 🤔
Would be interesting to do a comparison with Elysia, thanks for the suggestion!
Here is a comparison with Fastify v5 that got released last week (Encore.ts is about twice as fast): encore.dev/blog/fastify-v5
Our comparison includes request type validation, that is probably why the numbers differ a lot from the numbers on elysiajs.com.
It's 3x faster than Elysia when using type validation, check out the updated benchmark article (benchmark code linked from article): encore.dev/blog/event-loops
How to build encore follow clean architecture ?
With nest.js easy to setup because core of nest.js follow dependency injection.
Encore makes it simple to separate concerns by using multiple sub-systems and services using the API framework, and it provides observability and documentation out of the box so all service-to-service calls are clearly visible thanks to both tracing and automatic architecture diagrams. It also ensures the application logic is independent of specific infrastructure services using the cloud-provider independent infrastructure declarations in the framework.
Here's an example app consisting of a few different services: github.com/encoredev/examples/tree/main/ts/uptime
As I mention in the video, Encore.ts is unopinionated when it comes to how you structure your code. You can follow the SOLID principles in your business logic if you like, Encore.ts will not stop you.
@@SimonEncore Thanks for update, So with any libary on npm, pnpm can run on Express will run correctly on Encore ?
@@minhhieple6483 No, not necessarily. As shown in the video, you can not just swap out Encore.ts for Express and most middleware created for Express will not work out of the box for Encore.ts. Is there a particular library that you are thinking about using together with Encore.ts?
What about vs Hono
Great suggestion, we'll look into producing a benchmark vs Hono :)
@@encoredev seen elysiaJS benchmark result been 5-6 times faster then yours, wonder if its true
@@vladyslavprus9387 We've not seen an Encore vs elysia benchmark published anywhere, care to share a link?
Our comparison includes request type validation, that could be why the numbers differ a lot from the numbers on elysiajs.com.
Update: Encore.ts is 3x faster than Hono with schema validation, and 70% faster without schema validation. See x.com/encoredotdev/status/1839668756878184810
But is it faster than hono?
Encore.ts is 3x faster than Hono and Elysia with schema validation enabled, and 70% faster without. See x.com/encoredotdev/status/1839668756878184810
Yes. 3x faster when using type validation, check out the updated benchmark article (benchmark code linked from article): encore.dev/blog/event-loops
Is it faster than hono.js
Update: Encore.ts is 3x faster than Hono with schema validation, and 70% faster without schema validation. See x.com/encoredotdev/status/1839668756878184810
Yes. 3x faster when using type validation, check out the updated benchmark article (benchmark code linked from article): encore.dev/blog/event-loops
Supabase compatibility so necessary for Encore
Encore is compatible with any external database, there's nothing stopping you from using whatever provider you want. Not all the built-in infra related functionality will work out of the box though.
I think comparing anything with express is pretty meh, compare it with hono speed for example
It's coming!
Encore.ts is 3x faster than Hono and Elysia with schema validation enabled, and 70% faster without. See x.com/encoredotdev/status/1839668756878184810
It's 3x faster than Hono when using type validation, check out the updated benchmark article (benchmark code linked from article): encore.dev/blog/event-loops
Well nice.. but from those numbers I think it's on par with H3 , and u know what uses H3 out of the box ? NUXT JS.
So in my case why bother splitting the code even more into another api module, when i can keep it inside the main app as a BFF (backend for frontend).
What I like though about presented Encore is the TS integration and the builtin swagger-panel. HOWEVER, let's be honest .. past the dev phase, dont' think you'll waste time analyzing the data.
At this point bragging that you made something faster than express.js , should be a standard; not a feature.
Check any other alternative. They are all at least x5 faster.
It is a fair point that most modern web frameworks will be faster than vanilla Express but Express is still by far the most used web framework for Node.js with it's 32 million weekly downloads. Also, most Node.js devs are familiar with the Express API, that is why we feel that the comparison with Encore.ts makes sense.
Encore.ts is not for everyone, if you feel like your current setup is working for you then that is great! But if you need to build a scalable, robust application with end-to-end type-safe, we believe Encore.ts is a great choice (we are a bit biased of course).
In our experience, when having a distributed system with multiple services deployed to the cloud and millions of request per day, having access to tools like metrics and tracing is crucial for quickly finding bugs and bottlenecks.
Update: Encore.ts is 3x faster than Hono and Elysia with schema validation enabled, and 70% faster without. See x.com/encoredotdev/status/1839668756878184810
If nuxt gave the possibility to make auto-documentation of api routers with type-security out of the box with H3, it would be a fairy tale, but as it is, we have to look at the possibility to raise a server separately with less effort but similar metrics.
Comparing perf with grandpa express - weak move. Try compare with elysia or hono.
We sure will. Express is by far the most commonly used framework though, so it seemed relevant to a lot of developers.
Here is a comparison with Fastify v5 that got released last week: encore.dev/blog/fastify-v5
Encore.ts is about twice as fast.
Here is a comparison with Fastify v5 that got released last week (Encore.ts is about twice as fast): encore.dev/blog/fastify-v5
Update: Encore.ts is 3x faster than Hono and Elysia with schema validation, and 70% faster without schema validation. See x.com/encoredotdev/status/1839668756878184810
We've benchmarked it now, Encore.ts is 3x faster than Elysia and Hono when using type validation: encore.dev/blog/event-loops