AWS Lambda With NestJS

Greg Emerick Articles, AWS, Cloud, Development Technologies & Tools, JavaScript, Node.js 7 Comments

In my previous blog post, I showed running a Spring Boot Java application in AWS Lambda. I discussed the pros and cons of using Java and Spring with Lambda. In this blog post, I’ll cover another Lambda option with NestJS. NestJS provides a framework that is not too different from a typical Spring application. It also addresses some of the negatives of using Java and Spring in a Lambda function.

To recap, AWS Lambda provides low cost compute with zero maintenance. Lambda runs your code on demand, without provisioned and managed servers. Lambda automatically runs and scales your code. You are charged for every 100ms your code executes and the number of times your code is triggered. Lambda has clear cost and maintenance benefits over typical on-premise or EC2 deployments. What does it take to run a Nest application as a Lambda? Does NestJS provide benefits over a Java Spring application?

Building a Node.js Service with AWS Lambda, DynamoDB, and Serverless Framework

Matthew Brown Articles, AWS, Cloud, JavaScript, Node.js, Tutorial 3 Comments

My favorite new technology as a developer is serverless computing. The convenience and cost make it a very compelling choice for running options in the cloud. Especially for proof of concepts or quick ways to prove out ideas. Using serverless computing to get up and running takes very little effort and the costs of running an application in the cloud are minimal. Serverless really empowers developers to act on ideas as quickly as possible.

In this post, I’m going to briefly touch on what serverless computing is and the pros and cons of using it. Then I will build a Node.js service to do CRUD operations using AWS Lambda, DynamoDB, and the Serverless Framework. You can view the finished product on Github.

AWS Lambda with Spring Boot

Greg Emerick Articles, AWS, Cloud, Development Technologies & Tools, Java, Spring, Spring Boot 12 Comments

The typical deployment scenario for a Spring Boot application in AWS involves running the Java application on an EC2 instance 24 hours a day. Of course, the application could be deployed in AWS ECS as a Docker container, but it still runs continuously on an EC2 instance. In each case, the EC2 instances need to be monitored and you pay for compute capacity used by that EC2 instance.

AWS Lambda provides low cost compute with zero maintenance. Lambda runs your code on demand, without provisioned and managed servers. Lambda automatically runs and scales your code. You are charged for every 100ms your code executes and the number of times your code is triggered. If the code isn’t running, you pay nothing.

Lambda has clear cost and maintenance benefits. But what does it take to run the standard Spring Boot application as a Lambda? How does it work? What are the drawbacks? These are the questions that will be answered in this blog through a tangible example…

AWS AppSync with Lambda Data Sources

Mat Warger API Development, Articles, AWS, Cloud, Development Technologies & Tools, GraphQL, JavaScript, Tutorial Leave a Comment

The power of GraphQL lies in its flexibility. That is especially the case regarding resolvers, where any local or remote data can be used to fulfill a GraphQL query or mutation.

In this post, I’m going to demo a quick example of what this looks like, and a couple gotchas that were apparent in working with Lambdas as a data source for AppSync. Let’s gooooo!

Application Rewrite

Modernization: ReactJS, Python, AWS, & GraphQL

Shaylee Webb Application Rewrite, Cloud, Modernization, React

A team of Keyhole Consultants was brought in to help a client in the healthcare insurance space with a rewrite of their existing, proprietary application used to manage workers’ compensation claims. The Keyhole team worked with the client’s development team to shift the application from dated technologies to more modern, efficient tools and frameworks. The technical assistance, guidance, and team …