As much as we like writing code and building cool solutions, our lines of code are worth nothing until they run in production. On the other hand, time spent putting things in production is time not spent on new features. An interesting dilemma, and one we can solve with what we love most: automation!
The modern history of software development is one of platformization. By abstracting complexity behind self-service APIs, we make it possible for teams and organizations to move fast – and innovate even faster. When Amazon launched their first cloud service, it was based on its internal platform. As the company went through astronomic growth, these systems were made reusable, self-service and fit for public use.
Infrastructure as Code has made it possible to consistently repeat deployments and keep track of the details in version control. AWS CDK, the Cloud Development Kit, is a native Infrastructure as Code solution by AWS that allows you to write you infrastructure definitions in normal programming languages. Deploying a collection of cloud resources with it is as simple as running cdk deploy.
Infrastructure as Code is a phrase that you might’ve heard regularly, without really understanding what it is.
In this post, we will give a short introduction on various types of Infrastructure as Code.
Imagine, after an arduous exam sitting of three hours you push that final button to submit your answers. Even if you’re a calm person, you likely feel your nerves playing up.
During AWS Re:invent 2020 Container Image support for AWS Lambda was announced, giving us a new way to deploy our code to AWS Lambda.
Data-Oriented Programming is a new programming paradigm which simplifies the design of software where information has the focus. Instead of creating classes/entities with code works on the instantiated objects, DOP encourages to separate code from data.
In Cloud development we have become accustomed to using the infrastructure-as-code (IaC) principle to define infrastructure and related configuration together with CI/CD pipelines to deploy the infrastructure to our favorite Public Cloud environment.
Serverless development is more popular than ever. No servers to maintain, out-of-the-box scalability and pay-as-you-go pricing make it an attractive platform for developers, but these advantages come with a unique set of challenges.
Vanaf Java 9 is er een modulair systeem geintroduceerd om met packages om te gaan. In feite is een module een groep packages die verband houden met elkaar. Bij de release van java 9 kwam tevens de tool jlink. Jlink is een tool die een aangepaste Java-runtime-image genereert die alleen de platform modules bevat die vereist zijn voor een bepaalde toepassing.