The difficult part about structuring a Terraform project is that several solutions exist and there is no universal guide. The code structure would highly depend on the size of the project, complexity, the number of environments, how often the infrastructure changes, etc... For simple projects which contain just a few

In this article, I will continue the discussion from this [https://blog.softup.co/p/033f4766-780c-45b1-b448-40cc68c3f7a8/] section and present one way how we can automate our infrastructure and application deployments using Terraform Cloud and GitHub Actions. As it was mentioned in the other article, we will suppose that our system

One of the biggest misconceptions when it comes to Node is that every asynchronous operation is handled by Libuv’s thread pool. There are numerous articles and diagrams online which tend to explain Node’s runtime architecture and most of them show a standard Reactor pattern, where all the heavy

In this part, we will go through some Node.js code snippets to see how the event loop behaves and how it affects code execution. But first, let’s recap how the event loop actually works by using a diagram from this [https://www.youtube.com/watch?v=PNa9OMajw9w] talk

Introduction During Node’s original presentation [https://www.youtube.com/watch?v=ztspvPYybIY] in 2009, Ryan Dahl’s (i.e. creator of Node) thesis was: “I/O needs to be done differently”. At the beginning of the talk, he gives a simple example of a program that does a database

Node.js is an open-source and cross-platform JavaScript runtime environment for executing Javascript outside the browser. It is backed by Google’s V8 engine, which makes it extremely performant. An asynchronous event-driven runtime One of the most common statements that we encounter when we are introduced to Node is that