Operations | Monitoring | ITSM | DevOps | Cloud

Making an Open Source Software with sensitive data and dozens of external integrations is a real challenge, here are feedbacks and tradeoffs we've made.

At incident.io, we're acutely aware that we handle incredibly sensitive data on behalf of our customers. Moving fast and breaking things is all well and good, but keeping our customer data safe isn't something we can compromise on. We run incident.io as a multi-tenant application, which means we have a single database (and a single application).

I am a big proponent of cross-functional alignment, as I remnded our ELT at a recent off-site meeting. There’s a lot of buzz about FinOps bringing financial accountability to cloud spend by eliminating procurement siloes and implementing cross-functional best practices. As the CFO of a SaaS company, I fully support this practice. In fact, Virtana recently made some changes to our cloud infrastructure as part of our own evolution.

Cloud computing is the on-demand availability of computer system resources without direct active management by the user. Instead, the delivery of said resources is available over the internet, which has made cloud computing a popular digital service that various industries use to operate and manage work tasks. How cloud computing services are implemented, hosted and accessed by users is called cloud deployment. There are different types of deployments, each with defined advantages for users.

In August 2016, the United States government announced a new federal source-code policy, which mandates that at least 20% of custom source code developed by or for any agency of the federal government must be released as open-source software (OSS). The memo of this policy also states that the Federal Government spends more than $6 billion each year on software through more than 42,000 transactions. Obviously, this is a huge business for all open-source developers.

With Halloween behind us and the holiday shopping season fast approaching, engineering and product teams know what that means: code freezes! At xMatters, code freezes are a part of our product release process in anticipation of the busiest — and most important — time of the year for many of our customers. But code freezes are just one piece of the puzzle in how we ensure our customers have the most reliable experiences. The way our product releases are designed is much more than that.

Editor’s note: Today we hear from Kenny Kon, an SRE Director at Sabre. Kenny shares about how they have been able to successfully adopt Google’s SRE framework by leveraging their partnership with Google Cloud. As a leader in the travel industry, Sabre Corporation is driving innovation in the global travel industry and developing solutions that help airlines, hotels, and travel agencies transform the traveler experience and satisfy the ever-evolving needs of its customers.