Need advice about which tool to choose?Ask the StackShare community!
Add tool
Decisions about Dapr and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.7M views
Our whole DevOps stack consists of the following tools:
- GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
- Respectively Git as revision control system
- SourceTree as Git GUI
- Visual Studio Code as IDE
- CircleCI for continuous integration (automatize development process)
- Prettier / TSLint / ESLint as code linter
- SonarQube as quality gate
- Docker as container management (incl. Docker Compose for multi-container application management)
- VirtualBox for operating system simulation tests
- Kubernetes as cluster management for docker containers
- Heroku for deploying in test environments
- nginx as web server (preferably used as facade server in production environment)
- SSLMate (using OpenSSL) for certificate management
- Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
- PostgreSQL as preferred database system
- Redis as preferred in-memory database/store (great for caching)
The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:
- Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
- Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
- Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
- Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
- Scalability: All-in-one framework for distributed systems.
- Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn MorePros of Dapr
Pros of Kubernetes
Pros of Dapr
- Manage inter-service state3
- MTLS "for free"2
- App dashboard for rapid log overview2
- Zipkin app tracing "for free"2
Pros of Kubernetes
- Leading docker container management solution161
- Simple and powerful126
- Open source103
- Backed by google75
- The right abstractions56
- Scale services24
- Replication controller19
- Permission managment10
- Cheap7
- Supports autoscaling7
- Simple7
- Reliable4
- Self-healing4
- No cloud platform lock-in4
- Quick cloud setup3
- Open, powerful, stable3
- Scalable3
- Promotes modern/good infrascture practice3
- Captain of Container Ship2
- A self healing environment with rich metadata2
- Cloud Agnostic2
- Runs on azure2
- Backed by Red Hat2
- Custom and extensibility2
- Golang1
- Expandable1
- Gke1
- Easy setup1
- Sfg1
- Everything of CaaS1
Sign up to add or upvote prosMake informed product decisions
Cons of Dapr
Cons of Kubernetes
Cons of Dapr
Be the first to leave a con
Cons of Kubernetes
- Poor workflow for development15
- Steep learning curve14
- Orchestrates only infrastructure7
- High resource requirements for on-prem clusters4
- Too heavy for simple systems2
- Additional Technology Overhead1
- More moving parts to secure1
- Additional vendor lock-in (Docker)1
Sign up to add or upvote consMake informed product decisions
- No public GitHub repository available -
What is Dapr?
It is a portable, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
What is Kubernetes?
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Need advice about which tool to choose?Ask the StackShare community!
Jobs that mention Dapr and Kubernetes as a desired skillset
What companies use Dapr?
What companies use Kubernetes?
What companies use Dapr?
See which teams inside your own company are using Dapr or Kubernetes.
Sign up for StackShare EnterpriseLearn MoreSign up to get full access to all the companiesMake informed product decisions
What tools integrate with Dapr?
What tools integrate with Kubernetes?
What tools integrate with Dapr?
What tools integrate with Kubernetes?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+1 2
1326
+2 2
1066
+9 2
3701
+11 2
2134
+11 5
6145
+7 3
761
+12 4
1351
+2 2
831
What are some alternatives to Dapr and Kubernetes?
Istio
Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.
Akka
Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.
Orleans
Orleans is a framework that provides a straightforward approach to building distributed high-scale computing applications, without the need to learn and apply complex concurrency or other scaling patterns. It was created by Microsoft Research and designed for use in the cloud.
Knative
Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center
Envoy
Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.