# AWS's Lambda Layers allows custom runtimes, lambdas for any language

**URL:** <https://discourse.elm-lang.org/t/awss-lambda-layers-allows-custom-runtimes-lambdas-for-any-language/2692>\
**Category:** Show and Tell\
**Created:** [December 4, 2018, 2:20pm UTC](https://discourse.elm-lang.org/t/awss-lambda-layers-allows-custom-runtimes-lambdas-for-any-language/2692 "2018-12-04T14:20:06Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![choonkeat](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/choonkeat/32/1555_2.png) [@choonkeat](https://discourse.elm-lang.org/u/choonkeat)\
**Post date:** [December 5, 2018, 4:41pm UTC](https://discourse.elm-lang.org/t/awss-lambda-layers-allows-custom-runtimes-lambdas-for-any-language/2692/5 "2018-12-05T16:41:23Z")

</div>

> [@charliek](#):
>
> what the Elm community thinks

Since there’s currently “no ecosystem or api design for serverside stuff” to speak of, I think it might be quite equalising for elm to start her backend journey from constrained environment like aws lambda or even cloudflare workers [than starting in more general server environments]

I’m experimenting with elm on “server side” and I’m liking how elm can make “http routes” handling much better than standard url/middleware approaches; looking forward to more discoveries in this space.

The [lack of parallel Task execution](https://discourse.elm-lang.org/t/task-map2-and-independent-asynchronous-operations/2471/4) does mean an elm version of the [canonical “google search”](https://youtu.be/f6kdp27TYZs?t=1723) be slow, albeit concurrent.

---

_[View the full topic](https://discourse.elm-lang.org/t/awss-lambda-layers-allows-custom-runtimes-lambdas-for-any-language/2692)._