"Building Future-Ready Apps with .NET 8 and Azure Serverless Ecosystem", Stanislav Lebedenko.pdf

.NET 8 brought a lot of improvements for developers and maturity to the Azure serverless container ecosystem. So, this talk will cover these changes and explain how you can apply them to your projects. Another reason for this talk is the re-invention of Serverless from a DevOps perspective as a Platform Engineering trend with Backstage and the recent Radius project from Microsoft. So now is the perfect time to look at developer productivity tooling and serverless apps from Microsoft's perspective.

1. Building Future-Ready Apps:
.NET 8 and Azure Serverless Ecosystem
Stanislav Lebedenko
Cloud architect @Solidify

2. ■20+ years in TECH
■Microsoft Azure MVP
■Cloud architect & MCT
■#MSUGODUA & IT2SCHOOL
■Mentor and Engineer
■Working @Solidify AB
■Have different perspective
■Your friend and neighbor :)
BIO

3. Agenda
1.Bigger picture
2..NET 8 maturity
3.Azure Container Apps maturity
4.Azure functions maturity
5.App platform maturity
6.Summary and obstacles

4. Bigger picture

5. Bigger picture

6. Responsibilities

7. Comfort zone

8. .NET Maturity

9. Native ahead-of-time compilation

10. Native resilience

11. .NET Aspire

12. Integration testing -.NET Aspire

13. Integration testing -Testcontainers

14. Container maturity

15. Chiseled containers

16. Azure Container Apps (ACA)

17. ACA sample architecture

18. ■Developer centric
■No DevOps overhead
■Fast time-to-market
■No vendor lock*
■DAPR/KEDA/Envoy powered
■Perfect abstraction over K8s
■Operation centric
■Orchestration problem
■Patching problem
■Security hardening
■Complex network
■CPU/Memory/GPU intensive apps
Azure Container Apps vs Kubernetes
Serverless Kubernetes

19. Element Description
Plans Consumption -serverless with instance size limit
Dedicated -fully managed with CPU/Memory/GPU optimized compute
Environment (VNet) Two types -Workload profiles and Consumption (internal/public)
Provides secure network boundary around apps and jobs.
Containers Linux-based x86-64, app revisions, sidecars in single app, init containers, job templates
Revisions Immutable, versioned, historical revisions, multiple revisions concurrent run, blue/green
Jobs Single unit-of-work with finite duration, manual/scheduled/event based start
Network Limited auto VNet, full functionality with existing VNet + Dedicated environment
Resiliency Timeouts, Retries, Circuit breakers, Connection pools
Replica (K8s Pod) Instance of microservice or Kubernetes Pod
ACA key elements

20. ACA/DAPR Resiliency

21. ACA Dapr pubsub component Kubernetes Dapr pubsub component
Manifest difference

22. ■Containerizing legacy IIS apps
■Lifting Actors to cloud
■New service for existing solution
■Downgrade with simple integrations
■Batch jobs with complex workloads
■Lifting CPU/Memory heavy Functions
■Cheap dev/stage environments
■Portability to other clouds/platforms
Scenarios

23. Future

24. Functions maturity

25. ■Isolated worker model only from 2026
■New Flex Consumption plan
Network, instance size & concurrency
■<PublishReadyToRun>true</PublishReadyToRun>
<PublishAot>true</PublishAot>
■Functions on Container Apps
■DAPR triggers only for ACA and K8s
■Unification of .NET app boilerplate
■Functions scaler intro to App Service
Azure Functions

26. Isolated worker startup

27. Roadmap

28. App platform maturity

29. Radius project –Platform abstraction

30. Demo

31. ■Developer centric .NET tool
■Using specific dependencies
■For building distributed .NET apps
■Apps Integration testing
■Lessons from .NET Tyeproject
■One Visual Studio to rule them all
■Platform engineer centric
■Abstracting dependencies
■Defining platform setup
■Cloud agnostic
■BICEP as language
■Templates & guardrails
Aspire vs Radius
.NET Aspire Radius project

32. Summary and obstacles

33. Serverless containers

34. Bigger picture

35. Thank you!
LinkedInTwitterGitHub