In this post, l explain how we used Visual Studio Code’s Development Container feature as a stepping stone in our long-term effort to achieve Collaborative Infrastructure as Code. This one step in the process gave a versioned, repeatable working environment and allowed us time to determine the next steps in the effort to achieve IaC.
Many IT budgets are consumed by maintaining existing applications and resources, and getting out from under the weight of these existing applications can be daunting—schedule is king, and making time to address modernization comes at the expense of current business needs. However, as the business world moves into the digital space to prepare to meet the next generation of customers and to compete globally, organizations can’t manage their applications in the same way as they have in the past—they must take them to the next level.
Cloud technologies provide many of the building blocks to help businesses achieve these goals and prepare themselves for the future. This white paper is a solution-agnostic resource to help you understand enterprise cloud modernization and migration and to help you decide which strategy is right for your business. Are your applications ready for the new tomorrow?
The last few years have seen a lot of movement to bring applications that don’t require manual intervention from the mainframe to Unix, Linux, Windows servers, or even to the desktop. This concept is commonly known as batch programming, and Spring Batch has been the tool many of us are using to accomplish this. Another trend that is gaining steam is to move from an internally-hosted server to a cloud-hosted system.
In this post, we discuss multiple ways for transferring Spring Batch applications up to the AWS Cloud, including EC2, Docker, Lambda, and others. I concentrate on AWS in this post, but, from my experience in Google Cloud, the same ideas will apply…
AWS SQS (Simple Queue Service) can provide developers with flexibility and scalability when building microservice application(s). In this quick start tutorial, we will demonstrate how to configure a FIFO queue for a fictional online marketplace.
What Is A FIFO Queue?
A FIFO (first in, first out) queue is used when the order of items or events is critical, or where duplicates items in the queue are not permitted. For example:
– Prevent a user from buying an item that isn’t available on a marketplace.
I’m a big fan of Amplify. I’m also a big fan of TypeScript. Amplify is not built with TypeScript, and to use it effectively, sometimes you need to give it a little help, especially when it comes to GraphQL. With the advent of hooks, we can create some nice utilities for ourselves that let us leverage the power of TypeScript with our GraphQL queries. Let’s see what that looks like.
I’ll be assuming familiarity with React and TypeScript, i…
Originally posted by Mat Warger on mw.codes April 19, 2019.