Cloud Native Day: Cloud-native Anwendungsentwicklung im Jahr 2021

Cloud-native Anwendungsentwicklung im
Jahr 2021
Cloud Native Day, 10. Februar 2021

Nico Meisenzahl
• Senior Cloud & DevOps Consultant at white duck
• GitLab Hero, Microsoft MVP & Docker Community
Leader
• Container, Kubernetes & Cloud-Native
© white duck GmbH 2021
Phone: +49 8031 230159 0
Email: nico.meisenzahl@whiteduck.de
Twitter: @nmeisenzahl
LinkedIn: https://www.linkedin.com/in/nicomeisenzahl
Blog: https://meisenzahl.org

Martin Brandl
• Head of Cloud Development & Operations, CSA
• Microsoft Azure MVP
• Cloud-Native, Azure
Phone: +49 8031 230159 0
Email: martin.brandl@whiteduck.de
Twitter: @martin_jib
LinkedIn: https://www.linkedin.com/in/mbrandl
Blog: https://about-azure.com

Agenda
• Microservices are great, but also challenging
• Distributed Application Runtime – Dapr
• Service Mesh interface – SMI

Microservices are great, but also challenging
• a microservice should mostly contain business code and
nothing further
• this is hard and mostly not the case
• polyglot microservices can help streamline your business
but will also introduce complexity
• different languages and therefore different implementations and
libraries
• service-to-service communication for example
• Observability & distributed tracing

Abstraction can help
• we abstracted our …
• communication/backend with libraries and SDKs
• relational database with object-relational mapping
• infrastructure with containers
• container management with Kubernetes
• why not abstracting even further?
• that said, abstraction can also introduce more complexity

Distributed Application Runtime – Dapr
Service-
to- service
invocation
State
management
Publish
and
subscribe
Resource
bindings
and triggers
Actors Distributed
tracing
Secrets Extensible
Any cloud or edge infrastructure
HTTP API gRPC API
Application code
Microservices written in
Any code or framework…

Sidecar &
components
State stores
Publish & subscribe
Bindings
Scanning
for events
Messaging
Load and
save state
Input/output
Dapr API
Dapr API
Service
code B
Service
code A
Application
Sidecar Sidecar
Secure communication with mTLS
Tracing, logs
and metrics
Tracing, logs
and metrics
Observability
Prometheus AppInsightts Jaeger
Capturing, querying
traces, logs and metrics

Service invocation
“frontend”
“cart”
Post
http://localhost:3500/v1.0/invoke/cart/method/checkout
{
"user":"johndoe",
"cart":"0001"
}
Post
http://10.0.0.2:8000/checkout
{
"user":"johndoe",
"cart":"0001"
}

State management
App
“myApp”
{
"name": "Tatooine"
}
Get
http://localhost:3500/v1.0/state/<store-name>/planet
Post
http://localhost:3500/v1.0/state/<store-name>
[{
"key": "weapon",
"value": "DeathStar"
}, {
"key": "planet",
"value": {
"name": "Tatooine"
}
}]
key value
myApp-weapon "DeathStar"
myApp-planet {
"name": "Tatooine"
}
State store of your choice

Publish and subscribe
Subscribe
Publish
Post
http://localhost:3500/v1.0/publish/
"topic":"order",
"data":{
"user":"johndoe",
"item":"ZeroDay"
},
“cart” “shipping”
Post
http://10.0.0.5:8005/order
"data":{
"user":"johndoe",
"item":"ZeroDay"
}
“email”
Post
http://10.0.0.4:8004/order

How Dapr is run
Kubernetes
apiVersion: apps/v1
kind: Deployment
…
spec:
selector:
matchLabels:
app: my-app
template:
metadata:
annotations:
dapr.io/enabled: "true"
dapr.io/app-id: "my-appr"
dapr.io/app-protocol: ”http"
dapr.io/app-port: ”8080”
…
Standalone (self-hosted)
dapr run --app-id my-app
--app-protocol grpc
--app-port 50105
--components-path ./config
go run main.go
dapr run --app-id my-app
--app-protocol http
--app-port 3000
--components-path ./config
dotnet run

Service Meshes
• this talk is not about why you should or should not use a
Service Mesh
• it‘s more about how to abstract a Service Mesh in case
you decided to use one

The Service Mesh ecosystem (2019 vs 2020)
https://www.cncf.io/wp-content/uploads/2020/08/CNCF_Survey_Report.pdf
https://www.cncf.io/wp-content/uploads/2020/11/CNCF_Survey_Report_2020.pdf

Service Mesh interface – SMI
• „A standard interface (API spec) for service meshes
on Kubernetes.“
• like Open Container Initiative (OCI), Container Network
Interface (CNI), Container Storage Interface (CSI) just for
Services Meshes

Service Mesh interface – SMI
• a basic feature set for the most common mesh use cases
• flexibility to support new mesh capabilities over time
• allows abstractions for integrations
• Dashboards, canary release tools, …
• allows to change a Service Mesh implementation without
changing the configuration
• is a CNCF sandbox project
• https://smi-spec.io

SMI feature set
• traffic management – shift traffic between different
services
• traffic policy – apply policies like identity and transport
encryption across services
• traffic telemetry – capture key metrics like error rate and
latency between services

SMI Ecosystem

SMI spec in detail
• Traffic Split
• Traffic Specs
• Traffic Access Control
• Traffic Metrics

Things to keep in mind
• some things are in early stages…
• Istio requires an adapter
• https://github.com/servicemeshinterface/smi-adapter-istio
• does not yet support the latest Istio versions
• metrics requires extending the Kubernetes API
• https://github.com/servicemeshinterface/smi-metrics
• support for Istio and Linkerd (Consul and Open Service Mesh are
planed)
• be aware of the different API versions

SMI Community
• bi-weekly Community call
• Wednesday, 10 PST
• CNCF Slack
• #smi channel
• more details
• https://github.com/servicemeshinterface/smi-spec#communications

Questions?
• Slides
• https://www.slideshare.net/nmeisenzahl

Cloud Native Day: Cloud-native Anwendungsentwicklung im Jahr 2021

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Cloud Native Day: Cloud-native Anwendungsentwicklung im Jahr 2021

Similaire à Cloud Native Day: Cloud-native Anwendungsentwicklung im Jahr 2021 (20)

Plus de Nico Meisenzahl

Plus de Nico Meisenzahl (11)

Dernier

Dernier (20)

Cloud Native Day: Cloud-native Anwendungsentwicklung im Jahr 2021