Alternatives to BigCommerce logo

Alternatives to BigCommerce

WooCommerce, Magento, Squarespace, Shopify, and Wix are the most popular alternatives and competitors to BigCommerce.
690
93
+ 1
0

What is BigCommerce and what are its top alternatives?

BigCommerce is a popular e-commerce platform that offers a wide range of features including customizable storefront design, built-in marketing tools, multi-channel selling, and seamless integration with various third-party apps. However, some limitations of BigCommerce include limited free themes, transaction fees on lower-tier plans, and a learning curve for beginners.

  1. Shopify: Shopify is a user-friendly e-commerce platform with features like customizable themes, mobile responsiveness, and a wide array of apps. Pros of Shopify include easy setup, robust app store, and excellent customer support. However, cons include transaction fees on lower-tier plans and limited customization options.
  2. WooCommerce: WooCommerce is a WordPress plugin that allows for customized online stores with features like various payment gateways, flexible shipping options, and an extensive library of plugins. Pros of WooCommerce include its integration with WordPress, scalability, and no monthly fees. However, cons include the need for technical knowledge and maintenance.
  3. Magento: Magento is a powerful open-source e-commerce platform with features like advanced SEO capabilities, robust security features, and flexibility for customization. Pros of Magento include high scalability, extensive features, and a strong community support. However, cons include the need for technical expertise and expensive customization.
  4. Wix: Wix is a website builder platform that also offers e-commerce capabilities with features like drag-and-drop design, mobile optimization, and various marketing tools. Pros of Wix include ease of use, beautiful templates, and affordable pricing. However, cons include limited customization and scalability compared to other platforms.
  5. Square Online: Square Online is an e-commerce platform that integrates seamlessly with Square’s point-of-sale system, offering features like inventory management, secure payments, and easy setup. Pros of Square Online include easy integration with Square POS, no monthly fees, and simple pricing. However, cons include limited customization options and transaction fees.
  6. Volusion: Volusion is an e-commerce platform with features like customizable templates, secure hosting, and built-in marketing tools. Pros of Volusion include user-friendly interface, extensive support resources, and affordable pricing. However, cons include transaction fees on lower-tier plans and limited blog capabilities.
  7. 3DCart: 3DCart is an e-commerce platform that offers features like unlimited product listings, various payment gateways, and SEO tools. Pros of 3DCart include robust features, no transaction fees, and excellent customer support. However, cons include limited free templates and some features may require additional fees.
  8. PrestaShop: PrestaShop is an open-source e-commerce platform with features like customizable themes, multilingual support, and a user-friendly interface. Pros of PrestaShop include flexibility for customization, no monthly fees, and a large community of users. However, cons include the need for technical knowledge and potential costs for add-ons.
  9. OpenCart: OpenCart is an open-source e-commerce platform with features like multiple payment gateways, multi-store capability, and an intuitive admin interface. Pros of OpenCart include easy installation, scalability, and a wide range of extensions. However, cons include potential security vulnerabilities and limited customer support.
  10. Weebly: Weebly is a website builder platform that also offers e-commerce features with drag-and-drop design, mobile responsiveness, and integrated marketing tools. Pros of Weebly include easy setup, beautiful templates, and affordable pricing. However, cons include limited customization options and less advanced features compared to other platforms.

Top Alternatives to BigCommerce

  • WooCommerce
    WooCommerce

    WooCommerce is the most popular WordPress eCommerce plugin. And it's available for free. Packed full of features, perfectly integrated into your self-hosted WordPress website. ...

  • Magento
    Magento

    Magento Community Edition is perfect if you’re a developer who wants to build your own solution with flexible eCommerce technology. You can modify the core code and add a wide variety of features and functionality. ...

  • Squarespace
    Squarespace

    Whether you need simple pages, sophisticated galleries, a professional blog, or want to sell online, it all comes standard with your Squarespace website. Squarespace starts you with beautiful designs right out of the box — each handcrafted by our award-winning design team to make your content stand out. ...

  • Shopify
    Shopify

    Shopify powers tens of thousands of online retailers including General Electric, Amnesty International, CrossFit, Tesla Motors, Encyclopaedia Britannica, Foo Fighters, GitHub, and more. Our platform allows users to easily and quickly create their own online store without all the technical work involved in developing their own website, or the huge expense of having someone else build it. Shopify lets merchants manage all aspects of their shops: uploading products, changing the design, accepting credit card orders, and viewing their incoming orders and completed transactions. ...

  • Wix
    Wix

    Creating your stunning website for free is easier than ever. No tech skills needed. Just pick a template, change anything you want, add your images, videos, text and more to get online instantly. ...

  • Weebly
    Weebly

    Weebly is an AJAX website creator that allows you to create pages with template skins and content widgets. Users can easily drag-and-drop content widgets like pictures, text, video and Google Maps in WYSIWYG-fashion. ...

  • 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. ...

BigCommerce alternatives & related posts

WooCommerce logo

WooCommerce

