https://fulgurion.com/blog/tags/architecture/Recent content in Architecture on Fulgurion Systems Bloghttps://fulgurion.com/blog/images/Logo-linkedin.pnghttps://fulgurion.com/blog/images/Logo-linkedin.pngHugoen-usFri, 24 Apr 2026 00:00:00 -0300https://fulgurion.com/blog/posts/rust-on-aws-lambda-wrong-tool/Fri, 24 Apr 2026 00:00:00 -0300https://fulgurion.com/blog/posts/rust-on-aws-lambda-wrong-tool/<p>In <a href="https://fulgurion.com/blog/posts/rust-on-aws-lambda/">Part 1</a>, <a href="https://fulgurion.com/blog/posts/rust-on-aws-lambda-cold-start/">Part 2</a>, and <a href="https://fulgurion.com/blog/posts/rust-on-aws-lambda-cold-start-anatomy/">Part 3</a> I argued for Rust on Lambda and measured where the gains come from. This post draws the other edge of that fence: the shapes of work where Lambda is the wrong architectural choice, however lean the binary, and whichever language you wrote it in. The common thread across every case below is a single billing fact: <strong>Lambda charges you for wall-clock duration, including the time your handler spends waiting on IO.</strong></p>