As with any migration, this one has its challenges. Below you can find more about them and how to overcome some of them:
Obviously, anyone interested in learning about continuous delivery could learn a lot from Netflix. Luckily, Netflix's own engineering manager Ben Schmaus recently wrote an article titled "Deploying the Netflix API" on the Netflix Tech Blog.
Anything that takes longer than ten minutes is not refactoring. That is a redesign.
I’ve been playing around with the Unix tar command a bit this week and realized that I’d memorized some of the flag combinations but didn’t actually know what each of them meant.
After playing around with calculating the eigenvector centrality of a sub graph I learned that this algorithm can also be used in ranking systems. This is applicable for network-based ranking systems as we can build up a matrix of teams, store a value representing their performance against each other, and then calculate an ordered ranking based on eigenvector centrality.
A great discussion on the DevOps Google Group yesterday posed the question "What is a 'DevOps Engineer' anyway?" The OP pondered this question after poring over job listings for "DevOps Engineers" or developer jobs with some form of DevOps in the requirements for the position.
Maciej Zawadzki, co-founder of UrbanCode, talks through a risk calculus that demonstrates that shrinking release batch size lowers risk.
It’s a lot harder to fix application security vulnerabilities than it should be. If you can make the case that there are serious security problems that need to be taken care of, where do you start?
I recently saw a great presentation by Joe Armstrong called “Systems that Run Forever Self-heal and Scale”. The talk is well worth watching, but here’s a few quick notes for a busy reader or my future self.
So find out who thinks who should have access to PROD, plus how to keep calm and PROD on.
With this blog post we start a new series about how we work on the Codeship. Many people asked us how we develop features, about our workflow and which apps we use every day.
By writing we carefully sift through our own thought processes to break it down for novices, or a broader audience. This is a learning process for us, too. It’s therapeutic. But it also hones our message and makes us better teachers. We literally learn by doing.
Doing code reviews is a great way to discover things that people might struggle to comprehend. While proof-reading OpenStack patches recently, I spotted that people were not correctly using the various decorators Python provides for methods. So, here's my attempt at providing me with a link to send in my next code reviews. :-)
A couple of weeks ago I was trying to write a test around some OAuth code that we have on an internal application and I was using Jersey Client to send the various requests. When I ran the test I was getting the following exception:
Yes, there is an “Ops” role for your product. Understand who that is. Consider, for example, what problems an app store solves. Developers must cater to anyone between them and the end user. Any part of an upgrade that could be automated should be.
After a particularly horrendous streak of failures, I sent a team email saying, "Guys, the build is all screwed up and we need to fix it immediately. If you fix the build, I'll buy you doughnuts." You know what happened next? Someone fixed the build within the hour.
Maybe you want to learn shell scripting, but you need to get work done now that you don’t yet know how to do. One of these strategies could buy you some time.
A difficult-to-test scenario are asynchronous processes. If a method-under-test has threading, getting the timing right for the testcase asserts is difficult. Typically, the method will return control to the test class prior to competing the logic that is being tested. The test class then immediately starts processing the asserts. These tests are flaky at best or completely broken at worst.
Aaron and Brian talk with Brian McCallion about real-life usage of AWS, the AWS services model, the new application development model and how enterprises are leveraging public cloud for competitive advantages.
For the uninitiated, Kaizen is a Japanese word meaning "change for the better" or "improvement." The two parts of the word, which are displayed in the picture, translate into "change" and "good."
Yesterday, the big web news story of the day was the NYT outage. But the bigger performance story of the day was not the fact the NYT was down for a few hours, but rather, how the NYT team did all the right things to handle the outage.
In today’s edition of our blog series, “VMware or Microsoft?”, my friend Keith Mayer describes how you can use Windows Server 2012 as your storage servers for clustered NFS storage.
Following our events earlier this year in Raleigh, Montevideo, Buenos Aires, Toronto and Portland, we bring Percona University to Washington, D.C. on September 12.
SaltStack is often boxed into the configuration management tools basket, but it's much different from most software like it. In fact, it is radically different than most configuration management tools.