Learn AWS Serverless Computing

Using the ecosystem

AWS Lambda is just one service out of upwards of 160, each performing its own function for its own use cases. When we develop code for Lambda, there are often other activities that we need to do around that. I'm referring to the authoring, life cycle, and management activities that are necessary as we evolve our service. When we need to add more functionality, we should look to the ecosystem to see what AWS can provide. Using tooling from within the ecosystem can save us setup time and effort in procuring a new tool elsewhere. We can instantly make use of the native integration that the service will naturally provide and know we are covered under our existing support agreement with AWS if anything goes wrong. An additional ...