Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building and Delivering Microservices on AWS

You're reading from   Building and Delivering Microservices on AWS Master software architecture patterns to develop and deliver microservices to AWS Cloud

Arrow left icon
Product type Paperback
Published in May 2023
Publisher Packt
ISBN-13 9781803238203
Length 602 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Amar Deep Singh Amar Deep Singh
Author Profile Icon Amar Deep Singh
Amar Deep Singh
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Part 1: Pre-Plan the Pipeline
2. Chapter 1: Software Architecture Patterns FREE CHAPTER 3. Chapter 2: Microservices Fundamentals and Design Patterns 4. Chapter 3: CI/CD Principles and Microservice Development 5. Chapter 4: Infrastructure as Code 6. Part 2: Build the Pipeline
7. Chapter 5: Creating Repositories with AWS CodeCommit 8. Chapter 6: Automating Code Reviews Using CodeGuru 9. Chapter 7: Managing Artifacts Using CodeArtifact 10. Chapter 8: Building and Testing Using AWS CodeBuild 11. Part 3: Deploying the Pipeline
12. Chapter 9: Deploying to an EC2 Instance Using CodeDeploy 13. Chapter 10: Deploying to ECS Clusters Using CodeDeploy 14. Chapter 11: Setting Up CodePipeline Code 15. Chapter 12: Setting Up an Automated Serverless Deployment 16. Chapter 13: Automated Deployment to an EKS Cluster 17. Chapter 14: Extending CodePipeline Beyond AWS 18. Index 19. Other Books You May Enjoy Appendix

What is a serverless ecosystem?

In Chapter 1, we talked about serverless architecture patterns and the popularity these patterns have gained in the last few years. Let’s revise our knowledge and see what serverless means in software development.

A serverless application is not actually serverless, but it is a term used to signify that, as an application developer or owner, you are not responsible for maintaining the servers required for your application to run.

Your application is still deployed on servers, but instead of you owning those servers, a service provider is responsible for maintaining the hardware, OS patching, and other operational aspects. You, as a consumer, just request how much memory or CPU is needed and providers handle the provisioning of the required capacity from a pool of resources. You just upload your code and it gets executed on the infrastructure provided. You only pay for the duration of the runtime environment for which your code is executed...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image