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

Concepts

Programming Language

Author (1):

Christian Nagel

Table of Contents (23) Chapters

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

Why subscribe?

22. Other Books You May Enjoy

Using Aspir8 to deploy to Kubernetes

With .NET Aspire, we created the app model to define all the dependencies between the different resources that are used. First, in Chapter 1, you saw the Aspire manifest that’s created from an app model. This manifest file is independent of any technology where to deploy it. The Azure Developer CLI creates Bicep scripts for deploying the solution (see Chapter 6 and Chapter 8). The open source tool Aspirate (Aspir8) (see https://github.com/prom3theu5/aspirational-manifests) converts the Aspire manifest file to Docker Compose or Kubernetes with Helm charts or kustomize manifests.

You can create an Aspire manifest for every launch profile, like so:

cd Codebreaker.AppHost
dotnet run --launch-profile OnPremises -- --publisher manifest --output-path onpremises-manifest.json

Our app model is defined with two different versions. One version uses cloud-native Azure services, while the other option is independent of any cloud environment....