At Calavista, we were doing DevOps before it had a buzz-word title. Likewise, we’ve been doing DevSecOps for quite some time, and it’s about time we start calling it what it is.
This one goes out to our Austin-Area colleagues. Around the office (and over the phone) we have been discussing the events of the past week or two – finally power is restored across town after a classic February cold-snap. It’s true that the ice storm we saw recently was unique, but it wasn’t totally unheard of.
Our previous blogs have defined DevOps as a collaborative culture with its own defined practices, ideas, tools, technology, processes, and metrics. Integrating some of these elements into your workflow can help streamline and improve your development process.
DevOps has made it possible for organizations to develop and release stable applications faster than ever. However, and organization with a proper DevOps pipeline should always include Continuous Monitoring through the development lifecycle.
While it may seem I’m just trying to work in as many buzzwords as I can, in fact, there really is an important intersection of these three elements. I’ve been interested in both big data and fast data for several years, and my newest tech interest is machine learning.
I recently started a new greenfield project, where the decision was to use a microservices-based architecture. The application was pretty well defined, including most of the data model, since there was a working prototype, so my biggest first concern was how to break it up appropriately into microservices.
Test Driven Development (TDD) is a development practice where developers author code by first describing the intended functionality in small, automated tests, then writing the necessary code to make that test pass.
Every day, a million and one thoughts fly around in our heads. Sometimes, they’re killer ideas – the ones we think will make use never have to work again for the rest of our lives. Other times, they are just products of a very overactive imagination.
In the last decade, we have seen significant shifts in software development operations. One of these shifts is the evolution of DevOps, which came into play in 2008/9.
In this post, I’m going to discuss some approaches to obtain realistic Test Data without compromising the security of any customer’s sensitive data. In the world of health care software, this is referred to as Personal Health Information (PHI), but the concept exists in financial software, document management,… really, everything.