Alternatives to Kurento logo

Alternatives to Kurento

Jitsi, Wowza, WebRTC, GStreamer, and Mediasoup are the most popular alternatives and competitors to Kurento.
40
140
+ 1
5

What is Kurento and what are its top alternatives?

Kurento is an open-source multimedia framework that provides several functionalities to create rich WebRTC applications. Key features include real-time video and audio processing, recording, transcoding, and streaming. However, Kurento has some limitations such as complex setup and maintenance, lack of comprehensive documentation, and performance issues in large-scale deployments.

  1. Janus: Janus is a modular, open-source WebRTC server with plugin support. Key features include group communications, scalable architecture, and active community support. Pros include easy integration with existing applications and flexible plugin system. Cons include a steep learning curve for beginners.

  2. Jitsi: Jitsi is an open-source video conferencing platform with features like screen sharing, chat, and recording. Key features include end-to-end encryption, easy deployment, and cross-platform compatibility. Pros include strong security measures and user-friendly interface. Cons include occasional stability issues.

  3. Mediasoup: Mediasoup is a WebRTC server based on Node.js that offers advanced media capabilities for real-time communication. Key features include scalable architecture, audio and video routing, and low latency. Pros include powerful media processing capabilities and active developer community. Cons include limited documentation for beginners.

  4. OpenVidu: OpenVidu is a platform for building video conference applications with WebRTC. Key features include flexible APIs, screen sharing, and recording capabilities. Pros include simplified integration with existing applications and customizable layouts. Cons include limited support for advanced media processing.

  5. Wowza Streaming Engine: Wowza Streaming Engine is a customizable media server software with support for streaming protocols like WebRTC, RTMP, and HLS. Key features include adaptive bitrate streaming, DVR capabilities, and extensive codec support. Pros include robust streaming performance and wide protocol compatibility. Cons include high licensing costs for professional use.

  6. Ant Media Server: Ant Media Server is a scalable media server with support for WebRTC, RTMP, and HLS streaming. Key features include adaptive bitrate streaming, low latency, and cluster support for high availability. Pros include affordable pricing options and comprehensive documentation. Cons include limited community support.

  7. Pion WebRTC: Pion is a WebRTC framework for building scalable peer-to-peer applications. Key features include ICE and DTLS protocols, data channels, and flexible API. Pros include lightweight and modular design for custom development. Cons include limited out-of-the-box features compared to full-fledged media servers.

  8. KITE: KITE is an open-source WebRTC testing framework for automated testing of WebRTC applications. Key features include scriptable testing, real-time reporting, and integration with popular testing tools. Pros include comprehensive testing capabilities and community-driven development. Cons include a learning curve for setting up test environments.

  9. Red5: Red5 is an open-source media server with support for streaming protocols like RTMP, RTSP, and WebRTC. Key features include low latency streaming, server-side recording, and scalable architecture. Pros include flexible customization options and active open-source community. Cons include occasional stability issues in large-scale deployments.

  10. Cisco Webex: Cisco Webex is a cloud-based video conferencing platform with features like screen sharing, messaging, and whiteboarding. Key features include enterprise-grade security, integration with productivity tools, and large meeting support. Pros include reliable performance and extensive feature set. Cons include higher pricing for advanced features and scalability limitations.

Top Alternatives to Kurento

  • Jitsi
    Jitsi

    Jitsi (acquired by 8x8) is a set of open-source projects that allows you to easily build and deploy secure videoconferencing solutions. At the heart of Jitsi are Jitsi Videobridge and Jitsi Meet, which let you have conferences on the internet, while other projects in the community enable other features such as audio, dial-in, recording, and simulcasting. ...

  • Wowza
    Wowza

    It offers a customizable live streaming platform to build, deploy and manage high-quality video, live and on-demand. It powers professional-grade streaming for any use case and any device. ...

  • WebRTC
    WebRTC

    It is a free, open project that enables web browsers with Real-Time Communications (RTC) capabilities via simple JavaScript APIs. The WebRTC components have been optimized to best serve this purpose. ...

  • GStreamer
    GStreamer

    It is a library for constructing graphs of media-handling components. The applications it supports range from simple Ogg/Vorbis playback, audio/video streaming to complex audio (mixing) and video (non-linear editing) processing. ...

  • Mediasoup
    Mediasoup

    Mediasoup and its client side libraries provide a super low level API. They are intended to enable different use cases and scenarios, without any constraint or assumption. Some of these use cases are: Group video chat applications, One-to-many (or few-to-many) broadcasting applications in real-time, and RTP streaming. ...

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

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

