Log levels described as sh*t hitting the fan
Log Level Description DEBUG poop contains corn TRACE poop currently moving into colon WARN sh*t is approaching the fan ERROR sh*t has hit the »
For every request, IronFunctions would spin up a new container to handle the job, which depending on container and task could add a couple of 100ms »
Again if you missed it, IronFunctions is open-source, lambda compatible, on-premise, language agnostic, server-less compute service. While AWS Lambda only supports Java, Python and Node.js, »
As mentioned in my previous blog post there is new open-source, lambda compatible, on-premise, language agnostic, server-less compute service called IronFunctions. While IronFunctions is written in »
Imagine AWS Lambda being: On-Premise (host it anywhere) Language Agnostic (writing lambda functions in any language: Go, Rust, Python, Scala, Elixir you name it...) Horizontally Scalable »
Log Level Description DEBUG poop contains corn TRACE poop currently moving into colon WARN sh*t is approaching the fan ERROR sh*t has hit the »