Home→Search ResultsOrchestration Big Ideas Kubernetes, OpenShift, and Cloud FoundryThis video discusses platform orchestration from a broad scope. Specifically, Principal Consultant Jaime Niswonger takes a technology-agnostic look at the “big ideas” integral to platform orchestration for the enterprise. He introduces three popular orchestration platforms, Kubernetes, OpenShift, and Cloud Foundry, and discusses scaling container deployments in the enterprise. RecordingThis one-hour video was …
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?
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.
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!
Client Snapshot: Privately controlled and independent investment management firm. A cross-functional team of Keyhole Software consultants assisted a long-term client of Keyhole Software on various, concurrent initiatives. Primary efforts included Java / Spring Boot microservices and React applications. A selection of tasks completed follows: The team of Keyhole consultants helped support the client’s efforts to migrate its legacy applications into …