Ray
@xbeco.bsky.social
Platform Engineer who take care of some Lambda on production
YAML should be dumped into trash bin.
900+ Lambda
100M ish invocation per day
YAML should be dumped into trash bin.
900+ Lambda
100M ish invocation per day
Not just u.
All our ci/cd are impacted
All our ci/cd are impacted
February 6, 2025 at 8:56 AM
Not just u.
All our ci/cd are impacted
All our ci/cd are impacted
Events driven on K8S or(Lambda on K8S) is more close to BEAM actor pattern.
Each container is only triggered by event (HTTP/SQS/Kafka, etc)
Similar with each gen_server get a message. For K8S, it’s not related to any language.
Each container is only triggered by event (HTTP/SQS/Kafka, etc)
Similar with each gen_server get a message. For K8S, it’s not related to any language.
November 11, 2024 at 11:14 PM
Events driven on K8S or(Lambda on K8S) is more close to BEAM actor pattern.
Each container is only triggered by event (HTTP/SQS/Kafka, etc)
Similar with each gen_server get a message. For K8S, it’s not related to any language.
Each container is only triggered by event (HTTP/SQS/Kafka, etc)
Similar with each gen_server get a message. For K8S, it’s not related to any language.
Erlang Community had a research to support partial cluster network or p2p style network. The big cluster problem is all the Beam nodes are connecting to each fully. Just keeping all hundreds nodes to ping each others to keep alive create a ton of loads on network and node itself.
November 11, 2024 at 11:10 PM
Erlang Community had a research to support partial cluster network or p2p style network. The big cluster problem is all the Beam nodes are connecting to each fully. Just keeping all hundreds nodes to ping each others to keep alive create a ton of loads on network and node itself.