Operations | Monitoring | ITSM | DevOps | Cloud

It’s the end of a long week filled with countless taxing IT change requests. You put your mobile phone on vibrate, still apprehensive from the ALL CAPS text message abruptly received from the IT director last week. Your eyes are burning from the blue hue of your laptop. You begin to shut it down for the evening, lower the TV volume, and sluggishly doze into a deep sleep.

Back in 2005, the Royal Bank of Scotland (RBS) Group was running about 600 Unix servers and they had a bunch of manual processes that slowed down their software delivery cycles and could cause huge delays. As David Sandilands, an infrastructure engineer at RBS, put it in a webinar he did with us, their releases weren’t quick enough.

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.

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.