Choosing Between Effect-RPC and Hono+Effect for a New Project and DI Tips
Hi, Help me choose: Effect-RPC vs Hono+Effect for new project (and DI tips!)
Hey Effect folks!
I've been playing with Effect and Effect Schema lately, and honestly, I'm hooked! I'm about to kick off a new passion project and I'm super excited to use Effect, Svelte, and TanStack Query.
My backend dilemma: I've built a few (around 4) projects with Hono and like it, so my initial thought was Hono + Effect. But then I saw @effect/rpc! I'm trying to figure out what @effect/rpc really offers over just using Effect inside Hono. For my kind of project, they seem like they could do similar things, so what would I gain by switching to @effect/rpc?
And if I stick with Hono + Effect, I've got that classic DI question. Effect's dependency injection is amazing, right? But Hono has its ctx too. How do you all usually make these two play nicely together? and to add to that i was going to use that DI in frontend too Sense they are services that will be in backend with slight diff compared to the frontend but more or less same Utility is required in both, I'm worried about things getting messy or confusing when deciding which "context" or DI system to use for different parts of the request. Any tips on how people decide?
Thanks so much for any comments and help! And seriously, thank you for making TypeScript so much safer!
Hey Effect folks!
I've been playing with Effect and Effect Schema lately, and honestly, I'm hooked! I'm about to kick off a new passion project and I'm super excited to use Effect, Svelte, and TanStack Query.
My backend dilemma: I've built a few (around 4) projects with Hono and like it, so my initial thought was Hono + Effect. But then I saw @effect/rpc! I'm trying to figure out what @effect/rpc really offers over just using Effect inside Hono. For my kind of project, they seem like they could do similar things, so what would I gain by switching to @effect/rpc?
And if I stick with Hono + Effect, I've got that classic DI question. Effect's dependency injection is amazing, right? But Hono has its ctx too. How do you all usually make these two play nicely together? and to add to that i was going to use that DI in frontend too Sense they are services that will be in backend with slight diff compared to the frontend but more or less same Utility is required in both, I'm worried about things getting messy or confusing when deciding which "context" or DI system to use for different parts of the request. Any tips on how people decide?
Thanks so much for any comments and help! And seriously, thank you for making TypeScript so much safer!
Similar Threads
Was this page helpful?
