Software Engineering Blog
Are you tired of manually managing Terraform infrastructure code changes and collaborating with team members? Look no further than Atlantis! This open-source tool can help you automate your workflow and make managing Terraform code changes a breeze.
What is Atlantis? Atlantis is a tool that automates the workflow for collaborating on Terraform infrastructure code. It integrates with version control systems like GitHub, GitLab, and Bitbucket to provide a streamlined workflow for managing changes to infrastructure code.
You might have noticed some mysterious files with a .un~ extension showing up in your project directories. These files are created by Vim, a popular text editor used by many programmers, and can sometimes cause confusion or clutter in your file system. In this article, we’ll explain what these files are, why Vim creates them, and how you can manage them to keep your projects organized.
What are .un~ files? When you edit a file in Vim, the editor creates a backup file with the same name as the original file and a tilde (~) character at the end, by default.
You know that managing multiple versions of Terraform can be a real pain. Manually installing and uninstalling different versions of Terraform to match different projects can take up precious time and brainpower. Fortunately, there’s a solution: Terraform Switcher.
Installation with brew For Mac users who have Homebrew installed, getting started with Terraform Switcher is easy as pie. Just enter the following command into your terminal:
brew install warrensbox/tap/tfswitch How Terraform Switcher can be useful Let’s say you’re a software engineer working on two different projects.
If you’re a software engineer working with Kubernetes, chances are you’ve heard of Helm. But if you’re not already using it, you might be missing out on one of the most powerful tools for managing your Kubernetes deployments.
So, what exactly is Helm, and why should you care?
In short, Helm is a package manager for Kubernetes, designed to make it easier to manage and deploy complex applications on a Kubernetes cluster.
In the world of software engineering, databases play a critical role in storing and retrieving information. Whether you’re developing a web application, a mobile app, or any software that requires data management, it’s important to ensure that your database transactions are safe, reliable and consistent. This is where ACID comes in.
ACID is an acronym that stands for Atomicity, Consistency, Isolation, and Durability. These four principles are the foundation of transaction processing in databases, and they ensure that database transactions are executed reliably, even in the face of failures or errors.
As a software engineer working with databases, you may have heard of Write-Ahead Logging (WAL) and its importance in ensuring data integrity and recovery. In this article, we’ll take a closer look at WAL, its benefits, and how it works in database systems.
An Overview of Write-Ahead Logging Write-Ahead Logging (WAL) is a technique used in database systems to ensure that changes to the database are first written to a log file before being written to the database file itself.