I recently spoke on a panel discussion with the Securities Technology Analysis Center (STAC) on the use of infrastructure as a competitive advantage. The event offered fresh thinking on what it takes to manage high-frequency, low-latency trading environments - so I wanted to share some best practices for organization, monitoring, and how to make insights operational.
During World War II, a mathematician named Abraham Wald worked on a problem – identifying where to add armor to planes based on the aircraft that returned from missions and their bullet puncture patterns. The obvious and accepted thought was that the bullets represented the problem areas for the planes. Wald pointed out that the problem areas weren’t actually these areas, because these planes survived.
In the previous blog in this series, we discussed the principle of least privilege, and the importance of assigning bare minimum privileges to users and systems at database or server levels. However, there are certain built-in principals in your database that possess all permissions in SQL Server. If an attacker managed to get hold of one of these principals, the database could be easily exploited and damaged.
Browser (or UI) tests are a key part of end-to-end (E2E) testing. They are critical for monitoring key application workflows—such as creating a new account or adding items to a cart—and ensuring that customers using your application don’t run into broken functionalities. But browser tests can be difficult to create and maintain. They take time to implement, and configurations for executing tests become more complex as your infrastructure grows.
Virtual machines (VMs) are one of the on-demand, scalable computing resources that Microsoft Azure offers. They enable streamlined allocation of resources in backup, disaster recovery, and deployment environments. A VM is typically chosen when you need more control over your computing environment. However, Azure VMs come with the challenge of simultaneously monitoring them across multiple environments when the VMs are spread unevenly, with some being overutilized and others underutilized.
The Twelve-Factor App methodology is a methodology for building platform-agnostic and resilient applications. It was introduced by Adam Wiggins while working at Heroku in 2011. Nearly 10 years later, this methodology is still considered by the developer community as an excellent practice to follow when building an application. In this article, we will see step by step how Qovery respects and improves the 12-factor methodology. Here we go.
Our very own regional director of Northern EMEA, Jeroen Overmaat, recently joined our partner, Magic Sandbox BV (MSB), for the inaugural episode of Magic Devcast, their new technology podcast. Magic Devcast brings together technology industry personalities and influencers from around the world to discuss how they tackle the ever-changing landscape, how to approach remote work, learning and much more.
Coralogix offers the most extensive alerting mechanism in the logging market, including built-in webhooks for PagerDuty, custom webhooks, and automatic resolve notifications. PagerDuty is a leader in digital operations management. In an always-on world, organizations of all sizes trust PagerDuty to help them deliver a perfect digital experience to their customers, every time.
We’ve always been focused on creating tools that make development teams more productive. In 2014, we introduced GitKraken, the legendary cross-platform Git GUI: an intuitive tool to visualize what’s going on under the hood of Git in a way that makes version control less intimidating for individual developers and more scalable for organizations. Next came Glo Boards, a Kanban tool for project managers and developers.
It feels like a lifetime ago, well, 3 years is a lifetime in tech, that I wrote a blog post explaining how we rewrote our API server from Golang to Ruby on Rails. Here we are and I'm about to explain about how we've been back and forth doing the same thing for our CLI. Just after that time, I wrote the first version of our CLI utility in Golang. However, with only me knowing Golang on the team, we weren't able to achieve the velocity and pace of adding features within the CLI as I'd like.
