Get started Bring yourself up to speed with our introductory content.

Which AWS programming language is best for our project?

AWS developers can choose between a variety programming languages, including Microsoft, .NET, Java and Python. How do they differ and should we use them to develop applications?

IT teams can build applications using several AWS programming languages, including Microsoft .NET, Java, Python,...

Ruby, Node.js and PHP. These languages can be divided into two categories: statically compiled and strongly typed or dynamic and interpretive. Knowing which one is right for your AWS project means understanding the problems you need to solve as well as your project timeframe.

Statically compiled and strongly typed programming languages contain well-documented code with clean interfaces that provide compile-time errors rather than runtime errors. However, it takes longer to build software using this type of language. On the other hand, dynamic and interpretive languages simplify the development phase, including support assistance for sophisticated debugging and refactoring functionality. This ensures the delivery of high-quality code that's naturally suited for rapid AWS development projects.

When choosing an AWS programming language for your project, it's important to first identify problems with the domain and the local ecosystem. To do this, conduct research to identify what languages have solved similar types of business problems. If you're IT staff that's trained specifically for the programming language you choose or application type you're building, consider outsourcing work to a developer or third party.

The next step is to select an AWS programming language that allows for the quickest app development. Don't forget to take into account the business case and types of end users who will interact with the application. For example, if an application integrates heavily with Microsoft Office and other Windows apps, .NET might be the best choice. But if the application needs to perform functions such as weather forecasts, Python might be a good option because of its math library and ability to scale with Hadoop in the cloud.

Next Steps

Match services to programming language with AWS SDK

Understand the benefits of Node.js in development

Match the language to set up an AWS Lambda function

Dig Deeper on AWS tools for development

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

How do you decide on a cloud programming language before developing an application?
I disagree with a lot of points.
There are dynamic languages in .NET (F#, as an example).
The mainstream .NET languages and Java does have "including support assistance for sophisticated debugging and refactoring functionality.". You told a huge lie. This is a fanciful misinformation.
It is and ridiculous the point "if an application integrates heavily with Microsoft Office and other Windows apps". Totally ridiculous.
And one important thing: open-source tools are much more bug prone than supported by big companies. You can't trust your business to some open-source, only "suported by the community" code you find everywhere. I had a lot of problems with the Django framework and many Ruby tools that made me make servere changes to projects.
And if you don't know ASP.Net with C#, I recomend you to take a tour before say that it is not as productive as using dynamic languages. I agree that Java is less productive than Python, Ruby, Node etc, but C#... Take some more information...
I'm really scared by this article.
Hi Flavio, thanks for the comment. I'll start from the beginning to address your concerns. The article didn't mention that .NET doesn't have dynamic languages, I was just mentioning languages that have support for AWS SDK, but without going into details. In the second paragraph, intention wasn't to say that Java or .NET don't include support assistance for sophisticated debugging and refactoring functionality, of course they do, it was to point that dynamic languages that recently evolved such as Ruby don't suffer from lack of supporting tools. About choosing the right language for the problem, as we said, "When choosing an AWS programming language for your project, it's important to first identify problems with the domain and the local ecosystem", it's all about the platform where you will run your application, what are the business requirements and what resources you have. You can disagree with the saying that .NET is the best choice for Windows applications that integrate with Office, and I can personally agree, it's a matter of preference. As well, article never stated that the open source tools are much more bug prone than enterprise solutions. I personally don't think so, open source is all right, and good for most cases, but there is that 1% of exceptions where you need help of large software vendors, to solve your problems in high traffic multiple tiered environments. We're not saying you should go enterprise instead of open source, just do your research, measure everything and approach your future project with caution about the language, the tools, the deployment environment and future maintenance of the product as well. And I wouldn't also agree that Java is more productive than Python, look at the finance/trading/banking world :)