11.2K
4.6K
12
The most popular WordPress eCommerce plugin
11.2K
4.6K
+ 1
12
PROS OF WOOCOMMERCE
  • 12
    Easy to extend and customize
CONS OF WOOCOMMERCE
  • 1
    Slow if not optimized

related WooCommerce posts

Samuel Webster
Principal Developer at Colart · | 7 upvotes · 292K views

We needed our e-commerce platform (built using WooCommerce) to be able to keep products in sync with our #pim (provided by #akeneo) which is built in Symfony . We hooked into the kernel.event_listener to send RabbitMQ messages to a WordPress API endpoint that triggers the updated product to rebuild with fresh data.

See more
Dan Platon
PHP Software Developer · | 5 upvotes · 187.8K views

I'm looking to build an eCommerce website and seeking advice from professionals on the most reliable tech stack that I can use. Currently, the website is built on top of WordPress with WooCommerce, but the company has grown up, and evidently, the number of products have been increased. The site needs a fresh code because WordPress doesn't make it anymore.

The stack I'm most familiar with is PHP + Symfony + MySQL + Apache HTTP Server or NGINX. Headless eCommerce is the one I'm looking for, because of the huge complexity, it would be great to separate the backend from the frontend. Not sure about CMSs, because they had a huge amount of functionality that the application doesn't need. I've been looking also at PrestaShop, it seems ok, but not sure about customization and front-end integration. As a custom solution, I have found Sylius or Aimeos for the backend, but I'm not too sure about a frontend stack.

Could you please give some suggestions about the frontend stack and if the ones for the backend are ok?

See more
Magento logo

Magento

3.1K
861
74
Flexible eCommerce solutions, a vibrant extensions marketplace and an open global ecosystem
3.1K
861
+ 1
74
PROS OF MAGENTO
  • 22
    Open source
  • 14
    Robust
  • 12
    Powerful
  • 10
    Widespread community support
  • 8
    E-commerce made easy
  • 4
    Mature
  • 4
    Flexible
CONS OF MAGENTO
  • 2
    System is too complex
  • 2
    Slow
  • 1
    Processor hungry

related Magento posts

Johnny Bell

I've been in the #frontend game for about 7 years now. I started coding in Sublime Text because all of the tutorials I was doing back then everyone was using it. I found the speed amazing compared to some other tools at the time. I kept using Sublime Text for about 4-5 years.

I find Sublime Text lacks some functionality, after all it is just a text editor rather than a full fledged IDE. I finally converted over to PhpStorm as I was working with Magento and Magento as you know is mainly #PHP based.

This was amazing all the features in PhpStorm I loved, the debugging features, and the control click feature when you click on a dependency or linked file it will take you to that file. It was great.

PhpStorm is kind of slow, I found that Prettier was taking a long time to format my code, and it just was lagging a lot so I was looking for alternatives. After watching some more tutorial videos I noticed that everyone was using Visual Studio Code. So I gave it a go, and its amazing.

It has support for everything I need with the plugins and the integration with Git is amazing. The speed of this IDE is blazing fast, and I wouldn't go back to using PhpStorm anymore. I highly recommend giving Visual Studio Code a try!

See more
Siddhant Sharma
Tech Connoisseur at Channelize.io · | 12 upvotes · 1.1M views

WordPress Magento PHP Java Swift JavaScript

Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

Posting my first article. Please have a look and do give feedback.

Communication InAppChat Dating Matrimonial #messaging

See more
Squarespace logo

Squarespace

2.1K
382
85
Everything You Need To Create An Exceptional Website
2.1K
382
+ 1
85
PROS OF SQUARESPACE
  • 36
    Easy setup
  • 31
    Clean designs
  • 8
    Beautiful responsive themes
  • 6
    Easy ongoing maintenance
  • 3
    Live chat & 24/7 support team
  • 1
    No coding necessary
CONS OF SQUARESPACE
  • 1
    Hard to use custom code

related Squarespace posts

I am looking to make a website builder web app, where users can publish built websites with a custom or subdomain (much like Wix, Weebly, Squarespace, etc.), and I was wondering about any advice on which web framework to build it on? I currently know Node.js, but I would be excited to learn Laravel or Django if those would be better options. Any advice would be much appreciated!

See more
Niall Geoghegan
at experiential psychotherapy institute · | 8 upvotes · 85.5K views

