3 ms·
Lack of support for proper sockets is a real bummer. If binaries can't be used or talk to the app the applications are quite limited.
by akhatri_aus 11y ago
Lack of support for proper sockets is a real bummer.
If binaries can't be used or talk to the app the applications are quite limited.
- SomeStupidPoint 11y agoI guess I'm not understanding why you'd use lambda that way instead of just using container instances -- what would be the point?
- akhatri_aus 11y agoThere are tasks to be done that require binaries. Typically 1 second tasks. This binary needs to interact with Java or NodeJS so it uses sockets [creates a server and nodejs connects to it to tell it what to do] for the request. A container seems silly since its a sub 1 second task
- siscia 11y agoCan you elaborate ? You want socket just to bring down latency ? You want different client to connect to the same environment so that you can keep a local state of your application ? I am thinking about a videogame or a collaborative office tool. You simply want to send binary data to a function ?
- akhatri_aus 11y agoLambda is great for doing lots of tasks in bulk. Say I have a binary that is able to process data quickly. On a lambda request nodejs instructs a binary on what to do using a socket. Meaning it binds to a local port and interacts with the binary getting and receiving instructions until the task is complete. In all sub 1 second. Lambda doesn't allow sockets so its uses are very limited. Binaries also cut down the time it takes to do a task and allow a greater variety of things to be done.
- siscia 11y agoWouldn't be simple to ask Lambda to allow binary execution ? Then you could just pass the input as base64, or whatever other encoding system you please...