Choosing a runtime language is quite tricky when we start designing a serverless application. But we can always seek comfort in our skills sets when we decide on the runtime language. But the runtime language also determines the performance of our application. For example, if we use Java or .NET (the compiled language) as our runtime language, then this incurs the largest initial startup cost for a container's first invocation, but the performance will improve for subsequent invocations. Interpreted languages, such as Node.js or Python, have very fast initial invocation times compared to compiled languages, but they cannot output the maximum performance compared to complied languages. So if the application is latency sensitive or very spiky, then it is recommended that you use an interpreted language, and if the application does not experience large peaks or valleys within its traffic, or if user experience is not blocked with the lambda functions response time, then we can choose any language as the runtime language.