hahaha cheers man

yeah just like you mention, i also wonder if hono/CF workers will actually take half as long, or just within ±10ms compared to Vercel Edge network i haven't tested this on a large scale with more complex API calls, curious what y'all think about this

in my tests (production environment) I got about a ~30% consistent speed difference for db interactions in both API routes. Decided to leave it out cause that part was just boring, probably wouldve been a good idea to at least include the results. Fair point, appreciate ya

Can you tell how to access env vars in hono? Outside ant .get methods?

​​@@yourlinuxguyyou can't access env variables in top level of your module. If you want to use any library that requires env variables. You should use hono's vars middleware if you are using hono. Like this: const app = new Hono(); app.use(async (c, next) => { c.set("myDb", new DB(c.env.MY_ENV)); await next(); }); app.get("/", (c) => { const db = c.get("myDb"); return c.json({...}); });

​@@yourlinuxguyif you find out ,let me know

@@rishabhpandey6335 you can't access .env outside the .get methods

honestly no idea, I'd like to know as well

I guess that might be vercel overhead like: logging, analytics, routing, reading config, etc. But I'm not totally sure.

@@joshtriedcoding vercel has a ton of logging and middleware and other built in utilities that it needs to step through is my presumption.

interesting, I wonder if the regional edge thing could be the reason for the difference or if its also the vercel tracking, logging etc. Cheers man!

true. it might be the deployment region or the proprietary layers of logging and tracking. Cheers back!@@joshtriedcoding

I am waiting for their latest offering, the ultra pro edge, where the code to be executed will be even closer than the edge, it will be on the users device.😎

standard AWS feature

? not its not wdym@@adamconrad5249

This was released yesterday bruh

@@tvnishq lol

Elysia ❤

both are kinda goated

if its static you can port it to pretty much anywere, even if not most places support next builds out of the box like railway, amplify or netlify

hi! Technically you can reuse the APIs, practically you'd normally use a separate backend. At my last job we used fastify as the backend that our iOS, android and web apps could all access and it worked great

@@joshtriedcoding Thank you for the insight 🙌

10ms cpu time is not low. Its more than enough. But i dont think you can run pdf generations on cf workers.

@@twitchizle thank you mate, definitely will give it a try and compare between workers and AWS lambdas

The channel is called Josh tried coding, not that he succeeded.

It's called automatic semicolon insertion. Very few people learn about it, so it ends up being confusing. It is nothing more than a toxic flex, don't use it.

Because what for?

might be a problem with the pages vs app router, if you have both at the same time (hono initialized with pages by default, I switched to app manually), this can happen

@@joshtriedcodingi use app router only and never done pages router

Per the hono docs, move /app/[[...route]] to /app/api/[[...route]]. That fixed it for me

I prefer Elysia, but Elysia has some "Bun only" stuff, that doesn't work on Workers.

That was my first thought because thats where Ive been hosting mine.

i just rotate passwords or delete databases before uploading

From my understanding, it’s telling typescript “I need to export this file, but I should never use/import it anywhere else”

bro can you elaborate more on this !!!!....

@@farjulmallik4135 He is calling the function that establishes the connection inside the route handler which means a connection is being established on every request made to the route handler, this was mainly due to not being able to access the environment variable and not a runtime limitation, but this emulates what PHP does where it is completely stateless and the concept of database connection pooling or long lived connections do not exist because on every request php restarts its process. Most backends nowadays have connection pools to alleviate the issue of connection reestablishment. Not having pools or not having a long lived connection may not be the main concern of users of such a system, but there is a stark difference in terms of database IO performance between backends using a connection pool/long lived connection and those which do not.

yep, so now it's JS turn to solve those issues again :)

Pgbouncer

My guess would be more familiar API (feels like express)+ they add some interesting features

h3 and nitro are both great to work with

Immediately noticed "eventHandler" bloat. Otherwise looks identical.

Looks like express

What is wrong with using Next.js as a backend framework? Isn't it nice that you can stay in the same language and framework and have it deployed the same way?

​@@JakobTheCoder i think op is joking

@@JakobTheCoder If you are frontend developer, and only use it to connect to a single frontend. If you want to do more with your backend, Next.js is not a good choice. It is a backend for frontend, not a backend to create a generic API. Also if you want to build more workers / microservices, or want more freedom and not have vendor locking, Next.js is not what you want. So Next.js is great as frontend developer, and only for a single frontend with a single backend.

​@@JakobTheCoder yes, great for small-medium size applications, but JavaScript's performance is not enough for large/perf centric applications. This is where C#, Java, Rust, and other languages shines!!

@@sanampakuwal There are good points to make for and against using JS / C# etc. on the backend, this is a great discussion

Hosted at a CDN edge location. Closer to the user, so lower latency.

Use Drizzle instead

yes, there is trpc middleware for Hono

You can make anything with with trpc

for sure man

That's because you don't use Drizzle