Summary
In this chapter, we learned how to set up the Amplify DevOps pipeline, which automates the entire build workflow. We looked at various ways of sending notifications about when the build succeeded or failed. After that, we discussed some different ways of triggering the build and how it works in different kinds of branching scenarios.
Finally, we saw what NoOps (or LessOps) is all about. As we already know, DevOps exists for microservices or monolith architectures, but NoOps should be used for serverless technologies such as AWS Amplify Function or a Function as a Service (FaaS) such as Lambda. This is because we don't really need to set up nor maintain the infrastructure for the CI/CD pipeline.
In the next chapter, we will be learning about end-to-end test automation. I can say that this is a huge time saver based on my experience with many development teams that build enterprise solutions.
