Site reliability engineering (SRE) is a set of principles and practices that applies aspects of software engineering to IT infrastructure and operations. SRE claims to create highly reliable and scalable software systems. Although they are closely related, SRE is slightly different from DevOps.
From https://en.wikipedia.org/wiki/Site_reliability_engineering
| Employer | Date |
|---|---|
| Deezer | Since 2016 |
| Meetic | 2011 - 2016 |
| Employer | Deezer |
| Description | I joined Deezer to start a transversal technical overhaul. First on the PHP environment, then more broadly on a migration from a monolith to a service-oriented architecture (SOA). I brought and promoted modern development practices with some concepts like Continuous Integration, Continuous Deployment/Delivery, automated testing and modular code architectures adapted to the SOA shift. I also participated in the implementation of Kubernetes, observability of services and the construction of the required tools for team autonomy. I supported the teams in the construction new projects, and in the migration of old ones to the new practices. Finally, I built a GraphQL API in TypeScript with NodeJS to replace Deezer’s old APIs. I studied performance and scalability of this API. To know more → |
| Date | Since 2016 |
| Roles | Developer - Architect - DevOps - Site Reliability Engineer (SRE) - Tech lead - Trainer |
| Employer | Meetic |
| Description | I joined Meetic as a developer and contributed to the product evolutions within a SCRUM team. Then, I joined the CORE team to participate in the redesign of the site’s architecture and in particular to promote modern development practices and industrialization tools. The goal was to create new APIs, to promote and implement TDD, and CI/CD tools. I also actively participated in the training of the teams. To know more → |
| Date | 2011 - 2016 |
| Roles | Developer - Site Reliability Engineer (SRE) - Trainer - Tech lead |