Julian's Notebook - devops https://prod.jnet.julianscorner.com/ 2026-04-17T12:21:04+00:00 Julian's Notebook https://prod.jnet.julianscorner.com/ https://prod.jnet.julianscorner.com/_media/wiki/dokuwiki-128.png text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Build Features Iteratively https://prod.jnet.julianscorner.com/devops/build Build Features Iteratively Source Control Management DVCS vs VCS (central) Git Continuous Integration TeamCity Continuous Delivery OctopusDeploy/Other Tool, Configuration Management, ie. web.config) text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Treat Infrastructure as Cattle Instead of Pets https://prod.jnet.julianscorner.com/devops/cattle Treat Infrastructure as Cattle Instead of Pets <TODO> Describe why to treat it as cattle. Focus on Availability Plan for Capacity Manage Risk Automation * Desired State Configuration (DSC) * Chef text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Why Containers? https://prod.jnet.julianscorner.com/devops/containers Why Containers? The following list shows the key reasons developers are moving to containers: * Consistent: Containers include the application and all of its dependencies. The application executes the same code, regardless of computer, environment or cloud. text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Deliver Features Continuously https://prod.jnet.julianscorner.com/devops/deliver Deliver Features Continuously Using Unit, Integration, and Acceptance Testing. text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Use Scalable Designs https://prod.jnet.julianscorner.com/devops/design Use Scalable Designs Use Scalable Designs Including the Development Workflow text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Integrate Features Continuously https://prod.jnet.julianscorner.com/devops/integrate Integrate Features Continuously TODO Why? Use Short-Lived Branches WHY? also link over to SCM, GIT, and GitFlow stuff in the SCM section Cross-Functional "Packages" Instead of Code-Merges WHY? Talk about NuGet/NPM packages. Include SOLID reference specifically the Open-Close principle. Talk about why code-merges can and are difficult to merge especially when branches live for months instead of days text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Collect and Use Metrics to "Measure" Deployment Issues https://prod.jnet.julianscorner.com/devops/metrics Collect and Use Metrics to "Measure" Deployment Issues (detail page: errors per minute, Time to first byte, Feature Usage) Mean Time to Failure vs Mean Time to Recovery text/html 2023-09-18T20:00:11+00:00 Anonymous (anonymous@undisclosed.example.com) Continuous Delivery https://prod.jnet.julianscorner.com/devops/octopus Continuous Delivery Continuous Delivery is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software faster and more frequently. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production.