The document discusses different architectural styles including monolith, microservices architecture (MSA), serverless functions, and hybrid architectures. It also covers common concerns for MSA including configuration management, service discovery, load balancing, API gateways, security, logging, metrics, tracing, resilience, auto-scaling, packaging and more. Specific technologies mentioned that address these concerns include Spring Cloud, Netflix OSS, Kubernetes, Eureka, Ribbon, Zuul and others.

2. + Simplified Arch.
+ Less to deploy.
+ Less to manage.
- Inflexible.
- Slow updates.
SOA
MSA
Canonical
(Container Based)
Serverless FaaS
(Platform)
Monolith
+ Separation of Concerns
+ Specular to business
- Pre-cloud
- No infrastructure focus
+ Container-based
+ Reproducible
+ Vendor-agnostic
+ Easy to migrate
+ Scalability
- Manuel Admin
- Running cost
+ Scalability
+ Zero admin
+ cost
- Resource limits
- Size limits
- Vendor lock-in

5. Hybrid Arch?

9. MSA Concern Spring Cloud & Netflix OSS & Kubernetes
Configuration Management Spring Config Server, Netflix Archaius
Service Discovery Spring Cloud Eureka, Consul
Load Balancing Spring Cloud Ribbon
API Gateway Spring Cloud Gateway, Spring Cloud Zuul
Security Concerns Spring Cloud Security (OAuth, Ldap, …)
Centralized Logging EFK/ELK Stack
Centralized Metrics Spring Spectator & Atlas, Prometheus, & Grafana
Distributed Tracing Spring Cloud Sleuth
Resilience and fault tolerance Spring Hystrix, Turbine, & Ribbon
Auto-scaling and self-healing ?
Packaging, deployment, and scheduling Spring Boot, Maven, Gradle, Helm
Job management Spring Batch, Kubernetes Jobs
Singleton Application Spring Cloud Cluster, Kubernetes Pods