Continuous integration (CI) / continuous delivery (CD) is a model that allows software development teams to automate the integration and delivery of code changes in a more frequent and reliable manner. This gives development teams more time to improve the quality of their code, test with greater depth, and leads to more customer deployments overall.

Edgardo Peregrino is a freelance software developer, writer, maker and IT technician. For six years now, I’ve been a passionate maker with a focus on robotics. Recently, I entered the world of cloud native computing, which has allowed me to integrate maker projects with open source tools such as Grafana, Prometheus, and Jaeger.

With more than 7,000 customers and double the number of employees ServiceNow had four years ago, our digital technology (formerly IT) operations team faced increased demand for compute, storage, and bandwidth. At the same time, we had to maintain tight security controls. We embrace a three-zero strategy: zero unplanned outages, zero physical footprint, and zero user-reported incidents.

More organizations than ever run on Infrastructure-as-Code cloud environments. While migration brings unparalleled scale and flexibility advantages, there are also unique security and ops issues many don’t foresee. So what are the major IaC ops and security vulnerabilities? Configuration drift. Cloud config drift isn’t a niche concern. Both global blue-chips and local SMEs have harnessed Coded Infrastructure.

Multi-cloud strategy – the use of multiple private or public clouds – is increasingly becoming the main method companies use to deploy their IT infrastructure. In the next three years, an estimate 64% of companies will rely on multi-cloud as their main deployment model source. Despite the complexities that come from operationalizing it, as we disccussed in The Challenges of Building Multi Cloud, the multiple benefits that come from this deployment model can often make it worth the effort.

We have a term we like to use when we meet CFOs who have just gotten their biggest AWS bill ever: bill shock. Bill shock is when finance suddenly rings the alarm that the bill is “too high” and gets everyone scrambling to explain what they’re spending money on. It often happens when the bill reaches a new milestone (the first million, ten million, or hundred million) or growth trajectory (it doubled in a quarter!?). The problem with bill shock is that it can be highly disruptive.

You have a file and you need to send it. Email is the obvious choice, but it's sensitive and you know nothing sent via email is 100% secure. What are your options? You could load the file to a password-protected USB and mail it physically, fax it perhaps, or, the best choice, find an encrypted file sending service. There are several great, private file sending services on the market today, all with their own strengths and weaknesses.

At Platform.sh, we are committed to making your deployment experience as fast and seamless as possible, so that you can continue pushing changes as much as you need, and keep your customers happy. As part of this commitment, we are releasing three new infrastructure improvements, which will greatly improve caching strategy and significantly reduce downtime during deployments.

Azure Functions is an on-demand serverless compute offering built on top of Azure App Service that enables you to deploy event-driven code without the need to provision and manage infrastructure. Because applications rely on Azure Functions to handle business-critical tasks such as processing orders or logging in users, it’s important to ensure that your functions respond quickly when they’re invoked.