Alternatives to macOS logo

Alternatives to macOS

Windows, iOS, Ubuntu, Windows 10, and Linux are the most popular alternatives and competitors to macOS.
896
537
+ 1
6

What is macOS and what are its top alternatives?

macOS is a widely-used operating system developed by Apple Inc. known for its user-friendly interface, seamless integration with other Apple devices, and robust security features. Key features include Siri voice assistant, iCloud integration, and macOS App Store. However, macOS is limited in terms of customization options compared to other operating systems.

  1. Ubuntu: Ubuntu is a popular open-source Linux distribution known for its stability, security, and large community support. Key features include regular updates, a vast software repository, and customization options. Pros include high stability and security, while cons include a learning curve for new users.
  2. Windows 10: Windows 10 is a widely-used operating system by Microsoft known for its compatibility with a wide range of software and hardware. Key features include Cortana, Windows Store, and gaming support. Pros include broad software compatibility, while cons include occasional stability issues.
  3. Chrome OS: Chrome OS is a lightweight operating system developed by Google designed for web-based applications. Key features include seamless integration with Google services, fast boot times, and automatic updates. Pros include simplicity and fast performance, while cons include limited offline capabilities.
  4. Fedora: Fedora is a community-driven Linux distribution known for its bleeding-edge software and frequent updates. Key features include GNOME desktop environment, RPM package management, and developer-friendly tools. Pros include cutting-edge software, while cons include potential stability issues.
  5. Elementary OS: Elementary OS is a Linux distribution known for its sleek and user-friendly interface inspired by macOS. Key features include Pantheon desktop environment, AppCenter, and focus on simplicity. Pros include elegant design, while cons include limited software availability.
  6. Manjaro: Manjaro is a user-friendly Linux distribution based on Arch Linux known for its rolling release model and access to Arch User Repository. Key features include easy installation, customizable desktop environments, and up-to-date software. Pros include cutting-edge software, while cons include potential instability.
  7. Kubuntu: Kubuntu is an Ubuntu derivative featuring KDE Plasma desktop environment known for its customization options and visual appeal. Key features include KDE applications, Plasma widgets, and integration with Ubuntu repositories. Pros include highly customizable desktop, while cons include resource-intensive compared to other desktop environments.
  8. Linux Mint: Linux Mint is a user-friendly Linux distribution known for its out-of-the-box multimedia support and ease of use. Key features include Cinnamon desktop environment, Linux Mint Software Manager, and stability. Pros include user-friendly experience, while cons include slower release cycle for updates.
  9. OpenSUSE: OpenSUSE is a Linux distribution known for its YaST configuration tool, high level of control over system settings, and stability. Key features include KDE and GNOME desktop environments, software repositories, and openSUSE Build Service. Pros include robust system management tools, while cons include a smaller community compared to other distributions.
  10. FreeBSD: FreeBSD is a Unix-like operating system known for its advanced networking capabilities, ZFS file system, and scalability. Key features include port system for installing software, jails for system partitioning, and strong security features. Pros include strong networking performance, while cons include potential compatibility issues with certain hardware.

Top Alternatives to macOS

  • Windows
    Windows

    A series of personal computer operating systems produced by Microsoft as part of its Windows NT family of operating systems. ...

  • iOS
    iOS

    It is the operating system that presently powers many of the mobile devices, including the iPhone, iPad, and iPod Touch. It is designed to make your iPhone and iPad experience even faster, more responsive, and more delightful. ...

  • Ubuntu
    Ubuntu

    Ubuntu is an ancient African word meaning ‘humanity to others’. It also means ‘I am what I am because of who we all are’. The Ubuntu operating system brings the spirit of Ubuntu to the world of computers. ...

  • Windows 10
    Windows 10

    It is the latest iteration of the Microsoft operating systems and has been optimized for home PC performance in a wide variety of applications from serious work to after-hours gaming. ...

  • Linux
    Linux

    A clone of the operating system Unix, written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. It aims towards POSIX and Single UNIX Specification compliance. ...

  • Mac OS X
    Mac OS X

    It brings new features inspired by its most powerful users, but designed for everyone. Stay better focused on your work in Dark Mode. Automatically organize files using Stacks. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

macOS alternatives & related posts

Windows logo

