An Infrastructure in Line with My Requirements • Erwan Alliaume & Eric Favre • YOW! 2018

Developers and ops teams must collaborate to create an infrastructure that aligns with functional requirements, using tools like Git and Kubernetes, and adopting DevOps practices for efficient application success.

Key takeaways
  • Creating an infrastructure that aligns with functional requirements is crucial for application success.
  • Eric and Erwan discussed Okto Technology’s experience in evolving their infrastructure to support microservices and DevOps.
  • Infrastructure components include servers, containers, databases, file systems, and backup systems.
  • The role of ops is to create an infrastructure abstraction layer, providing a standardized infrastructure for developers to work with.
  • For developers, it’s essential to use tools like Git, SVN, Mercurial, and build tools, and to understand concepts like automated testing, continuous integration, and container orchestration.
  • The infrastructure abstraction layer should provide a standardized environment, allowing developers to focus on writing code instead of managing infrastructure.
  • The concept of the “two-speed IT” came up, where there’s one approach for legacy infrastructure and another for new technology adoption.
  • The importance of collaboration, trust, and communication between developers and ops teams was emphasized.
  • Okto Technology’s experience showed the need for a centralized logging solution and the importance of monitoring and alerting to detect issues early.
  • The team encountered issues with file system saturation and eventually moved to a container-based infrastructure using Kubernetes.
  • They also explored the concept of “t-shaped developers” who have a broad range of skills to work on different aspects of the development and operations process.
  • The importance of continuously learning and adapting to new technologies, services, and methodologies was highlighted.
  • Conclusion: creating an infrastructure that supports a company’s goals and functional requirements can lead to increased efficiency, reduced technical debt, and improved collaboration between development and operations teams.