Need advice about which tool to choose?Ask the StackShare community!
Kubernetes vs Visual Studio: What are the differences?
Developers describe Kubernetes as "Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops". 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. On the other hand, Visual Studio is detailed as "State-of-the-art tools and services that you can use to create great apps for devices, the cloud, and everything in between". Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications.
Kubernetes can be classified as a tool in the "Container Tools" category, while Visual Studio is grouped under "Integrated Development Environment".
"Leading docker container management solution", "Simple and powerful" and "Open source" are the key factors why developers consider Kubernetes; whereas "Intellisense, ui", "Complete ide and debugger" and "Plug-ins" are the primary reasons why Visual Studio is favored.
Kubernetes is an open source tool with 54.2K GitHub stars and 18.8K GitHub forks. Here's a link to Kubernetes's open source repository on GitHub.
Google, DigitalOcean, and 9GAG are some of the popular companies that use Kubernetes, whereas Visual Studio is used by Microsoft, Intuit, and OpenTable. Kubernetes has a broader approval, being mentioned in 1018 company stacks & 1060 developers stacks; compared to Visual Studio, which is listed in 657 company stacks and 979 developer stacks.
Hello, we have a bunch of local hosts (Linux and Windows) where Docker containers are running with bamboo agents on them. Currently, each container is installed as a system service. Each host is set up manually. I want to improve the system by adding some sort of orchestration software that should install, update and check for consistency in my docker containers. I don't need any clouds, all hosts are local. I'd prefer simple solutions. What orchestration system should I choose?
If you just want the basic orchestration between a set of defined hosts, go with Docker Swarm. If you want more advanced orchestration + flexibility in terms of resource management and load balancing go with Kubernetes. In both cases, you can make it even more complex while making the whole architecture more understandable and replicable by using Terraform.
The problem I have is whether to choose Android Studio or Visual Studio? I have to develop a simple app for a school project that can work on both iPhone and Android.
The most important factors for me are Android and iOS compatibility. Although note that i would like to become a Software Engineer when i finish my course. (I'd like to work for Apple, just saying!)
After that id like easy integration for Google Ads and such if i do develop another app that people actually use to support development. (I'd also like to stick with one easy programming language that's compatible with a wide variety of platforms since i'm a beginner and have only ever used Pascal)
First of all - Android Studio and Visual Studio are IDE's. Tools to create code. What you are asking is programming framework. I assume that when you are talking about Android Studio you mean Native Android Development and by Visual Studio you mean Xamarin.
If you want to create crossplatform app then Native Android Development is NOT a way to go. Xamarin might work for you, BUT - you'd rather recommend you to go with Flutter. It's much more performant than Xamarin, programming model is friendlier for developer and technology seems just more refined. It's also officially supported by google, so no worries about support.
We develop rapidly with docker-compose orchestrated services, however, for production - we utilise the very best ideas that Kubernetes has to offer: SCALE! We can scale when needed, setting a maximum and minimum level of nodes for each application layer - scaling only when the load balancer needs it. This allowed us to reduce our devops costs by 40% whilst also maintaining an SLA of 99.87%.
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.
Pros of Kubernetes
- Leading docker container management solution166
- Simple and powerful129
- Open source107
- Backed by google76
- The right abstractions58
- Scale services25
- Replication controller20
- Permission managment11
- Supports autoscaling9
- Simple8
- Cheap8
- Self-healing6
- Open, powerful, stable5
- Reliable5
- No cloud platform lock-in5
- Promotes modern/good infrascture practice5
- Scalable4
- Quick cloud setup4
- Custom and extensibility3
- Captain of Container Ship3
- Cloud Agnostic3
- Backed by Red Hat3
- Runs on azure3
- A self healing environment with rich metadata3
- Everything of CaaS2
- Gke2
- Golang2
- Easy setup2
- Expandable2
- Sfg2
Pros of Visual Studio
- Intellisense, ui305
- Complete ide and debugger244
- Plug-ins165
- Integrated104
- Documentation93
- Fast37
- Node tools for visual studio (ntvs)35
- Free Community edition33
- Simple24
- Bug free17
- Made by Microsoft8
- Full free community version6
- JetBrains plugins (ReSharper etc.) work sufficiently OK5
- Productivity Power Tools3
- Vim mode2
- VIM integration2
- I develop UWP apps and Intellisense is super useful1
- Cross platform development1
- The Power and Easiness to Do anything in any.. language1
- Available for Mac and Windows1
Sign up to add or upvote prosMake informed product decisions
Cons of Kubernetes
- Steep learning curve16
- Poor workflow for development15
- Orchestrates only infrastructure8
- High resource requirements for on-prem clusters4
- Too heavy for simple systems2
- Additional vendor lock-in (Docker)1
- More moving parts to secure1
- Additional Technology Overhead1
Cons of Visual Studio
- Bulky16
- Made by Microsoft14
- Sometimes you need to restart to finish an update6
- Too much size for disk3
- Only avalible on Windows3