4 ms·

Looks great! I build something similar (vramework.dev), actually on my way now to give a talk on it Got a presentation for it at presentation.vramework.dev if

Looks great! I build something similar (vramework.dev), actually on my way now to give a talk on it Got a presentation for it at presentation.vramework.dev if anyone is interested

sramam 2y ago
vramework looks really well thought out. Is it in use by anyone yet?
- yasserf 2y ago
  Heya! It’s used in three companies so far, but the new productised (via the cli) version is still in development / qa stages There is one company that has been using it for over four years tho! Just checked in and seems to be working solid
  - yasserf 2y ago
    The difference between the two versions is that we now have a cli, whereas before you needed to call scripts to do the same things
pmdfgy 2y ago
Looks great, will have a look at it.
- yasserf 2y ago
  Thank you!
gervwyk 2y ago
interesting, when you say websocket support on aws, does this mean ws using lambda? and ws on nextjs (would be a game changer if someone made this happen)
- yasserf 2y ago
  Yes it’s ws using lambda, the worker-starter example shows how it works Also abstracts away the idea of an eventbus which is pretty critical in any Websocket deployment. It doesn’t use Websocket directly via Vercel, but would work if you use nextjs by providing it a http server and also providing that server to ws Can get this to work, but I’m pretty curious why you think this is a game changer? Thanks!
  - yasserf 2y ago
    Also curious how you would want Websocket servers to talk to each other (to broadcast messages). Would you be okay having a pub sub layer like redis that nestjs servers run on? Also is running on vercel a requirement?
  - gervwyk 2y ago
    Nice. I’m going to look into this more. We currently run a dedicated server next to our vercel apps just for ws support. Adds considerable overhead. Maybe game changer is an exaggeration but In the vercel community, ws has been a top requested feature for years. See comments on https://x.com/rauchg/status/1872729115595587627 https://x.com/rauchg/status/1872729115595587627
    - yasserf 2y ago
      I raised an issue here https://github.com/vramework/vramework/issues/119 https://github.com/vramework/vramework/issues/119, feel free to add any info that can help. Note to self: need to signup to X! If deploying off of vercel is acceptable, it can be done pretty nicely via serverless-nextjs or nextjs docker in one server. But from what I understand vercel internally does quite a bit of code analysis to split things and I don't really want to get too deep into the weeds in that direction Thank you for raising!

Looks great! I build something similar (vramework.dev), actually on my way now to give a talk on it Got a presentation for it at presentation.vramework.dev if anyone is interested

sramam 2y ago

vramework looks really well thought out. Is it in use by anyone yet?

yasserf 2y ago
Heya! It’s used in three companies so far, but the new productised (via the cli) version is still in development / qa stages There is one company that has been using it for over four years tho! Just checked in and seems to be working solid
- yasserf 2y ago
  The difference between the two versions is that we now have a cli, whereas before you needed to call scripts to do the same things

pmdfgy 2y ago

Looks great, will have a look at it.

yasserf 2y ago
Thank you!

gervwyk 2y ago

interesting, when you say websocket support on aws, does this mean ws using lambda? and ws on nextjs (would be a game changer if someone made this happen)

yasserf 2y ago
Yes it’s ws using lambda, the worker-starter example shows how it works Also abstracts away the idea of an eventbus which is pretty critical in any Websocket deployment. It doesn’t use Websocket directly via Vercel, but would work if you use nextjs by providing it a http server and also providing that server to ws Can get this to work, but I’m pretty curious why you think this is a game changer? Thanks!
- yasserf 2y ago
  Also curious how you would want Websocket servers to talk to each other (to broadcast messages). Would you be okay having a pub sub layer like redis that nestjs servers run on? Also is running on vercel a requirement?
- gervwyk 2y ago
  Nice. I’m going to look into this more. We currently run a dedicated server next to our vercel apps just for ws support. Adds considerable overhead. Maybe game changer is an exaggeration but In the vercel community, ws has been a top requested feature for years. See comments on https://x.com/rauchg/status/1872729115595587627 https://x.com/rauchg/status/1872729115595587627
  - yasserf 2y ago
    I raised an issue here https://github.com/vramework/vramework/issues/119 https://github.com/vramework/vramework/issues/119, feel free to add any info that can help. Note to self: need to signup to X! If deploying off of vercel is acceptable, it can be done pretty nicely via serverless-nextjs or nextjs docker in one server. But from what I understand vercel internally does quite a bit of code analysis to split things and I don't really want to get too deep into the weeds in that direction Thank you for raising!