Featured in Architecture & Design

Monal Daxini presents a blueprint for streaming data architectures and a review of desirable features of a streaming engine. He also talks about streaming application patterns and anti-patterns, and use cases and concrete examples using Apache Flink.

Featured in AI, ML & Data Engineering

Joy Gao talks about how database streaming is essential to WePay's infrastructure and the many functions that database streaming serves. She provides information on how the database streaming infrastructure was created & managed so that others can leverage their work to develop their own database streaming solutions. She goes over challenges faced with streaming peer-to-peer distributed databases.

News

The 2019 State of Testing survey is now seeking participation, and aims to provide insights into how the testing profession develops and to recognize testing trends. Anyone completing the survey will receive a complimentary copy of the State of Testing 2019 report once it is published.

Docker has released a new Docker Hub experience that combines the previous Docker Store, Docker Cloud, and Docker Hub functionality into one location. This provides users with a single experience for finding, storing, and sharing container images. Verified and certified images and plugins are now available through Docker Hub. They have also released improvements to the automated build feature.

Many incidents happen during or right after the release argues Charity Majors, CEO at Honeycomb. She believes that stronger ownership of the deployment process by developers will ensure it is executed regularly and reduce risk. She argues for investment in the tooling, high observability during and after release, and small, frequent releases to minimize the impact caused by shipping new code.

At the recent Connect() event, Microsoft announced several new features and integrations with Azure Pipelines. The new features and integrations include an Azure Pipelines extension for Visual Studio Code, management of GitHub Releases, support for IoT projects, and ServiceNow integration.

Kohsuke Kawaguchi, creator of Jenkins and CTO at CloudBees, spoke last month at Jenkins World in Nice about five on-going initiatives to modernize the popular CI/CD tool. The initiatives revolve around Jenkins Evergreen, Jenkins Pipeline (Blue Ocean), Jenkins Configuration-as-Code, Jenkins X, and Cloud-Native Jenkins.

A Lead Developer at Thoughtworks shared his team’s experience in rewriting the build pipeline for one of their clients. They migrated from Jenkins to ConcourseCI, with a focus on configuration-as-code, pipeline-driven delivery, container support and visibility into the system.

At GOTO Copenhagen, Rod Johnson announced “The Software Defined Delivery Manifesto”, and argued that the delivery of software “is not a detail, it is our job”, and accordingly, “now is the time to engineer our delivery”. The authors of the manifesto argue that software defined delivery should be core, well-engineered, collaborative, accelerated (through automation and reuse) and observable.

Mesa CI is a continuous integration system at Intel for running builds and compliance test suites for the Mesa graphics library. It runs across more than 200 systems and runs tens of millions of tests per day.

At GitHub Universe in San Francisco, GitHub announced a number of new tools to help developers make their workflows more effective, including Actions, Suggested Changes, Security Alerts for .NET and Java, and more.

With continuous delivery we need to focus on quality as we write the code. Not every team will have testers, but if there are testers then they will work closely with developers, writing code to automate the small number of tests that cannot be covered by unit tests while helping developers creating unit tests.

Microsoft has announced Azure Pipelines, their new CI/CD service which is part of the Azure DevOps offering. Azure Pipelines allows to build, test, and deploy workloads and works together with a diverse range of languages, project types, and platforms.

The Jenkins project team has decided to split its efforts between focusing on stability issues and on better support for running on platforms like Kubernetes. The former, which will potentially have backward-incompatible changes, will impact the release model and provide a more pre-configured installation, whereas the latter will work on similar lines as the existing Jenkins X project.

Over the past year, the Weaveworks team has increasingly refined the ideas around the practice of “GitOps”, their name for how they use developer tooling to drive operations and to implement continuous delivery.