Windows

1K
771
3
A group of several graphical operating system families, all of which are developed by Microsoft
1K
771
+ 1
3
PROS OF WINDOWS
  • 3
    Lovely
CONS OF WINDOWS
  • 2
    Proprietary
  • 1
    Not free to use

related Windows posts

Shared insights
on
UnityUnityElectronElectronmacOSmacOSWindowsWindows

We want to create a 3D web and desktop(Windows and macOS) application with a lot of functionalities. This is a 3D furniture customization application in which we give options to add, delete, scale, move, rotate objects. Something like a floor planner. We are also going to add AR and VR.

I am thinking about using Electron or Unity. Please recommend what should I choose for this purpose. Please consider that we have to develop for web and desktop (windows and mac) all platforms.

See more

Actually, I'll add, C++ and C# as well.

Well, I'm into Computer Science since 1996, so I understand a bit of everything plus a lot of different OSs, I study 10 hours per day every day. However back in the 90s we didn't have books or universities about programming, all were passed through if you knew somebody in that profession. Which I did and in that time, he showed me .NET and MySQL, and that offered a lot of jobs also Java. Today you have a lot of options but I'm already discarding new languages as I believe they will jot succeed.

My always dream was to create game, and software. I don't understand all programming concepts and I'm studying all languages at the same time, so I'm heavy loaded. But that keeps me more aware.

I made a choice: use Python for everything but if you want performance, apps, security, compatibility, Multiplatform. What should I choose? The real question here is: which language should I go 100% and that language will teach me all I need about programming BUT without getting lost in that language forever (I discard any Assembly possibility) and one that has full documentation, support and libraries.

In my experience: I found a lot of info for python and java. But hardly I have ever found anything for C lang, C++ and, what about C# (it's only for Windows, is it easy, I saw a lot of documentation). Thanks!!

See more
iOS logo

iOS

1.9K
1.5K
4
A mobile operating system by Apple
1.9K
1.5K
+ 1
4
PROS OF IOS
  • 2
    Integrated with other Apple products
  • 1
    Privacy
  • 1
    Apple
