This article originally appeared on Forbes.
With more and more infrastructure and applications moving to the cloud in support of digital transformation, one of the decisions enterprises must confront is the best approach to cloud migration for long-term success. While some favor a lift and shift model, others come down on the side of replatforming or even a refactoring approach. However, there is no single path to success. And, indeed, a hybrid approach is often the ideal answer.
As DevOps adoption grows, the demand for DevOps engineers grows with it and a field of highly diverse applicants. Here at Flux7, we are frequently asked for best practices and tips when sourcing and hiring a DevOps Engineer. While we highly recommend “breeding” DevOps experts in-house, when our customers do feel the need to hire a DevOps resource, the following are our top five recommendations:
As I’m flying from Austin, the home of Flux7, to the Silicon Valley, my immediate thoughts are honed in on the session I’m sharing this week at the Internet of Things Expo in Santa Clara. I’ll be discussing how Docker helped our client Horan & Bird quickly advance the development of its IoT app. It’s a really good story. And one I hope you have a chance to hear at the conference.
If you won’t be attending, you can read about it here.
But, as my jet mates and I soar above the clouds over Nevada, my thoughts are also wandering to other significant events, both recent and upcoming.
54 signups so far and still increasing. We have the Docker Austin meet up coming up this Thursday and the Flux7 team is excited to be playing a key role in it.
Our website, flux7.com, runs inside a Docker container and last weekend we learned that Flux7’s investment in Docker is really starting to pay off. Using Docker we were quickly able to recover the website from a buggy code change, quickly reproduce and fix the bug. Here’s what happened.
We had a very interesting discussion with a client yesterday about the use of Docker and where it fits within their environment. The client’s representative was pushing back on us for using Docker and, as always, I enjoyed the constructive argument. As it turned out, we pretty much fought to a conclusion that Docker does have some clear advantages in an Dev environment. Our debate challenged me to crystallize my thoughts and to clearly articulate why we use Docker at Flux7, hence, this article.
At Flux7, we believe in high productivity, so each of our engineers handle multiple AWS client accounts, and sometimes multiple engineers handle one client. As a team leader who manages 10s of client accounts, I need to switch in and out of each account several times an hour, which is a real challenge because so much customer-specific information must be loaded into files and environments that we call “customer profiles”. Each includes the following: