Alternatives to imgix logo

Alternatives to imgix

Kraken.io, Cloudinary, CloudFlare, Fastly, and Uploadcare are the most popular alternatives and competitors to imgix.
215
318
+ 1
176

What is imgix and what are its top alternatives?

imgix is a powerful image processing and delivery service that allows users to dynamically manipulate images and optimize them for fast loading on websites and apps. Key features of imgix include real-time image transformation, responsive image optimization, automatic format selection, and advanced image caching. However, some limitations of imgix include its pricing structure, which can be costly for high traffic websites, and the learning curve involved in using its advanced features.

  1. Cloudinary: Cloudinary offers a comprehensive cloud-based image and video management solution with features such as automatic optimization, responsive delivery, and AI-based content-aware cropping. Pros include robust SDKs for easy integration and generous free tier, while cons include pricing based on resource consumption.
  2. Kraken.io: Kraken.io is an image optimization tool that uses advanced algorithms to reduce image file size without compromising quality. Key features include lossless and lossy compression options, API integration, and support for various image formats. Pros include affordable pricing and easy-to-use interface, while cons include lack of advanced image manipulation features.
  3. Fastly Image Optimizer: Fastly Image Optimizer is a CDN-aware image optimization service that enables quick delivery of optimized images at scale. Features include WebP format support, automatic quality adjustments, and lazy loading. Pros include seamless integration with Fastly CDN and real-time image optimization, while cons include limited customization options.
  4. ImageKit: ImageKit is an image optimization and delivery service that offers real-time image resizing, optimization, and transformation capabilities. Key features include built-in lazy loading, automatic format selection, and easy integration with popular platforms like Shopify and WordPress. Pros include generous free tier and flexible pricing plans, while cons include limited support for video optimization.
  5. Thumbor: Thumbor is an open-source smart imaging service that enables users to build custom image manipulation pipelines with ease. Features include smart cropping, resizing, and filters, as well as support for custom image storage backends. Pros include flexibility to create custom image processing pipelines and extensibility through plugins, while cons include self-hosting requirements and need for technical expertise.
  6. Sirv: Sirv is an image optimization and delivery service that offers on-the-fly image rendering, smart cropping, and SEO-friendly image URLs. Key features include built-in CDN, automatic image optimization, and real-time image editing capabilities. Pros include easy implementation with plugins for popular platforms like Shopify and Magento, while cons include pricing based on bandwidth consumption.
  7. Optimole: Optimole is a WordPress plugin that automatically optimizes images on websites for fast loading times and better performance. Features include lazy loading, WebP format support, and automatic image resizing based on user's device. Pros include seamless integration with WordPress sites and affordable pricing plans, while cons include dependency on WordPress platform.
  8. TinyIMG: TinyIMG is a Shopify app that helps optimize images on e-commerce websites for improved loading speed and better SEO rankings. Key features include bulk image optimization, automatic image compression, and SEO-friendly image metadata. Pros include easy integration with Shopify stores and one-click optimization, while cons include limited support for advanced image manipulation.
  9. Gumlet: Gumlet is an image optimization service that offers features such as lazy loading, automatic resizing, and CDN delivery for fast loading images on websites. Pros include simple setup with one-line code integration and flexible pricing plans, while cons include limited support for custom image transformations.
  10. Piio: Piio is an intelligent image optimization service that dynamically resizes and compresses images based on user's device and viewport. Key features include automatic image format selection, lazy loading, and advanced image caching. Pros include AI-based optimization for optimal image delivery and easy integration with popular platforms like WordPress and Shopify, while cons include pricing based on bandwidth usage.

Top Alternatives to imgix

  • Kraken.io
    Kraken.io

    It supports JPEG, PNG and GIF files. You can optimize your images in two ways - by providing an URL of the image you want to optimize or by uploading an image file directly to its API. ...

  • Cloudinary
    Cloudinary

    Cloudinary is a cloud-based service that streamlines websites and mobile applications' entire image and video management needs - uploads, storage, administration, manipulations, and delivery. ...

  • CloudFlare
    CloudFlare

    Cloudflare speeds up and protects millions of websites, APIs, SaaS services, and other properties connected to the Internet. ...

  • Fastly
    Fastly

    Fastly's real-time content delivery network gives you total control over your content, unprecedented access to performance analytics, and the ability to instantly update content in 150 milliseconds. ...

  • Uploadcare
    Uploadcare

    Uploadcare is file management platform and a CDN for user-generated content. It is a robust file API for uploading, managing, processing, rendering, optimizing, and delivering users’ content. ...

  • Thumbor
    Thumbor

    It is a smart imaging service. It enables on-demand crop, resizing and flipping of images. It allows users to store and load images from anywhere needed. It's really simple to implement a new loader or storage. ...

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

imgix alternatives & related posts

Kraken.io logo

Kraken.io

16
53
7
Image optimization and compression API
16
53
+ 1
7
PROS OF KRAKEN.IO
  • 6
    Free
  • 1
    Magento plugin
CONS OF KRAKEN.IO
    Be the first to leave a con

    related Kraken.io posts

    Cloudinary logo

    Cloudinary

    578
    591
    179
    An end-to-end image & video management solution for your web and mobile applications
    578
    591
    + 1
    179
    PROS OF CLOUDINARY
    • 37
      Easy setup
    • 31
      Fast image delivery
    • 26
      Vast array of image manipulation capabilities
    • 21
      Free tier
    • 11
      Heroku add-on
    • 9
      Reduce development costs
    • 7
      Amazing support
    • 6
      Heroku plugin
    • 6
      Great libraries for all languages
    • 6
      Virtually limitless scale
    • 5
      Easy to integrate with Rails
    • 4
      Cheap
    • 3
      Shot setup time
    • 3
      Very easy setup
    • 2
      Solves alot of image problems.
    • 1
      Best in the market and includes free plan
    • 1
      Extremely generous free pricing tier
    • 0
      Fast image delivery, vast array
    CONS OF CLOUDINARY
    • 5
      Paid plan is expensive

    related Cloudinary posts

    Repost

    Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

    Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

    Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

    Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

    See more

    Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku. However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

    Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

    Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

    Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

    See more
    CloudFlare logo

    CloudFlare

    75.9K
    22.1K
    1.8K
    The Web Performance & Security Company.
    75.9K
    22.1K
    + 1
    1.8K
    PROS OF CLOUDFLARE
    • 424
      Easy setup, great cdn
    • 277
      Free ssl
    • 199
      Easy setup
    • 190
      Security
    • 180
      Ssl
    • 98
      Great cdn
    • 77
      Optimizer
    • 71
      Simple
    • 44
      Great UI
    • 28
      Great js cdn
    • 12
      Apps
    • 12
      HTTP/2 Support
    • 12
      DNS Analytics
    • 12
      AutoMinify
    • 9
      Rocket Loader
    • 9
      Ipv6
    • 9
      Easy
    • 8
      IPv6 "One Click"
    • 8
      Fantastic CDN service
    • 7
      DNSSEC
    • 7
      Nice DNS
    • 7
      SSHFP
    • 7
      Free GeoIP
    • 7
      Amazing performance
    • 7
      API
    • 7
      Cheapest SSL
    • 6
      SPDY
    • 6
      Free and reliable, Faster then anyone else
    • 5
      Ubuntu
    • 5
      Asynchronous resource loading
    • 4
      Global Load Balancing
    • 4
      Performance
    • 4
      Easy Use
    • 3
      CDN
    • 2
      Registrar
    • 2
      Support for SSHFP records
    • 1
      Web3
    • 1
      Прохси
    • 1
      HTTPS3/Quic
    CONS OF CLOUDFLARE
    • 2
      No support for SSHFP records
    • 2
      Expensive when you exceed their fair usage limits

    related CloudFlare posts

    Eugene Cheah

    For inboxkitten.com, an opensource disposable email service;

    We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.

    If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...

    1. <5ms CPU time limit
    2. Incompatible with express.js
    3. one script limitation per domain

    Limitations our workload is able to conform with (YMMV)

    For hosting of static files, we migrated from Firebase to CommonsHost

    More details on the trade-off in between both serverless providers is in the article

    See more
    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
    Fastly logo

    Fastly

    1.1K
    502
    153
    We're redefining content delivery.
    1.1K
    502
    + 1
    153
    PROS OF FASTLY
    • 28
      Real-time updates
    • 26
      Fastest CDN
    • 22
      Powerful API
    • 20
      Great support
    • 14
      Great customer support
    • 7
      Instant Purging
    • 7
      Custom VCL
    • 6
      Good pricing
    • 6
      Tag-based Purging
    • 5
      HTTP/2 Support
    • 4
      Speed & functionality
    • 4
      Image processing on demande (Fastly IO)
    • 4
      Best CDN
    CONS OF FASTLY
    • 1
      Minimum $50/mo spend

    related Fastly posts

    Paul Whittemore
    Developer and Owner at Appurist Software · | 15 upvotes · 1.1M views

    I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.

    The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.

    Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.

    See more
    Justin Dorfman
    Open Source Program Manager at Reblaze · | 4 upvotes · 235.3K views

    When my SSL cert MaxCDN was expiring on my personal site I decided it was a good time to revamp some things. Since GitHub Services is depreciated I can no longer have #CDN cache purges automated among other things. So I decided on the following: GitHub Pages, Netlify, Let's Encrypt and Jekyll. Staying the same was Bootstrap, jQuery, Grunt & #GoogleFonts.

    What's awesome about GitHub Pages is that it has a #CDN (Fastly) built-in and anytime you push to master, it purges the cache instantaneously without you have to do anything special. Netlify is magic, I highly recommend it to anyone using #StaticSiteGenerators.

    For the most part, everything went smoothly. The only things I had issues with were the following:

    • If you want to point www to GitHub Pages you need to rename the repo to www
    • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
    • I had to disable the Grunt htmlmin module. I replaced it with Jekyll layout that compresses HTML for #webperf

    Last but certainly not least, I made a donation to Let's Encrypt. If you use their service consider doing it too: https://letsencrypt.org/donate/

    See more
    Uploadcare logo

    Uploadcare

    72
    121
    27
    File uploads, media processing, and adaptive delivery for web and mobile
    72
    121
    + 1
    27
    PROS OF UPLOADCARE
    • 10
      Great team
    • 6
      Simple image upload with widget
    • 5
      Easy to integrate into any website
    • 5
      Awesome support
    • 1
      <a href="http://fixbit.com/">useful tool</a>
    CONS OF UPLOADCARE
    • 1
      Upload widget is large (114KB)
    • 0
      no cons

    related Uploadcare posts

    Thumbor logo

    Thumbor

    22
    28
    0
    Allows users to store and load images from anywhere needed
    22
    28
    + 1
    0
    PROS OF THUMBOR
      Be the first to leave a pro
      CONS OF THUMBOR
        Be the first to leave a con

        related Thumbor posts

        JavaScript logo

        JavaScript

        351K
        267.2K
        8.1K
        Lightweight, interpreted, object-oriented language with first-class functions
        351K
        267.2K
        + 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.9K
        174.2K
        6.6K
        Fast, scalable, distributed revision control system
        289.9K
        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