# Julia gets mentioned in an article about FORTRAN

**URL:** <https://discourse.julialang.org/t/julia-gets-mentioned-in-an-article-about-fortran/60605>\
**Category:** Community\
**Created:** [May 5, 2021, 8:52pm UTC](https://discourse.julialang.org/t/julia-gets-mentioned-in-an-article-about-fortran/60605 "2021-05-05T20:52:36Z")\
**Posts on this page:** 1\
**Showing post:** 81

<div class="post-metadata">

**Author:** ![johnh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/johnh/32/3615_2.png) [@johnh](https://discourse.julialang.org/u/johnh)\
**Post date:** [May 9, 2021, 1:55am UTC](https://discourse.julialang.org/t/julia-gets-mentioned-in-an-article-about-fortran/60605/81 "2021-05-09T01:55:11Z")

</div>

@dcgrigsby please look at this thread. The limits on lambda have changed. The report here is that the Julia image size is around 500mb

> [@\[ANN\] AWS Lambda Julia runtime](https://discourse.julialang.org/t/ann-aws-lambda-julia-runtime/59023):
>
> Hello all, I’ve seen the question of using Julia in AWS Lambda come up a few times in the past, but as far as I can see without any definite solution. AWS have built out their Lambda container functionality a bit since then, so I’ve tried to simplify the process of creating Julia docker containers - for use in AWS Lambda - here: Users can fill in entires in a short-ish config file, write their code into a function.jl file, then use bash scripts to create a local image, test that image, and th…

---

_[View the full topic](https://discourse.julialang.org/t/julia-gets-mentioned-in-an-article-about-fortran/60605)._