Serverless Development with Kotlin, AWS Lambda, and MongoDB Atlas

As seen in a previous tutorial, creating a serverless function for AWS Lambda with Java and MongoDB isn’t too complicated of a task. In fact, you can get it done with around 35 lines of code!

However, maybe your stack doesn’t consist of Java, but instead Kotlin. What needs to be done to use Kotlin for AWS Lambda and MongoDB development? The good news is not much will be different!

In this tutorial, we’ll see how to create a simple AWS Lambda function. It will use Kotlin as the programming language and it will use the MongoDB Kotlin driver for interacting with MongoDB.

Serverless Development with AWS Lambda and MongoDB Atlas Using Java

So you need to build an application that will scale with demand and a database to scale with it? It might make sense to explore serverless functions, like those offered by AWS Lambda, and a cloud database like MongoDB Atlas.

Serverless functions are great because you can implement very specific logic in the form of a function and the infrastructure will scale automatically to meet the demand of your users. This will spare you from having to spend potentially large amounts of money on always on, but not always needed, infrastructure. Pair this with an elastically scalable database like MongoDB Atlas, and you’ve got an amazing thing in the works.

In this tutorial, we’re going to explore how to create a serverless function with AWS Lambda and MongoDB, but we’re going to focus on using Java, one of the available AWS Lambda runtimes.

Delivering a Near Real-Time Single View into Operations with a Federated Database

So the data within your organization spans across multiple databases, database platforms, and even storage types, but you need to bring it together and make sense of the data that’s dispersed. This is referred to as a Single View application and it is a common need for many organizations, so you’re not alone!

With MongoDB Data Federation, you can seamlessly query, transform, and aggregate your data from one or more locations, such as within a MongoDB database, AWS S3 buckets, and even HTTP API endpoints. In other words, with Data Federation, you can use the MongoDB Query API to work with your data even if it doesn’t exist within MongoDB.

What’s a scenario where this might make sense?

Let’s say you’re in the automotive or supply chain industries. You have customer data that might exist within MongoDB, but your parts vendors run their own businesses external to yours. However, there’s a need to pair the parts data with transactions for any particular customer. In this scenario, you might want to be able to create queries or views that bring each of these pieces together.

In this tutorial, we’re going to see how quick and easy it is to work with MongoDB Data Federation to create custom views that might aid your sales and marketing teams.

Local Development with the MongoDB Atlas CLI and Docker

Need a consistent development and deployment experience as developers work across teams and use different machines for their daily tasks? That is where Docker has you covered with containers. A common experience might include running a local version of MongoDB Community in a container and an application in another container. This strategy works for some organizations, but what if you want to leverage all the benefits that come with MongoDB Atlas in addition to a container strategy for your application development?

In this tutorial we’ll see how to create a MongoDB-compatible web application, bundle it into a container with Docker, and manage creation as well as destruction for MongoDB Atlas with the Atlas CLI during container deployment.

Getting Started with MongoDB Atlas and Azure Functions using .NET and C#

So you need to build an application with minimal operating costs that can also scale to meet the growing demand of your business. This is a perfect scenario for a serverless function, like those built with Azure Functions. With serverless functions you can focus more on the application and less on the infrastructure and operations side of things. However, what happens when you need to include a database in the mix?

In this tutorial we’ll explore how to create a serverless function with Azure Functions and the .NET runtime to interact with MongoDB Atlas. If you’re not familiar with MongoDB, it offers a flexible data model that can be used for a variety of use cases while being integrated into most application development stacks with ease. Scaling your MongoDB database and Azure Functions to meet demand is easy, making them a perfect match.

Interact with MongoDB in an AWS Lambda Function Using Go

If you’re a Go developer and you’re looking to go serverless, AWS Lambda is a solid choice that will get you up and running in no time. But what happens when you need to connect to your database? With serverless functions, also known as functions as a service (FaaS), you can never be sure about the uptime of your function or how it has chosen to scale automatically with demand. For this reason, concurrent connections to your database, which aren’t infinite, happen a little differently. In other words, we want to be efficient in how connections and interactions to the database are made.

In this tutorial we’ll see how to create a serverless function using the Go programming language and that function will connect to and query MongoDB Atlas in an efficient manner.

Listen for SIGINT and SIGTERM Events in a ZX Script

Have you ever needed to handle signal events within your ZX script? For example, what happens if you need to handle a graceful shutdown of your long-running or infinite-running script? Or what happens when the user forcefully stops the script?

These signal events are typically “SIGTERM”, “SIGINT”, and similar events. When using a script language like Bash, these events are most commonly captured with trap commands, but what happens when we’re using ZX?

In this tutorial we’ll explore how to use simple JavaScript to capture signal events in a modern ZX script.