Kurento alternatives & related posts

Jitsi logo

Jitsi

248
719
93
Multi-platform open-source video conferencing
248
719
+ 1
93
PROS OF JITSI
  • 32
    Open Source
  • 20
    Entirely free conferencing
  • 19
    Unlimited time
  • 5
    Accessible from browser
  • 3
    Desktop, app and browser tab sharing
  • 3
    WebRTC standard
  • 2
    Secure & encrypted video conference
  • 2
    Great API to develop with
  • 2
    Live stream to youtube
  • 1
    Dial-In and Dial-Out via SIP
  • 1
    Full HD
  • 1
    FSB Approved
  • 1
    Share youtube videos in conference
  • 1
    Easy installation and good support
  • 0
    MCU
CONS OF JITSI
  • 7
    UnLimited time
  • 5
    No multiplatform
  • 1
    Great quality
  • 1
    Good support
  • 1
    Live conference statistics
  • 1
    Great features

related Jitsi posts

Shared insights
on
JitsiJitsiJavaScriptJavaScript

For weeks I have been researching to find an open source video conferencing platform that allows integration from native clients. I am working on a solution that would need to communicate from a native app via a windows dll (at least initially). Ultimately, I want any OS to talk to it natively. A lot of platforms provide the JavaScript interface (like Jitsi) but wrapping this in a windows dll is both complicated and has a huge footprint. What open source video conference servers are available that have native windows clients that can be packaged in a DLL?

See more
Shared insights
on
JitsiJitsiZoomZoom

A common issue with Zoom is the "half-duplex" operation, where only one person can speak at a time, and another person speaking will cause an interrupt and take control. Hence the infernal mute button is so needed. Does Jitsi allow for a "full-duplex" communication to occur? An example scenario is two people singing a duet, which is impossible on a Zoom call.

Many Thanks, Garry

See more
Wowza logo

Wowza

