Many enterprises today have a range of assets residing in a mixture of both public and private clouds. As a result, there is a need to connect not just site-to-cloud but also cloud-to-cloud - use cases we would term Data Centre Interconnection (DCI) and Cloud Interconnection.

We can plausibly say the enterprise development market turned the tide on cloud-native development in 2020, as most net-new software and serious overhaul projects started moving toward microservices architectures, with Kubernetes as the preferred platform.

Let’s face it. Once you have consumed your free credit, AWS costs an arm and a leg. This is the price to pay for high-quality services. But how can you reduce your costs without sacrificing quality? This post will show you how to reduce your bill by up to 60% by combining four built-in features in Qovery. There are three categories of costs on AWS. The “data transfer”, the “compute”, and the “storage” costs.

In this article, we’ll be rewinding back to the very beginning of the AWS Well-Architected Framework to understand how and why it came to be, and why is it of utmost importance, but very often underrated, for serverless developers to learn, understand and apply this framework of best-practices. We’ll also be looking into how the framework has evolved and how it should be used in 2021.

Technical debt is an important — but often unclear — concept for engineering teams. In software development, technical debt, also called code debt or tech debt, is defined as the cost of refactoring a piece of code or system to keep it working efficiently. It can be caused by outdated architecture, a change in requirements, or the result of choosing an easier solution instead of a better, but more difficult one.

Moving to the cloud brings benefits such as reduced infrastructure costs, increased scalability, and added redundancy. As your company takes advantage of the cloud, you may follow the trend to automate both the creation and destruction of cloud resources.

We're excited to share some updates on what we've been working on at Taloflow. We've come a long way since we launched Tim - AWS cost management for developers, which was a finalist for Product Hunt Dev Tool of the Year. Since launch, we've had the opportunity to work with nearly 100 companies and developers. We've helped digital native companies like NS1, Bluecore and Modusbox save money, improve performance, and get a better grasp of their marginal costs on the cloud.

In this blog in the “IT security under attack” series, we wanted to shed some light on an unfamiliar and seldom discussed topic in IT security: the default, out-of-the-box configurations in IT environments that may be putting your network and users at risk. Default settings, and why the initial configuration is not the most secure.

Cloud migration is, more often than not, treated as a one-way street where organizations migrate applications and workloads from on-premises to a public cloud, or less often, from one public cloud to another. But a key finding in our recent State of Hybrid Cloud survey of 350 IT professionals with cloud decision influence/authority is that a whopping 72% of participating organizations stated that they’ve had to move applications back on-premises after migrating them to the public cloud.