Published Jun 23, 2017

Deploying Changelog.com

Gerhard Lazu delves into the transformation of Changelog.com's infrastructure from WordPress to a modern Phoenix/Elixir stack, highlighting automation through Ansible and Concourse CI, the impact of learning and collaboration, and strategies for future-proofing with a potential shift to Kubernetes.
Episode Highlights
The Changelog logo

Popular Clips

Episode Highlights

  • Flexibility

    Changelog.com’s infrastructure is designed to be flexible and adaptable, allowing for seamless transitions between different platforms and technologies. emphasizes the importance of not being tied to a specific stack, which enables the team to move hosts or container platforms with ease 1. This approach ensures that the system can evolve alongside the changing needs of the site, which has grown significantly in terms of content and audience 1. highlights the importance of staying informed about new technologies while maintaining a safe distance from the cutting edge to avoid unnecessary complexity 2.

    It's always like a flow, right? It's never static. You've never arrived. You have to keep moving and you have to keep going because the landscape is changing.

    ---

    By keeping things simple and containerized, Changelog.com reduces the cost of change, allowing for quick adaptation if a significant benefit arises from new technologies 2.

       

    Kubernetes

    The potential migration to Kubernetes is a topic of interest for Changelog.com, as it represents a future platform that could offer benefits in scalability and management. notes that while Kubernetes has matured significantly, the complexity it introduces must be carefully weighed against the current system's simplicity and effectiveness 3. The team is cautious about transitioning, as the current setup, though imperfect, works well and is easier to manage 3. and Jerod discuss the importance of evaluating the tangible benefits of such a migration against the costs involved 4.

    Maybe it never will make sense to go to Kubernetes. Maybe what we have now is enough.

    ---

    The decision to migrate would depend on whether the advantages of Kubernetes outweigh the simplicity and reliability of the existing infrastructure 4.

Related Episodes