Alternatives to Phabricator logo

Alternatives to Phabricator

Redmine, GitHub, Jira, GitLab, and Asana are the most popular alternatives and competitors to Phabricator.
220
295
+ 1
186

What is Phabricator and what are its top alternatives?

Phabricator is a collection of open source web applications that help software companies build better software.
Phabricator is a tool in the Code Review category of a tech stack.

Top Alternatives to Phabricator

  • Redmine

    Redmine

    Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database. ...

  • GitHub

    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

  • Jira

    Jira

    Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster. ...

  • GitLab

    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

  • Asana

    Asana

    Asana is the easiest way for teams to track their work. From tasks and projects to conversations and dashboards, Asana enables teams to move work from start to finish--and get results. Available at asana.com and on iOS & Android. ...

  • Bitbucket

    Bitbucket

    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. ...

  • OpenProject

    OpenProject

    It is an open source software for project management with a wide set of features and plugins and an active international community. ...

  • SonarQube

    SonarQube

    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving. ...

Phabricator alternatives & related posts

Redmine logo

Redmine

535
381
122
A flexible project management web application written using Ruby on Rails framework
535
381
+ 1
122
PROS OF REDMINE
  • 52
    Open source
  • 26
    Customizable with themes and plugins
  • 9
    Powerful custom queries
  • 8
    Integration with code version control like git/svn
  • 6
    RESTful API
  • 6
    Customizable workflows
  • 6
    Integration with email clients
  • 5
    Support for MS SQL Server
  • 1
    Self-hosted
  • 1
    Lightweight
  • 1
    Projects and groups separation
  • 1
    Time tracking, reports
