Focus on what matters with instant visibility into the condition of your backup application and detailed analytics to quickly pinpoint where any issues lie. IBM’s backup monster, Spectrum Protect (TSM as we called back in the day), sucks. Not because the software sucks – it’s actually the best there is – but because backups suck in general. It’s the quintessential necessary evil of IT.
Testing within the CI/CD pipeline, also known as shift-left testing, is a devops best practice that enables agile teams to continually assess the viability of new features at every stage of the development process. Running tests early and often makes it easier to catch issues before they impact your users, reduce technical debt, and foster efficient, cross-team collaboration.
The Datadog Partner Network (DPN) is a rapidly growing registry of hundreds of leaders in the cloud service industry who choose Datadog to meet their infrastructure-monitoring needs. Partners are well-acquainted with the more than 400 technology integrations available to Datadog customers, but with the huge diversity in technical stacks used by our customers, there’s always demand for more customization and flexibility.
Today, at Dash 2020, we unveiled new products and features on the Datadog platform that provide engineering teams with even deeper visibility into their distributed applications and infrastructure. With these additions, Datadog further streamlines every step of your release cycle, from shift-left testing in your CI/CD pipelines to profiling your code in production.
During my career, I’ve taken part in many on-call rotations and post-mortems. The longest on-call rotation I’ve ever had — no breaks, vacations, or holidays — lasted for a whopping 2.5 years at Lucid Software. I’m jaded. I strongly prefer stability to tinkering with shiny new toys. Very few software engineers start this way, but enough of them make the transition after having been bit enough times by a bad release.
For our second community meetup we focussed on using Civo for CI/CD through GitOps and Github actions for cloud native application development This installment featured talks from our CTO Andy, our Developer Advocate Kai, and guest talks from community members Sam Weston and Johannes Tegnér. The talks touched on a wide variety of topics within CI/CD, from automating builds to monitoring and observability. Here's what was on the agenda...
Interviewing for a new job and finding your right fit is tough enough, not to mention the added stress of interviewing during the COVID-19 pandemic. As stated on our Careers Page, our process is pretty consolidated and we move quickly (you have to when you’re a growing tech company).
If you know anything about WebAssembly (WASM), it’s probably that WASM lets you execute code compiled from languages such as C, C++, Rust, or others in the browser at almost native speeds. You might be less familiar with the fact that WASM is not only an interesting technology in the browser, but also in other environments that require fast sandboxing. As such, WASM has found some popularity with edge computing and as a lightweight docker replacement for certain situations.
In the pre-Kubernetes, pre-container world, backup and recovery solutions were generally implemented at the virtual machine (VM) level. That works for traditional applications when an application runs on a single VM. But when applications are containerized and managed with an orchestrator like Kubernetes, this system falls apart. That means effective disaster recovery (DR) plans for Kubernetes must be designed for containerized architectures and natively understand the way Kubernetes functions.
Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?", "What is continuous deployment?", and "Are continuous deployment and continuous delivery the same thing?" So first, let's start by clearly defining these terms.
