Git: One repo to rule them all?
Details
So, you’ve ditched SVN, Perforce or Visual SourceSafe, and all your code is in Git. What now?
Hugely successful and highly scaled software engineering companies like Google, Facebook, Microsoft and Uber choose to go towards a monolithic repository structure even in the current world of microservices and small empowered teams.
While there are tradeoffs to be considered there is obviously one right way to organize your source code, but how?
This meet-up will be all about choosing the best Git practices for you and your software organization. After the debate you will know the whys, whats and hows of one vs. many Git repositories in a software organization.
AGENDA
17.15: Doors open
17.30: Welcome
17:45: “Repositories for the rest of us” - Sofus Albertsen, Continuous Delivery Consultant, Praqma
18:15: “Scaling with Git: From monolith, to poly repos, to mega repos” - Kenneth Boegh, Senior Software Engineer, Uber
18:45: Food and drinks
19:15: Q&A and Debate
20:00: Thanks and goodbye
TALKS
“Scaling with Git: From monolith, to poly repos, to mega repos” by Kenneth Boegh, Senior Software Engineer, Uber
Uber is currently moving from a poly repo structure towards mega repos. Kenneth will take us on a journey where he will tell about why Uber have chosen as they did. Kenneth will be sharing some of the experience they have gained from scaling the company and how it have affected their git strategy over time.
“Repositories for the rest of us” by Sofus Albertsen, Continuous Delivery Consultant, Praqma
Huge companies invest massive amounts of effort into developer processes and custom tooling fit for cloud scale.
But what about the rest of us. When we don't have thousands of developers, and can't compile a custom version of Git that fits our needs perfectly. In this talk Sofus will show efficient workflows and tools for the rest of us!
Psst... The Continuous Delivery and DevOps Conference (CoDe-Conf) will be on October 11th in Copenhagen. Check out the program: https://www.code-conf.com/2018/cph/#agenda
Git: One repo to rule them all?