Initially, Lambda only supported callbacks with Javascript handlers. Back then in 2014 it was the common way to handle asynchronicity as async/await was nowhere near as mainstream as it is today. Moreover, the SDK functions also used callbacks so it fits into the trend.

In the first article, we’ve covered how async/await helps with async commands but it offers little help when it comes to asynchronously processing collections. In this post, we’ll look into the some and the every functions that are used for a more efficient reduce when the result is a boolean value.

Bash scripts are infamous for their maintainability, but with pipes and small functions, the result can be terse, readable code. And it’s not only code quality: writing concurrent applications is a hard task, but it’s easy to achieve in Bash by relying on this mechanism. jq — a tool to query and manipulate JSON — fits nicely into this world.

In the first article, we’ve covered how async/await helps with async commands but it offers little help when it comes to asynchronously processing collections. In this post, we’ll look into the filter function, that has probably the most unintuitive way to support async functions.