37
70
0
A customizable live streaming platform
37
70
+ 1
0
PROS OF WOWZA
    Be the first to leave a pro
    CONS OF WOWZA
      Be the first to leave a con

      related Wowza posts

      We would like to connect a number of (about 25) video streams, from an Amazon S3 bucket containing video data to endpoints accessible to a Docker image, which, when run, will process the input video streams and emit some JSON statistics.

      The 25 video streams should be synchronized. Could people share their experiences with a similar scenario and perhaps offer advice about which is better (Wowza, Amazon Kinesis Video Streams) for this kind of problem, or why they chose one technology over the other?

      The video stream duration will be quite long (about 8 hours each x 25 camera sources). The 25 video streams will have no audio component. If you worked with a similar problem, what was your experience with scaling, latency, resource requirements, config, etc.?

      See more
      Shared insights
      on
      WowzaWowzaBitmovinBitmovin

      We want to make a live streaming platform demo to show off our video compression technology.

      Simply put, we will stream content from 12 x 4K cameras ——> to an edge server(s) containing our compression software ——> either to Bitmovin or Wowza ——> to a media player.

      What we would like to know is, is one of the above streaming engines more suited to multiple feeds (we will eventually be using more than 100 4K cameras for the actual streaming platform), 4K content streaming, latency, and functions such as being to Zoom in on the 4K content?

      If anyone has any insight into the above, we would be grateful for your advice. We are a Japanese company and were recommended the above two streaming engines but know nothing about them as they literally “foreign” to us.

      Thanks so much.

      See more
      WebRTC logo

      WebRTC

      316
      526
      6
      A free, open project that provides browsers and mobile applications with Real-Time Communications
      316
      526
      + 1
      6
      PROS OF WEBRTC
      • 3
        OpenSource
      • 2
        No Download
      • 1
        You can write anything around it, because it's a protoc
      CONS OF WEBRTC
        Be the first to leave a con

        related WebRTC posts

        Hello. So, I wanted to make a decision on whether to use WebRTC or Amazon Chime for a conference call (meeting). My plan is to build an app with features like video broadcasting, and the ability for all the participants to talk and chat. I have used Agora's web SDK for video broadcasting, and Socket.IO for chat features. As I read the comparison between Amazon Chime and WebRTC, it further intrigues me on what I should use given my scenario? Is there any way that so many related technologies could be a hindrance to the other? Any advice would be appreciated. Thanks. Ritwik Neema

        See more
        Abdullah Adeel

        Hey everyone, I am planning to start a personal project that would be yet another social media project with real-time communication facilities like one-to-one chat, group chat, and later voice and video chat using WebRTC. The thing I am concerned about is Django being able to handle all the real-time stuff using websockets. I can use Django Channels, but I don't think that would be a very scalable solution. Moreover, django_channels require alto of configurations, and deployment is also a pain. My plan is to use a separate Node.js server to handle all the socket connections and have it talk to the main django server through Redis. My question is whether the above-mentioned solution is a good choice? If yes, how this can be achieved, keeping in mind all the authentication other related problems. It might be simple, but I have never done this before, which might be the main reason I am concerned. But any suggestion will be appreciated.

        Thanks in advance 😊

        See more
        GStreamer logo

        GStreamer

        49
        79
        4
        Open source multimedia framework
        49
        79
        + 1
        4
        PROS OF GSTREAMER
        • 2
          Ease of use
        • 1
          Cross Platform
        • 1
          Open Source
        CONS OF GSTREAMER
          Be the first to leave a con

          related GStreamer posts

          Shared insights
          on
          GStreamerGStreamerFFMPEGFFMPEG

          I have a situation to convert the H264 streams into MP4 format using FFMPEG/GStreamer.

          However Im stuck with the gst-ugly plugin, now trying my luck with ffmeg. How big are the ffmeg libs and licensing complications?

          See more
          Mediasoup logo

          Mediasoup

          19
          90
          0
          Cutting Edge WebRTC Video Conferencing
          19
          90
          + 1
          0
          PROS OF MEDIASOUP
            Be the first to leave a pro
            CONS OF MEDIASOUP
              Be the first to leave a con

              related Mediasoup posts

              JavaScript logo

              JavaScript

              352.4K
              268.2K
              8.1K
              Lightweight, interpreted, object-oriented language with first-class functions
              352.4K
              268.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
              • 897
                Fast
              • 745
                Light weight
              • 425
                Flexible
              • 392
                You can't get a device today that doesn't run js
              • 286
                Non-blocking i/o
              • 237
                Ubiquitousness
              • 191
                Expressive
              • 55
                Extended functionality to web pages
              • 49
                Relatively easy language
              • 46
                Executed on the client side
              • 30
                Relatively fast to the end user
              • 25
                Pure Javascript
              • 21
                Functional programming
              • 15
                Async
              • 13
                Full-stack
              • 12
                Setup is easy
              • 12
                Future Language of The Web
              • 12
                Its everywhere
              • 11
                Because I love functions
              • 11
                JavaScript is the New PHP
              • 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
                Most Popular Language in the World
              • 8
                Powerful
              • 8
                Can be used both as frontend and backend as well
              • 8
                For the good parts
              • 8
                No need to use PHP
              • 8
                Easy to hire developers
              • 7
                Agile, packages simple to use
              • 7
                Love-hate relationship
              • 7
                Photoshop has 3 JS runtimes built in
              • 7
                Evolution of C
              • 7
                It's fun
              • 7
                Hard not to use
              • 7
                Versitile
              • 7
                Its fun and fast
              • 7
                Nice
              • 7
                Popularized Class-Less Architecture & Lambdas
              • 7
                Supports lambdas and closures
              • 6
                It let's me use Babel & Typescript
              • 6
                Can be used on frontend/backend/Mobile/create PRO Ui
              • 6
                1.6K Can be used on frontend/backend
              • 6
                Client side JS uses the visitors CPU to save Server Res
              • 6
                Easy to make something
              • 5
                Clojurescript
              • 5
                Promise relationship
              • 5
                Stockholm Syndrome
              • 5
                Function expressions are useful for callbacks
              • 5
                Scope manipulation
              • 5
                Everywhere
              • 5
                Client processing
              • 5
                What to add
              • 4
                Because it is so simple and lightweight
              • 4
                Only Programming language on browser
              • 1
                Test
              • 1
                Hard to learn
              • 1
                Test2
              • 1
                Not the best
              • 1
                Easy to understand
              • 1
                Subskill #4
              • 1
                Easy to learn
              • 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.9M 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

              291.4K
              174.8K
              6.6K
              Fast, scalable, distributed revision control system
              291.4K
              174.8K
              + 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.7M 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.7M 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
              GitHub logo

              GitHub

              280.6K
              244.8K
              10.3K
              Powerful collaboration, review, and code management for open source and private development projects
              280.6K
              244.8K
              + 1
              10.3K
              PROS OF GITHUB
              • 1.8K
                Open source friendly
              • 1.5K
                Easy source control
              • 1.3K
                Nice UI
              • 1.1K
                Great for team collaboration
              • 867
                Easy setup
              • 504
                Issue tracker
              • 486
                Great community
              • 483
                Remote team collaboration
              • 451
                Great way to share
              • 442
                Pull request and features planning
              • 147
                Just works
              • 132
                Integrated in many tools
              • 121
                Free Public Repos
              • 116
                Github Gists
              • 112
                Github pages
              • 83
                Easy to find repos
              • 62
                Open source
              • 60
                It's free
              • 60
                Easy to find projects
              • 56
                Network effect
              • 49
                Extensive API
              • 43
                Organizations
              • 42
                Branching
              • 34
                Developer Profiles
              • 32
                Git Powered Wikis
              • 30
                Great for collaboration
              • 24
                It's fun
              • 23
                Clean interface and good integrations
              • 22
                Community SDK involvement
              • 20
                Learn from others source code
              • 16
                Because: Git
              • 14
                It integrates directly with Azure
              • 10
                Standard in Open Source collab
              • 10
                Newsfeed
              • 8
                It integrates directly with Hipchat
              • 8
                Fast
              • 8
                Beautiful user experience
              • 7
                Easy to discover new code libraries
              • 6
                Smooth integration
              • 6
                Cloud SCM
              • 6
                Nice API
              • 6
                Graphs
              • 6
                Integrations
              • 6
                It's awesome
              • 5
                Quick Onboarding
              • 5
                Reliable
              • 5
                Remarkable uptime
              • 5
                CI Integration
              • 5
                Hands down best online Git service available
              • 4
                Uses GIT
              • 4
                Version Control
              • 4
                Simple but powerful
              • 4
                Unlimited Public Repos at no cost
              • 4
                Free HTML hosting
              • 4
                Security options
              • 4
                Loved by developers
              • 4
                Easy to use and collaborate with others
              • 3
                Ci
              • 3
                IAM
              • 3
                Nice to use
              • 3
                Easy deployment via SSH
              • 2
                Easy to use
              • 2
                Leads the copycats
              • 2
                All in one development service
              • 2
                Free private repos
              • 2
                Free HTML hostings
              • 2
                Easy and efficient maintainance of the projects
              • 2
                Beautiful
              • 2
                Easy source control and everything is backed up
              • 2
                IAM integration
              • 2
                Very Easy to Use
              • 2
                Good tools support
              • 2
                Issues tracker
              • 2
                Never dethroned
              • 2
                Self Hosted
              • 1
                Dasf
              • 1
                Profound
              CONS OF GITHUB
              • 54
                Owned by micrcosoft
              • 38
                Expensive for lone developers that want private repos
              • 15
                Relatively slow product/feature release cadence
              • 10
                API scoping could be better
              • 9
                Only 3 collaborators for private repos
              • 4
                Limited featureset for issue management
              • 3
                Does not have a graph for showing history like git lens
              • 2
                GitHub Packages does not support SNAPSHOT versions
              • 1
                No multilingual interface
              • 1
                Takes a long time to commit
              • 1
                Expensive

              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
              Russel Werner
              Lead Engineer at StackShare · | 32 upvotes · 2.5M views

              StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

              Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

              #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

              See more