Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Pragmatic Microservices with C# and Azure

You're reading from  Pragmatic Microservices with C# and Azure

Product type Book
Published in May 2024
Publisher Packt
ISBN-13 9781835088296
Pages 508 pages
Edition 1st Edition
Languages
Author (1):
Christian Nagel Christian Nagel
Profile icon Christian Nagel
Toc

Table of Contents (23) Chapters close

Preface 1. Part 1: Creating Microservices with .NET
2. Chapter 1: Introduction to .NET Aspire and Microservices 3. Chapter 2: Minimal APIs – Creating REST Services 4. Chapter 3: Writing Data to Relational and NoSQL Databases 5. Chapter 4: Creating Libraries for Client Applications 6. Part 2: Hosting and Deploying
7. Chapter 5: Containerization of Microservices 8. Chapter 6: Microsoft Azure for Hosting Applications 9. Chapter 7: Flexible Configurations 10. Chapter 8: CI/CD – Publishing with GitHub Actions 11. Chapter 9: Authentication and Authorization with Services and Clients 12. Part 3: Troubleshooting and Scaling
13. Chapter 10: All About Testing the Solution 14. Chapter 11: Logging and Monitoring 15. Chapter 12: Scaling Services 16. Part 4: More communication options
17. Chapter 13: Real-Time Messaging with SignalR 18. Chapter 14: gRPC for Binary Communication 19. Chapter 15: Asynchronous Communication with Messages and Events 20. Chapter 16: Running Applications On-Premises and in the Cloud 21. Index 22. Other Books You May Enjoy

Scaling up or scaling out services

Let’s run the test with 50 virtual users and compare how the performance differs when increasing CPU and memory, as well as increasing the number of replicas.

Configuring scaling up

To scale up, we must increase the CPU and memory values.

Note

When using azd up to create a Container App, a consumption-based environment is created. There’s also the option to create a workload profile with dedicated hardware. When using dedicated hardware, you can choose the type of virtual machine that will be used. At the time of writing this book, the virtual machines were in categories D (general purpose, 4 – 32 cores, 16 – 128 GiB memory) and E (memory optimized 4 – 32 cores, 32 – 256 GiB memory, and GPU enabled with up to 4 GPUs). The type of machine also defines the available network bandwidth. Depending on the workload you have, there are great options available.

To change CPU and memory in the Azure portal...

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 €14.99/month. Cancel anytime}