atul-jalan

14 ms·

1.
AI Coding for Lazy Developers(composehq.com)
2 points by atul-jalan 1y ago|0 comments
2.
by atul-jalan 1y ago
Looks interesting. Don't see any info on pricing though?
3.
by atul-jalan 1y ago
Hey HN! I’m Atul, and today I’m super excited to open-source Compose: a server-side SDK for building internal tools faster, without leaving your codebase. I first showed Compose to HN about 6 months ago ( https://news.ycombinator.
4.
Show HN: Compose – Build internal tools faster, without leaving your codebase(github.com)
3 points by atul-jalan 1y ago|1 comments
5.
by atul-jalan 2y ago
It does, but it will generally give a grace period for outstanding requests to resolve prior to killing the service. It's a good idea for short-lived HTTP requests, but will cause problems for a persistent connection.
6.
by atul-jalan 2y ago
How would you make it simpler?
7.
by atul-jalan 2y ago
The initial handshake will usually include an `Upgrade: websocket` header, which can be inspected by networks.
8.
by atul-jalan 2y ago
Yep, for our application, we have an `executionId` that is sent in essentially every single WebSocket message. But client and server use it to maintain a record of events.
9.
by atul-jalan 2y ago
I think there is a way to do it, but it likely involves custom headers on the initial connection that the load balancer can read to route to the correct origin server. I imagine the way it might go is that the client would first send an HTT
10.
by atul-jalan 2y ago
Node has similar libraries like Socket.IO too, but it over-abstracts it a bit in my opinion.
11.
The hidden complexity of scaling WebSockets(composehq.com)
194 points by atul-jalan 2y ago|68 comments
12.
Show HN: Compose – Build internal tools with just back end code(composehq.com)
3 points by atul-jalan 2y ago|0 comments