May 2021 Summaries

Harness has introduced new features and integrations aimed at improving its continuous delivery (CD) module, notably integrating Terragrunt to streamline infrastructure as code practices and enhancing custom dashboards for better deployment visibility. The company released an ebook on modernizing continuous integration (CI) and hosted the {unscripted} conference featuring industry experts like Dave Farley. The conference also included discussions on observability, with insights shared by Chris Riley from Splunk. Harness allows users to configure Terragrunt similarly to Terraform or CloudFormation, supporting the DRY principle to reduce maintenance across different environments. Enhancements to custom dashboards now enable users to better analyze deployments by environment type and service. Additionally, Harness plans to implement new features like supporting secrets with webhook triggers and introducing granular access control for deployment rollbacks, alongside hosting various webinars and participating in industry events.

Harness has enhanced its infrastructure as code capabilities by integrating native Terragrunt support, allowing users to apply the DRY (Don't Repeat Yourself) principle more effectively in Terraform code and thereby reduce repetition and maintenance across different environments. Terragrunt, a wrapper tool around Terraform, facilitates the management of identical Terraform code across various environments by handling differences in input, output, and state files efficiently. Previously, Harness users had to use shell script provisioners for Terragrunt infrastructure provisioning, but now they benefit from a first-class integration, making the configuration of Terragrunt as seamless as configuring Terraform or CloudFormation within Harness. This development is particularly appealing to developers who value maintaining components easily and defining code once for multiple uses.

Cloud cost intelligence, as discussed in the article by Bhargav Brahmbhatt, is a comprehensive approach to managing cloud expenses through transparency, optimization, and forecasting, which can lead to significant cost savings and improved resource utilization. Harness Cloud Cost Management is highlighted as a tool that provides businesses with detailed insights into their cloud spending, enabling them to identify wastage and predict future costs, thus transforming financial management related to cloud services. The article emphasizes the importance of understanding where costs originate, how to reduce them, and what future expenses might look like, forming the basis for implementing effective cost management strategies. Various metrics are essential for this process, including overall spend, cost by cost center, utilized versus unutilized resource spend, and unit cost, which help in achieving cost transparency and optimization. Additionally, it compares native billing tools from major cloud providers such as AWS, Azure, and GCP, explaining their capabilities and limitations in providing cloud cost intelligence.

Kubernetes has revolutionized CI/CD practices by facilitating rapid deployments and rolling updates, but maintaining discipline in these processes remains essential to fully harness its potential. The platform's use of a declarative language enables consistent and agile application and infrastructure management, offering benefits such as ephemeral build runners, artifact repositories, and health checks to ensure smooth and efficient deployments. By leveraging Kubernetes for CI, teams can automate build processes and manage compute resources effectively, while CD practices benefit from its rapid deployment capabilities and advanced release strategies like blue-green and canary deployments. The integration of modern tools and practices, such as GitOps, allows for enhanced standards enforcement and self-healing, ensuring reliable and secure software delivery. Despite the ease and speed Kubernetes provides, the importance of adhering to established best practices within CI/CD processes remains paramount.

Zeotap significantly improved its software deployment process by adopting Harness, which increased deployment frequency by 36 times and reduced rollback time from 4 hours to seconds. This transformation allowed developers to focus on high-priority projects and streamlined the deployment process from requiring a team for 4 hours to just one developer for 30 minutes. Previously, Zeotap's deployment process involved over 400 Jenkins pipelines with a high change failure rate and lacked visibility, limiting deployments to once a month. The switch to Harness enabled multiple daily deployments using standardized pipelines and automated rollbacks, while also helping Zeotap achieve GDPR, ISO27001, and CSA STAR compliance through advanced role-based access control, audit, and reporting capabilities. As a result, Zeotap's developers gained independence in scheduling deployments and reduced the risk and effort associated with software delivery.

Continuous Integration and Continuous Delivery (CI/CD) pipelines are essential for efficiently transitioning software changes from development to production, ensuring reliability and speed in deployment. The Harness eBook on CI/CD pipeline patterns explores common strategies that organizations use to design these pipelines, emphasizing the importance of having a fast, safe, and repeatable workflow for software delivery. Pipelines transform source code into builds, which are then tested and deployed across environments until they reach end-users. The book highlights the significance of choosing the right pipeline strategy based on various factors such as environments, tests, services, and manual approvals, and it outlines different design patterns like the Button Push Pattern, Test Automation Pattern, and Full Approval Pattern, each offering its benefits and challenges. By examining these patterns, the eBook helps organizations tailor their CI/CD processes to meet specific needs, while encouraging best practices for achieving efficient software deployment.

Understanding Java's synchronization mechanisms, such as the synchronized keyword and object locks, is essential for developing efficient multi-threaded applications by ensuring smooth performance and preventing deadlocks and throughput issues. Java and Scala offer various components like object pools, concurrent collections, and advanced locks to facilitate solid multi-threaded programming. The synchronized keyword, a popular idiom in Java, is used to restrict method execution to one thread at a time or to declare a code block as a critical section. Synchronization is implemented using bytecode instructions MonitorEnter and MonitorExit, which are automatically managed by the Java compiler to ensure proper lock acquisition and release, even in cases of exceptions. The JVM optimizes locking through mechanisms like lock biasing and CAS operations to enhance efficiency. These mechanisms and optimizations are crucial for maintaining application liveliness and preventing issues like deadlocks and stranded threads.

Integrating StackHawk's Dynamic Application Security Testing (DAST) into the CI/CD pipeline using Harness empowers development teams to detect and address security vulnerabilities early in the software development lifecycle, enhancing application security without compromising deployment speed. The process involves configuring StackHawk to scan applications for vulnerabilities by running tests against isolated instances, often containerized, and utilizing Harness to deploy applications to Kubernetes clusters. The guide outlines a detailed setup, including the installation of Harness delegates, configuration of environments, and orchestration of deployment pipelines that include security scans, interpretation of results, and conditional deployments based on scan outcomes. By leveraging these tools, teams can achieve a seamless DevSecOps workflow, enabling automated security checks and fostering a shift-left security approach, where security considerations are integrated into every stage of development.

DevOps represents a transformative approach to software delivery, emphasizing collaboration, mindset, and continuous improvement through cross-functional teams, appropriate tools, and a commitment to ongoing learning and adaptation. The evolution of DevOps from traditional waterfall methodologies to a more dynamic, agile framework has been driven by the need for faster and more efficient business value delivery across various industries. This approach requires a cultural shift within organizations, where people, processes, and technology integrate seamlessly to support a successful DevOps lifecycle. Key principles involve creating with the end in mind, fostering cross-functional teams, and committing to a journey of experimentation and learning. Essential practices such as source code management, continuous integration, continuous delivery, infrastructure as code, and secrets management enable teams to deliver high-quality software efficiently. Ultimately, each organization must tailor DevOps practices to fit their specific needs and contexts, continually innovating and experimenting to enhance their capabilities and outcomes.

GoCD is an open-source Continuous Delivery tool offering standard features such as end-to-end pipeline visualization, cloud-native deployments, complex workflow modeling, and advanced traceability, positioning it as a decent option for beginners and a generic CI/CD solution. However, in a competitive market, alternatives like Argo CD, GitLab, and Harness offer advanced functionalities that enhance software delivery processes. Argo CD is notable for its GitOps focus and ease of use, GitLab integrates project management with CI/CD and enhanced security, while Harness stands out with its comprehensive software delivery platform incorporating modules for CI, CD, verification, cost management, and feature flag management. These alternatives, with their unique features and strengths, offer more efficient, secure, and scalable solutions compared to the standard features of GoCD.

In a podcast episode of ShipTalk, Chris Riley, a Senior Developer Advocate at Splunk, discusses the nuances of observability (O11Y) and the importance of internal advocacy for technological change within organizations. Riley highlights that observability involves more than traditional monitoring by focusing on distributed systems and integrating practices like incident response and infrastructure monitoring. He stresses the significance of data quality and the strategy behind incident response, emphasizing that these elements are crucial for effective technology use rather than just relying on tools. Additionally, Riley points out that advocating for new technologies requires empathy, stewardship, and aligning with organizational goals. He reflects on the broader role of advocacy in tech-enabled enterprises, suggesting that even roles like Site Reliability Engineering (SRE) now focus on spreading best practices across organizations.

Intelliflo, a company providing technology solutions for financial advisors, significantly enhanced its software deployment process by adopting Harness, leading to a remarkable increase in deployment frequency from 10 to over 200 times a day and reducing reliance on dedicated maintenance engineers. This transition facilitated a smoother migration to AWS, allowing intelliflo to expand its international customer base and improve multiregional support without undergoing the initially estimated five-month overhaul of their existing Jenkins pipelines. Harness provided intelliflo with out-of-the-box features such as blue-green deployments and a GitOps experience, which streamlined their environment configurations and reduced maintenance overhead, enabling the company to modernize its software delivery efficiently and effectively.