CONS OF REDMINE
    Be the first to leave a con

    related Redmine posts

    We were using a hosted version of Redmine to track defects and user stories originally. We migrated to Jira.

    Jira was an easy decision for a number of reasons:

    • It's much more "Scrum ready" straight out of the box
    • It's so much easier to keep a track of progress (I love the reporting)
    • It natively encourages you to adhere to Scrum/Agile/Kanban practices
    • Atlassian has a fantastic DevOps ecosystem when considering the likes of Confluence and Bamboo etc
    • So many integrations!
    • Its UI is so intuitive which makes it an absolute pleasure to use!

    I know there are alot of other tools in this space but not even considering anything else at the moment. Love Jira!

    See more
    GitHub logo

    GitHub

    187.4K
    154.1K
    10.2K
    Powerful collaboration, review, and code management for open source and private development projects
    187.4K
    154.1K
    + 1
    10.2K
    PROS OF GITHUB
    • 1.8K
      Open source friendly
    • 1.5K
      Easy source control
    • 1.2K
      Nice UI
    • 1.1K
      Great for team collaboration
    • 859
      Easy setup
    • 499
      Issue tracker
    • 482
      Great community
    • 478
      Remote team collaboration
    • 446
      Great way to share
    • 439
      Pull request and features planning
    • 142
      Just works
    • 128
      Integrated in many tools
    • 114
      Free Public Repos
    • 108
      Github Gists
    • 106
      Github pages
    • 81
      Easy to find repos
    • 60
      Open source
    • 58
      Easy to find projects
    • 56
      Network effect
    • 55
      It's free
    • 47
      Extensive API
    • 42
      Organizations
    • 41
      Branching
    • 33
      Developer Profiles
    • 32
      Git Powered Wikis
    • 29
      Great for collaboration
    • 23
      It's fun
    • 22
      Community SDK involvement
    • 21
      Clean interface and good integrations
    • 19
      Learn from others source code
    • 14
      It integrates directly with Azure
    • 14
      Because: Git
    • 13
      Wide acceptance
    • 10
      Large community
    • 9
      Newsfeed
    • 9
      Standard in Open Source collab
    • 8
      It integrates directly with Hipchat
    • 7
      Beautiful user experience
    • 7
      Fast
    • 6
      Easy to discover new code libraries
    • 6
      Cloud SCM
    • 5
      Graphs
    • 5
      Smooth integration
    • 5
      Nice API
    • 5
      Integrations
    • 5
      It's awesome
    • 4
      Remarkable uptime
    • 4
      Hands down best online Git service available
    • 4
      Reliable
    • 3
      Easy to use and collaborate with others
    • 3
      CI Integration
    • 3
      Free HTML hosting
    • 3
      Loved by developers
    • 3
      Quick Onboarding
    • 3
      Security options
    • 3
      Simple but powerful
    • 3
      Uses GIT
    • 3
      Unlimited Public Repos at no cost
    • 3
      Version Control
    • 2
      Nice to use
    • 1
      Free private repos
    • 1
      Easy deployment via SSH
    • 1
      Beautiful
    • 1
      Owned by micrcosoft
    • 1
      Free HTML hostings
    • 1
      Self Hosted
    • 1
      All in one development service
    • 1
      Easy to use
    • 1
      Good tools support
    • 1
      Easy source control and everything is backed up
    • 1
      Leads the copycats
    • 1
      Never dethroned
    • 1
      Ci
    • 1
      Issues tracker
    • 1
      Easy and efficient maintainance of the projects
    • 1
      IAM
    • 1
      IAM integration
    • 0
      Profound
    • 0
      1
    CONS OF GITHUB
    • 46
      Owned by micrcosoft
    • 36
      Expensive for lone developers that want private repos
    • 15
      Relatively slow product/feature release cadence
    • 10
      API scoping could be better
    • 8
      Only 3 collaborators for private repos
    • 3
      Limited featureset for issue management
    • 2
      GitHub Packages does not support SNAPSHOT versions
    • 1
      Have to use a token for the package registry
    • 1
      No multilingual interface
    • 1
      Takes a long time to commit

    related GitHub posts

    Johnny Bell

    I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

    I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

    I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

    Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

    Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

    With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

    If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.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
    Jira logo

    Jira

    43.4K
    32.6K
    1.2K
    The #1 software development tool used by agile teams to plan, track, and release great software.
    43.4K
    32.6K
    + 1
    1.2K
    PROS OF JIRA
    • 306
      Powerful
    • 253
      Flexible
    • 148
      Easy separation of projects
    • 112
      Run in the cloud
    • 104
      Code integration
    • 56
      Easy to use
    • 50
      Run on your own
    • 37
      Easy Workflow Configuration
    • 37
      Great customization
    • 25
      REST API
    • 11
      Great Agile Management tool
    • 7
      Integrates with virtually everything
    • 5
      Confluence
    • 3
      Sentry Issues Integration
    • 2
      Complicated
    CONS OF JIRA
    • 6
      Rather expensive
    • 4
      Large memory requirement
    • 2
      Slow

    related Jira posts

    Johnny Bell

    So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

    When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

    With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

    I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

    In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

    #StackDecisionsLaunch

    See more
    Jakub Olan
    Node.js Software Engineer · | 17 upvotes · 173.1K views

    Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

    See more
    GitLab logo

    GitLab

    42.3K
    34.6K
    2.3K
    Open source self-hosted Git management software
    42.3K
    34.6K
    + 1
    2.3K
    PROS OF GITLAB
    • 491
      Self hosted
    • 420
      Free
    • 334
      Has community edition
    • 238
      Easy setup
    • 238
      Familiar interface
    • 131
      Includes many features, including ci
    • 107
      Nice UI
    • 81
      Good integration with gitlabci
    • 53
      Simple setup
    • 33
      Has an official mobile app
    • 31
      Free private repository
    • 26
      Continuous Integration
    • 19
      Open source, great ui (like github)
    • 15
      Slack Integration
    • 11
      Full CI flow
    • 9
      Free and unlimited private git repos
    • 8
      User, group, and project access management is simple
    • 7
      Built-in CI
    • 7
      All in one (Git, CI, Agile..)
    • 7
      Intuitive UI
    • 4
      Both public and private Repositories
    • 3
      Mattermost Chat client
    • 3
      Issue system
    • 3
      Integrated Docker Registry
    • 2
      I like the its runners and executors feature
    • 2
      Unlimited free repos & collaborators
    • 2
      One-click install through DigitalOcean
    • 2
      It's powerful source code management tool
    • 2
      CI
    • 2
      Free private repos
    • 2
      Excellent
    • 2
      Build/pipeline definition alongside code
    • 2
      On-premises
    • 2
      Security and Stable
    • 2
      So easy to use
    • 2
      Great for team collaboration
    • 2
      Low maintenance cost due omnibus-deployment
    • 2
      It's fully integrated
    • 1
      Many private repo
    • 1
      Published IP list for whitelisting (gl-infra#434)
    • 1
      Powerful Continuous Integration System
    • 1
      Kubernetes Integration
    • 1
      Kubernetes integration with GitLab CI
    • 1
      Review Apps feature
    • 1
      Built-in Docker Registry
    • 1
      The dashboard with deployed environments
    • 1
      Multilingual interface
    • 1
      Native CI
    • 1
      HipChat intergration
    • 1
      It includes everything I need, all packaged with docker
    • 1
      Powerful software planning and maintaining tools
    • 1
      Groups of groups
    • 1
      Dockerized
    • 1
      Beautiful
    • 1
      Wounderful
    • 1
      Opensource
    • 1
      Because is the best remote host for git repositories
    • 1
      Not Microsoft Owned
    • 1
      Full DevOps suite with Git
    • 0
      Supports Radius/Ldap & Browser Code Edits
    CONS OF GITLAB
    • 26
      Slow ui performance
    • 6
      Introduce breaking bugs every release
    • 5
      Insecure (no published IP list for whitelisting)
    • 1
      Built-in Docker Registry
    • 0
      Review Apps feature

    related GitLab posts

    Tim Abbott
    Shared insights
    on
    GitHubGitHubGitLabGitLab
    at

    I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

    But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

    • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
    • You can't let anyone with a GitHub account self-assign issues to themselves.
    • Many more similar issues.

    It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

    We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

    See more
    Joshua Dean Küpper
    CEO at Scrayos UG (haftungsbeschränkt) · | 18 upvotes · 286K views

    We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

    While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

    We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

    See more
    Asana logo

    Asana

    7K
    5K
    652
    Enabling the teams to work together effortlessly
    7K
    5K
    + 1
    652
    PROS OF ASANA
    • 160
      Super fast task creation
    • 148
      Flexible project management
    • 101
      Free up to 15
    • 99
      Followers and commenting on tasks
    • 57
      Integration with external services
    • 25
      Email-based task creation
    • 17
      Plays nice with Google Apps
    • 14
      Clear usage
    • 13
      Plays nice with Harvest Time Tracking
    • 6
      Supports nice keyboard shortcuts
    • 4
      Integration with GitHub
    • 2
      Slack supported
    • 2
      Integration with Instagantt for Gantt Charts
    • 1
      Integration with Alfred
    • 1
      Both Card View & Task View
    • 1
      Easy to use
    • 1
      Friendly API
    • 0
      Slick and fast interface
    CONS OF ASANA
    • 0
      Not Cross Platform

    related Asana posts

    Lucas Litton
    Founder & CEO at Macombey · | 24 upvotes · 121.1K views

    Sentry has been essential to our development approach. Nobody likes errors or apps that crash. We use Sentry heavily during Node.js and React development. Our developers are able to see error reports, crashes, user's browsers, and more, all in one place. Sentry also seamlessly integrates with Asana, Slack, and GitHub.

    See more
    Shared insights
    on
    JiraJiraAsanaAsanaTrelloTrelloAha!Aha!

    I'm comparing Aha!, Trello and Asana. We are looking for it as a Product Management Team. Jira handles all our development and storyboard etc. This is for Product Management for Roadmaps, Backlogs, future stories, etc. Cost is a factor, as well. Does anyone have a comparison chart of Pros and Cons? Thank you.

    See more
    Bitbucket logo

    Bitbucket

    31.7K
    24.7K
    2.8K
    One place to plan projects, collaborate on code, test and deploy, all with free private repositories
    31.7K
    24.7K
    + 1
    2.8K
    PROS OF BITBUCKET
    • 905
      Free private repos
    • 398
      Simple setup
    • 347
      Nice ui and tools
    • 341
      Unlimited private repositories
    • 240
      Affordable git hosting
    • 123
      Integrates with many apis and services
    • 119
      Reliable uptime
    • 86
      Nice gui
    • 84
      Pull requests and code reviews
    • 58
      Very customisable
    • 16
      Mercurial repositories
    • 14
      SourceTree integration
    • 11
      JIRA integration
    • 10
      Track every commit to an issue in JIRA
    • 8
      Best free alternative to Github
    • 8
      Deployment hooks
    • 7
      Automatically share repositories with all your teammates
    • 7
      Compatible with Mac and Windows
    • 6
      Source Code Insight
    • 5
      Price
    • 5
      Login with Google
    • 5
      Create a wiki
    • 5
      Approve pull request button
    • 4
      Customizable pipelines
    • 4
      #2 Atlassian Product after JIRA
    • 3
      Continuous Integration and Delivery
    • 3
      Unlimited Private Repos at no cost
    • 3
      Also supports Mercurial
    • 2
      Teamcity
    • 2
      Mercurial Support
    • 2
      IAM
    • 2
      Issues tracker
    • 2
      Open source friendly
    • 2
      Multilingual interface
    • 2
      Academic license program
    • 2
      IAM integration
    • 0
      Free Private Repositories
    CONS OF BITBUCKET
    • 19
      Not much community activity
    • 17
      Difficult to review prs because of confusing ui
    • 14
      Quite buggy
    • 10
      Managed by enterprise Java company
    • 8
      CI tool is not free of charge
    • 7
      Complexity with rights management
    • 6
      Only 5 collaborators for private repos
    • 4
      Slow performance
    • 2
      No AWS Codepipelines integration
    • 1
      No more Mercurial repositories
    • 1
      No server side git-hook support

    related Bitbucket posts

    Michael Kelly
    Senior Software Engineer at StackShare · | 14 upvotes · 626K views

    I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

    GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

    It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

    See more
    Shared insights
    on
    GitHubGitHubGitLabGitLabBitbucketBitbucket

    A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.

    • Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
    • Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
    • Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.

    Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:

    • Wiki and project repositories
    • Project uploads
    • The configuration including webhooks and services
    • Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.

    GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.

    So go ahead with better understanding.

    See more
    OpenProject logo

    OpenProject

    39
    63
    0
    Aa web-based project collaboration software
    39
    63
    + 1
    0
    PROS OF OPENPROJECT
      Be the first to leave a pro
      CONS OF OPENPROJECT
        Be the first to leave a con

        related OpenProject posts

        SonarQube logo

        SonarQube

        1.2K
        1.4K
        39
        Continuous Code Quality
        1.2K
        1.4K
        + 1
        39
        PROS OF SONARQUBE
        • 20
          Tracks code complexity and smell trends
        • 12
          IDE Integration
        • 7
          Complete code Review
        CONS OF SONARQUBE
        • 5
          Sales process is long and unfriendly
        • 4
          Paid support is poor, techs arrogant and unhelpful

        related SonarQube posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.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
        Ganesa Vijayakumar
        Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

        I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

        I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

        As per my work experience and knowledge, I have chosen the followings stacks to this mission.

        UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

        Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

        Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

        Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

        Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

        Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

        Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

        Happy Coding! Suggestions are welcome! :)

        Thanks, Ganesa

        See more