Git architects
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
279
On Slideshare
276
From Embeds
3
Number of Embeds
1

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 3

http://wiki.glitchdata.com 3

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Conceptually simple Integration Manager not needed (in theory) May lead to conflict Doesn't scale
  • Who do you think “G” is?

Transcript

  • 1. Git ArchitectsPresentation: 1hrWorkshop: 1hr © Terence ChiaRevision: 1.2 1 September 2010
  • 2. Git Architects● System Design ● Production Release● Team Design ● Testing● Software Design ● Issue Management● Code Organisation ● Continuous Integration● Environment ● Configuration● Infrastructure ● Backups● Development ● Security Process ● Performance
  • 3. System Design● Legacy Systems● Modularity / n-tier● New Systems● Integration● Support
  • 4. Team Design● Existing Team● Skill Sets● Development Capability● Team Evolution – Hiring / Training● Support
  • 5. Software Design● Legacy code● Define Universe● Define Interfaces● Modularity● New Development● Integration● Support
  • 6. Code Organisation● Modularity● Maintenance● Define Interfaces● New Development● Integration● Support
  • 7. Environment● Development Environment● Resource Schedules● Local / Remote / Team size● Tools● Licenses
  • 8. Infrastructure● Servers● Databases● Message Buses● Network Connectivity● Load● Storage● Security / Repository Security● Licenses
  • 9. Development Processes● Agile / Waterfall● Code Access Protocols● Testing● Terminology – Beta / Alpha / RC● Issue Tracking / Notifications● Continuous Integration● Release
  • 10. Git Workflow: Centralised● Centralised A● Simple● Possible Conflict C B Central● Doesnt Scale Repo● Overall: Below Average D E
  • 11. Git Workflow: Peer 2 Peer● N to N Mesh A● Self-organising Teams C B● Flexible● Possible Conflict● Good for RAD D E● No Point of Truth● Doesnt Scale F● Overall: Bad
  • 12. Git Workflow: Hybrid A● Semi-Centralised● Higher C Satellite B Repo Complexity● Reduced Conflicts D Central G Repo● Point of Truth● Scales Satellite Repo● Lacks Process● Overall: Average E F
  • 13. Git Workflow: Integration Mgr● Mid-sized Teams A A Public Private● Self-organising B B Teams Public Private● Integration C C Manager Public Private● Point of Truth● Not Scalable● Defined Processes Blessed G Integration Repo Manager● IM Bottleneck● Overall: Better
  • 14. Git Workflow: Dictator A A● Large Teams Public Private● Lieutenant/s (IM) B Public B Private● Large Teams C C Overheads Public Private●● Point of Truth● Scalable F Lieutenant E Lieutenant● Defined Processes Blessed Repo● Overall: Good G Dictator
  • 15. And so on ...
  • 16. Production Release● Schedule● Dependencies● Git for Configuration● Passwords● Push / Pull / Manual● Code Integrity
  • 17. Testing● Servers● Databases● Message Buses● Network Connectivity● Load● Storage● Security● Licenses
  • 18. Issue Management● Jira / Trac / Redmine / more...● Git for Versioning – Branches & Tags● Issue Aging● Burndown / Burnup● Gantt● Resourcing
  • 19. Continuous Integration● Realtime / Daily Integration● Git Hooks● Jenkins
  • 20. Git for Configuration● Dev / Test / Production Environments● Minor configuration changes● Logging changes● Configuration Security
  • 21. Git for Backups● Code Backups● Data Backups● Redundancy / Replication● Automated● Rsync?
  • 22. Security● Repository Security● Codebase Signing● Infrastructure Security
  • 23. Git Performance● When is code checked in?● Code? Data? Media? Configuration?● Binary Files? Or Text?● Repository Size● History● Improving Performance– git fsck – git gc (packing)● Case Studies
  • 24. Thank You● Questions?● Design Exercises. © Terence Chia 1 September 2010