CONS OF IOS
    Be the first to leave a con

    related iOS posts

    Hello,

    We're just brainstorming for the moment and we have a few questions.

    We have an idea for an app that we want to develop, here are the prerequisites:

    1) cross-platform (iOS, Android, and website);

    2) as easy to maintain as possible / well documented / widely used;

    3) Visual Studio Code and Copilot compatible;

    4) Text to speech;

    5) Speech recognition;

    6) Running in background (screen off with TTS and speech recognition);

    7) could be using TypeScript;

    8) Monetized through ad and in-App payment for premium version;

    9) Display on lock screen (Android only I guess)

    So what would you recommend?

    I've been trying to review the options available, and I've considered:

    • NativeScript

    • React Native

    • Flutter

    • Any other?

    Thanks in advance for your help, and I'm open to any comments.

    See more
    Ubuntu logo

    Ubuntu

    77.4K
    57K
    468
    The leading OS for PC, tablet, phone and cloud
    77.4K
    57K
    + 1
    468
    PROS OF UBUNTU
    • 230
      Free to use
    • 96
      Easy setup for testing discord bot
    • 57
      Gateway Linux Distro
    • 54
      Simple interface
    • 9
      Don't need driver installation in most cases
    • 6
      Open Source
    • 6
      Many active communities
    • 3
      Software Availability
    • 3
      Easy to custom
    • 2
      Many flavors/distros based on ubuntu
    • 1
      Lightweight container base OS
    • 1
      Great OotB Linux Shell Experience
    CONS OF UBUNTU
    • 5
      Demanding system requirements
    • 4
      Adds overhead and unnecessary complexity over Debian
    • 2
      Snapd installed by default
    • 1
      Systemd

    related Ubuntu posts

    CDG

    I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

    Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

    As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

    To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

    CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

    Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

    See more
    Tassanai Singprom

    This is my stack in Application & Data

    JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

    My Utilities Tools

    Google Analytics Postman Elasticsearch

    My Devops Tools

    Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

    My Business Tools

    Slack

    See more
    Windows 10 logo

    Windows 10

    405
    374
    13
    The most secure Windows ever built
    405
    374
    + 1
    13
    PROS OF WINDOWS 10
    • 3
      On 4gb other applications less likely to run smoothly
    • 3
      Slow
    • 2
      Best for Indonesian PC Users
    • 2
      The best developer tools for all devices
    • 1
      Editors choice. But not suitable on 4gb ram. Alth
    • 1
      Complies with JIS Standard
    • 1
      Great is if you have 8b ram and a 128gb ssd minimum
    CONS OF WINDOWS 10
    • 3
      Lags really much on low end devices
    • 3
      Slow, slow and slow
    • 2
      Worst OS to run on 2GB of RAM
    • 1
      Acts posh
    • 1
      Can't fix bugs yourself

    related Windows 10 posts

    Shared insights
    on
    Windows 10Windows 10C#C#Visual StudioVisual Studio

    Visual Studio 2019 keeps rendering only part of my project. I changed from 200% dpi to 100% and it is still doing this. Any ideas?

    Razer Blade Stealth Intel 7th gen i7 8550u

    A little more info, I'm trying to make my GUI my self in WPF C# so I turned off FormBorderStyle

    I have Windows 10 Pro Installed which Home is usually the go-to.

    I'm going to uninstall and reinstall and see if that does anything. Fingers crossed, I was looking for a more concrete solution though. :x

    See more
    Justin Dorfman
    Open Source Program Manager at Reblaze · | 3 upvotes · 39.1K views

    I have been using macOS for 12 years. I can't imagine switching to another operating system since I have all of my hotkeys memorized. Windows 10 has made some drastic improvements like adding GNU Bash/Linux to win developers over from unix-like systems, I just don't feel it is there yet. Maybe I'll give it a shot next time I need a new laptop. 🤷‍♂️

    See more
    Linux logo

    Linux

    2.9K
    2.3K
    41
    A family of free and open source software operating systems based on the Linux kernel
    2.9K
    2.3K
    + 1
    41
    PROS OF LINUX
    • 17
      Open Source
    • 11
      Free
    • 8
      Reliability
    • 5
      Safe
    CONS OF LINUX
      Be the first to leave a con

      related Linux posts

      I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.

      • It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.

      • Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (.rpm and .deb packages)

      • LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.

      • Extended language support: Supports by default the majority of the most used languages and syntax like JavaScript, HTML, C#, Swift, Java, PHP, Python and others. Also, VS Code supports different file types associated to projects like .ini, .properties, XML and JSON files.

      • Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.

      • Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.

      • Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)

      See more
      Wesly Nouse

      We use G Suite because of its cheap costs, easy management/administration, Excellent DKIM score, and everything that comes with it. We switched from Microsoft Office 365 because it doesn't work on Linux which is our OS of choice. Furthermore, G Suite does not lack any of the features that Office365 had to offer, I'd even say it offers more.

      See more
      Mac OS X logo

      Mac OS X

      282
      197
      2
      A desktop operating system for Macintosh computers
      282
      197
      + 1
      2
      PROS OF MAC OS X
      • 1
        Stability
      • 1
        Elegant, Minimalist look
      CONS OF MAC OS X
      • 2
        Expensive if you don't want to break the EULA
      • 1
        Even less customization

      related Mac OS X posts

      JavaScript logo

      JavaScript

      351.1K
      267.3K
      8.1K
      Lightweight, interpreted, object-oriented language with first-class functions
      351.1K
      267.3K
      + 1
      8.1K
      PROS OF JAVASCRIPT
      • 1.7K
        Can be used on frontend/backend
      • 1.5K
        It's everywhere
      • 1.2K
        Lots of great frameworks
      • 896
        Fast
      • 745
        Light weight
      • 425
        Flexible
      • 392
        You can't get a device today that doesn't run js
      • 286
        Non-blocking i/o
      • 237
        Ubiquitousness
      • 191
        Expressive
      • 55
        Extended functionality to web pages
      • 49
        Relatively easy language
      • 46
        Executed on the client side
      • 30
        Relatively fast to the end user
      • 25
        Pure Javascript
      • 21
        Functional programming
      • 15
        Async
      • 13
        Full-stack
      • 12
        Its everywhere
      • 12
        Future Language of The Web
      • 12
        Setup is easy
      • 11
        JavaScript is the New PHP
      • 11
        Because I love functions
      • 10
        Like it or not, JS is part of the web standard
      • 9
        Expansive community
      • 9
        Can be used in backend, frontend and DB
      • 9
        Easy
      • 9
        Everyone use it
      • 8
        Most Popular Language in the World
      • 8
        Can be used both as frontend and backend as well
      • 8
        Powerful
      • 8
        For the good parts
      • 8
        No need to use PHP
      • 8
        Easy to hire developers
      • 7
        Love-hate relationship
      • 7
        Agile, packages simple to use
      • 7
        Its fun and fast
      • 7
        Hard not to use
      • 7
        Nice
      • 7
        Versitile
      • 7
        Evolution of C
      • 7
        Photoshop has 3 JS runtimes built in
      • 7
        It's fun
      • 7
        Popularized Class-Less Architecture & Lambdas
      • 7
        Supports lambdas and closures
      • 6
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 6
        1.6K Can be used on frontend/backend
      • 6
        Client side JS uses the visitors CPU to save Server Res
      • 6
        It let's me use Babel & Typescript
      • 6
        Easy to make something
      • 5
        What to add
      • 5
        Clojurescript
      • 5
        Stockholm Syndrome
      • 5
        Function expressions are useful for callbacks
      • 5
        Scope manipulation
      • 5
        Everywhere
      • 5
        Client processing
      • 5
        Promise relationship
      • 4
        Because it is so simple and lightweight
      • 4
        Only Programming language on browser
      • 1
        Easy to learn
      • 1
        Not the best
      • 1
        Hard to learn
      • 1
        Easy to understand
      • 1
        Test
      • 1
        Test2
      • 1
        Subskill #4
      • 0
        Hard 彤
      CONS OF JAVASCRIPT
      • 22
        A constant moving target, too much churn
      • 20
        Horribly inconsistent
      • 15
        Javascript is the New PHP
      • 9
        No ability to monitor memory utilitization
      • 8
        Shows Zero output in case of ANY error
      • 7
        Thinks strange results are better than errors
      • 6
        Can be ugly
      • 3
        No GitHub
      • 2
        Slow

      related JavaScript posts

      Zach Holman

      Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

      But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

      But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

      Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

      See more
      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.1M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Git logo

      Git

      290K
      174.3K
      6.6K
      Fast, scalable, distributed revision control system
      290K
      174.3K
      + 1
      6.6K
      PROS OF GIT
      • 1.4K
        Distributed version control system
      • 1.1K
        Efficient branching and merging
      • 959
        Fast
      • 845
        Open source
      • 726
        Better than svn
      • 368
        Great command-line application
      • 306
        Simple
      • 291
        Free
      • 232
        Easy to use
      • 222
        Does not require server
      • 27
        Distributed
      • 22
        Small & Fast
      • 18
        Feature based workflow
      • 15
        Staging Area
      • 13
        Most wide-spread VSC
      • 11
        Role-based codelines
      • 11
        Disposable Experimentation
      • 7
        Frictionless Context Switching
      • 6
        Data Assurance
      • 5
        Efficient
      • 4
        Just awesome
      • 3
        Github integration
      • 3
        Easy branching and merging
      • 2
        Compatible
      • 2
        Flexible
      • 2
        Possible to lose history and commits
      • 1
        Rebase supported natively; reflog; access to plumbing
      • 1
        Light
      • 1
        Team Integration
      • 1
        Fast, scalable, distributed revision control system
      • 1
        Easy
      • 1
        Flexible, easy, Safe, and fast
      • 1
        CLI is great, but the GUI tools are awesome
      • 1
        It's what you do
      • 0
        Phinx
      CONS OF GIT
      • 16
        Hard to learn
      • 11
        Inconsistent command line interface
      • 9
        Easy to lose uncommitted work
      • 7
        Worst documentation ever possibly made
      • 5
        Awful merge handling
      • 3
        Unexistent preventive security flows
      • 3
        Rebase hell
      • 2
        When --force is disabled, cannot rebase
      • 2
        Ironically even die-hard supporters screw up badly
      • 1
        Doesn't scale for big data

      related Git posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.3M 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.
      See more
      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 23 upvotes · 8.3M views

      Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

      It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

      I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

      We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

      If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

      The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

      Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

      See more