DevOps

Kubernetes is all the rage right now for several reasons: It’s the industry standard for deploying containers in production, it’s the new go-to in managing virtualized infrastructure, developers seem to love it, and it can run any containerized application (thanks to Cynthia Harvey for organizing these thoughts).

Continuous improvement and continuous development (CI/CD) is a landmark of solid Linux and DevOps work, specifically in Kubernetes and Jenkins.

Recently we worked with an amazing biotech client on an initiative to shutdown internal self-hosted systems and move all services to “the cloud”.

Jenkins is a core part of our Continuous Integration and Continuous Deployment (CI/CD) pipeline for our clients. Here are the top 3 reasons we love Jenkins:

Container based micro-service deployment has been a logical evolution of better managing large software systems and getting the most out of your server resources.

With many diverse server systems to deploy, configure, and maintain for our clients, it is important to have a Managed Configuration and Orchestration platform.

Knowing what went wrong in the event of a failure is incredibly important. Elasticsearch provides storage for log level events across systems, creating a reliable and redundant way to store, search, and query critical system events.

If you are just getting into DevOps, here is some reading and light homework to get you started: Read the Phoenix Project book by Gene Kim etc.

As a team we have many years of experience using a plethora of different solutions for storing code. Everything from paid solutions like Jira and Bitbucket, all the way to hand-written custom solutions to store assembler code.

Wim had the pleasure of moderating the “Props to DevOps!” panel meetup on March 21st, 2017, presented by BC Tech Jobs in partnership with the BC Tech Association.