3 Service pipelines: Building cloud-native applications

 

This chapter covers

  • Discovering the components for delivering cloud-native applications
  • Learning the advantages of creating and standardizing service pipelines
  • Using Tekton, Dagger, and GitHub Actions to build cloud-native applications

In the previous chapter, you installed and interacted with a simple distributed Conference application composed of four services. This chapter covers what it takes to continuously deliver each component using the pipeline concept as a delivery mechanism. This chapter describes and shows in practice how each of these services can be built, packaged, released, and published so they can run in your organization’s environments.

This chapter introduces the concept of service pipelines. The service pipeline takes all the steps to build your software from source code until the artifacts are ready to run. This chapter is divided into two main sections:

  • What does it take to deliver a cloud-native applications continuously?
  • Service pipelines
    • What is a service pipeline?
    • Service pipelines in action using:
      • Tekton, a Kubernetes native pipeline engine
      • Dagger to code your pipelines, and then run everywhere
      • Should I use Tekton, Dagger, or GitHub Actions?

3.1 What does it take to deliver cloud-native applications continuously?

3.2 Service pipelines

3.3 Conventions that will save you time

3.4 Service pipeline structure

3.4.1 Service pipeline in real life

3.4.2 Service pipeline requirements

3.4.3 Opinions, limitations, and compromises around service pipelines

3.5 Service pipelines in action

3.5.1 Tekton in action

3.5.2 Pipelines in Tekton

3.5.3 Tekton advantages and extras

3.5.4 Dagger in action

3.5.5 Should I use Tekton, Dagger, or GitHub Actions?

3.6 Linking back to platform engineering

Summary

sitemap