Hope everyone had a great Thanksgiving holiday, and I'm sure we're all buckling down for the typical end-of-year madness. This week: continuous integration with Salesforce, use cases for Docker, lean development with DevOps, and full stack deployment.
Zone Leader John Vester has been interested for a while on how to introduce DevOps methodologies and integrate CD and CI tools with Salesforce, and for the next few weeks he'll be writing about his experiences and how you can do the same. John has already published a followup to this article here. The first article in this series looks at what makes Salesforce unique from an architecture perspective, the challenges developers face in working with it, and how to use Atlassian tools for a CI pipeline that includes Salesforce.
There's been a lot of excitement and skepticism around Docker as so many open source and enterprise projects attempt to harness the benefits of containerization. It's a tough space to navigate and get started in. Here, Ajitesh has provided a great, concise list of what Docker can do to make developer lives easier for those who may not know everything about the potential benefits of using containers.
Barry is organizer for DevOps Days London next year, and I hope to hear more from him in the future! He's contributed a great article about waste that can arise from day-to-day operations, how to reduce that waste via familiar lean principles, and using metrics throughout the organization to help everyone understand the best KPIs. He also makes several references to Hoshin Kanri, which roughly means "a methodology for strategic direction setting." I found some more information on this methodology from a consulting site, which you can read here.
We know the traditional deployment process means you change to your code, commit it to source control, test it, and deploy it. We also know that we can treat infrastructure as code, thanks to tools like Chef, Puppet, and Ansible, but what about re-deploying the whole stack every time you needed to make a change to anything? Sounds weird, but Zachary Flower has some thoughts on why this approach is better for software agility, Continuous Delivery, and code quality than the traditional approach.