I created a Squarespace website with multiple blog pages. I discovered that the native Squarespace commenting tool is not currently capable of letting people subscribe to my blog pages if they are using Google Chrome or Safari! I then discovered that Disqus email verification doesn't work with Yahoo Mail. I also hate that there's no way to turn off that email verification (which I don't need since I moderate all comments anyway). So I want to use a different commenting system. I've read some good things about Commento. Three questions: (1) will it work on a Squarespace site? (I'll pay a developer to integrate it for me) (2) Does it have its own issues/elements that don't work smoothly, similar to the other two? (3) Is there another plugin I should be considering for my Squarespace site?

See more
Shopify logo

Shopify

11.9K
6.2K
76
Quickly and easily create a beautiful online store with Shopify.
11.9K
6.2K
+ 1
76
PROS OF SHOPIFY
  • 23
    Affordable yet comprehensive
  • 14
    Great API & integration options
  • 11
    Business-friendly
  • 10
    Intuitive interface
  • 9
    Quick
  • 3
    Liquid
  • 3
    Awesome customer support
  • 2
    POS & Mobile
  • 1
    Dummy Proof
  • 0
    Nopcommerce
CONS OF SHOPIFY
  • 1
    User is stuck with building a site from a template

related Shopify posts

Dennis Kraaijeveld
Shared insights
on
MongoDBMongoDBShopifyShopify

For learning purposes, I am trying to design a dashboard that displays the total revenue from all connected webshops/marketplaces, displaying incoming orders, total orders, etc.

So I will need to get the data (using Node backend) from the Shopify and marketplace APIs, storing this in the database, and get the data from the back end.

My question is:

What kind of database should I use? Is MongoDB fine for storing this kind of data? Or should I go with a SQL database?

See more
Tim Little
Software Consultant at timlittletech · | 7 upvotes · 100.4K views

Hi there, I am trying to figure out if it's worth creating a Braintree account to do subscription billing in my Shopify store. The goal is to have as little custom code as possible for the store but be able to do subscription billing services, we already have a PayPal business account, but from the looks of it, we can't use PayWhirl directly with Paypal.

See more
Wix logo

Wix

598
281
12
Wix.com is a web development platform enabling anyone to build a stunning online presence using simple cloud-based creation...
598
281
+ 1
12
PROS OF WIX
  • 12
    WYSIWYG
CONS OF WIX
    Be the first to leave a con

    related Wix posts

    I am looking to make a website builder web app, where users can publish built websites with a custom or subdomain (much like Wix, Weebly, Squarespace, etc.), and I was wondering about any advice on which web framework to build it on? I currently know Node.js, but I would be excited to learn Laravel or Django if those would be better options. Any advice would be much appreciated!

    See more

    Hi,

    I'm a graphic designer and an acting teacher, and I want to build websites for each of my activities. A few months ago, I created, a Wix website, but it's not responsive. So, I plan to build one from scratch, as I want to host the content and not leave it to Wix or such companies. I was pretty decided to use WordPress to build my website (with "Local" macOS app), but I came across Bootstrap (via "blocs" macOS app).

    I'm now wondering which of these two options I should consider building my website? I want something clean, easy to customize, aesthetic, and easy to update. I read about the lack of SEO with Bootstrap, but I guess there's a way to compensate and promote the website anyway.

    Any piece of advice welcome! Thanks.

    See more
    Weebly logo

    Weebly

    511
    98
    1
    The easiest way to create a website
    511
    98
    + 1
    1
    PROS OF WEEBLY
    • 1
      WYSIWYG
    CONS OF WEEBLY
      Be the first to leave a con

      related Weebly posts

      I am looking to make a website builder web app, where users can publish built websites with a custom or subdomain (much like Wix, Weebly, Squarespace, etc.), and I was wondering about any advice on which web framework to build it on? I currently know Node.js, but I would be excited to learn Laravel or Django if those would be better options. Any advice would be much appreciated!

      See more
      JavaScript logo

      JavaScript

      350.9K
      267.1K
      8.1K
      Lightweight, interpreted, object-oriented language with first-class functions
      350.9K
      267.1K
      + 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
      • 236
        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
        Setup is easy
      • 12
        Its everywhere
      • 12
        Future Language of The Web
      • 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
        Everyone use it
      • 9
        Can be used in backend, frontend and DB
      • 9
        Easy
      • 8
        Easy to hire developers
      • 8
        No need to use PHP
      • 8
        For the good parts
      • 8
        Can be used both as frontend and backend as well
      • 8
        Powerful
      • 8
        Most Popular Language in the World
      • 7
        Popularized Class-Less Architecture & Lambdas
      • 7
        It's fun
      • 7
        Nice
      • 7
        Versitile
      • 7
        Hard not to use
      • 7
        Its fun and fast
      • 7
        Agile, packages simple to use
      • 7
        Supports lambdas and closures
      • 7
        Love-hate relationship
      • 7
        Photoshop has 3 JS runtimes built in
      • 7
        Evolution of C
      • 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
      • 6
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 5
        Promise relationship
      • 5
        Stockholm Syndrome
      • 5
        Function expressions are useful for callbacks
      • 5
        Scope manipulation
      • 5
        Everywhere
      • 5
        Client processing
      • 5
        Clojurescript
      • 5
        What to add
      • 4
        Because it is so simple and lightweight
      • 4
        Only Programming language on browser
      • 1
        Test2
      • 1
        Easy to learn
      • 1
        Easy to understand
      • 1
        Not the best
      • 1
        Hard to learn
      • 1
        Subskill #4
      • 1
        Test
      • 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

      289.8K
      174.2K
      6.6K
      Fast, scalable, distributed revision control system
      289.8K
      174.2K
      + 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.2M 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