Alternatives to Fastify logo

Alternatives to Fastify

Koa, Restify, hapi, Golang, and ExpressJS are the most popular alternatives and competitors to Fastify.
409
507
+ 1
95

What is Fastify and what are its top alternatives?

Fastify is a high-performance web framework for Node.js that boasts low overhead and optimal performance due to its speedy routing and minimalist design. It supports schema-based validation, plugins, and hooks, making it a robust choice for building efficient web applications. However, Fastify's ecosystem may not be as extensive as other popular frameworks, limiting the availability of additional tools and resources.

  1. Express: Express is a widely-used web framework for Node.js known for its flexibility and simplicity. Key features include robust routing, middleware support, and template engines. Pros: Extensive community support and a wide range of plugins available. Cons: Slightly slower performance compared to Fastify.
  2. Koa: Koa is a lightweight and modular web framework that uses async/await functions. It offers streamlined middleware handling and is ideal for building modern applications. Pros: Elegant syntax and built-in support for generators. Cons: Less mature ecosystem compared to Fastify.
  3. NestJS: NestJS is a progressive Node.js framework that leverages TypeScript and follows the Angular design pattern. It offers a well-structured architecture, dependency injection, and built-in support for GraphQL, WebSockets, and microservices. Pros: Scalable and maintainable codebase. Cons: Steeper learning curve for developers new to TypeScript.
  4. Hapi: Hapi is a rich framework for building applications and services with robust plugin support. It emphasizes configuration-driven development and includes features like caching, validation, and authentication. Pros: Great for creating API-centric applications. Cons: Requires more configuration compared to Fastify.
  5. Sails.js: Sails.js is a full-featured MVC framework for Node.js that simplifies the development of web applications and APIs. It offers auto-generated REST APIs, WebSockets support, and adapter-based data stores. Pros: Rapid development with built-in features like blueprints and scaffolding. Cons: Heavy reliance on Waterline ORM can lead to performance issues.
  6. LoopBack: LoopBack is an extensible framework with built-in models, data sources, and APIs. It supports a variety of connectors, including SQL databases, NoSQL databases, and REST services. Pros: Easy integration with services and databases. Cons: Complex configuration and setup process compared to Fastify.
  7. AdonisJS: AdonisJS is a full-featured MVC framework for Node.js with a focus on developer ergonomics. It includes a powerful ORM, authentication, and authorization features out of the box. Pros: Scaffolding tools for rapid development. Cons: Opinionated structure may not suit all projects.
  8. Restify: Restify is a web framework designed specifically for building REST APIs. It offers built-in support for versioning, throttling, and pre and post handlers. Pros: Lightweight and efficient for API development. Cons: Limited support for building full-fledged web applications.
  9. Feathers: Feathers is a minimalist web framework that focuses on real-time applications and microservices. It provides a flexible architecture, service-oriented design, and client-server agnostic APIs. Pros: Seamless integration with various databases and real-time services. Cons: Limited support for complex web application development.
  10. Meteor: Meteor is a full-stack JavaScript platform for building responsive web and mobile applications. It provides a unified development experience with real-time data synchronization and instant updates. Pros: Easy learning curve for beginners and seamless integration with front-end frameworks. Cons: Less flexible compared to Fastify for back-end development.

Top Alternatives to Fastify

  • Koa
    Koa

    Koa aims to be a smaller, more expressive, and more robust foundation for web applications and APIs. Through leveraging generators Koa allows you to ditch callbacks and greatly increase error-handling. Koa does not bundle any middleware. ...

  • Restify
    Restify

    A Node.js web service framework optimized for building semantically correct RESTful web services ready for production use at scale. it optimizes for introspection and performance. ...

  • hapi
    hapi

    hapi is a simple to use configuration-centric framework with built-in support for input validation, caching, authentication, and other essential facilities for building web applications and services. ...

  • Golang
    Golang

    Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. ...

  • ExpressJS
    ExpressJS

    Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications. ...

  • NestJS
    NestJS

    Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming). Under the hood, Nest makes use of Express, but also, provides compatibility with a wide range of other libraries, like e.g. Fastify, allowing for easy use of the myriad third-party plugins which are available. ...

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

Fastify alternatives & related posts

Koa logo

Koa

715
483
12
Next generation web framework for node.js
715
483
+ 1
12
PROS OF KOA
  • 6
    Async/Await
  • 5
    JavaScript
  • 1
    REST API
CONS OF KOA
    Be the first to leave a con

    related Koa posts

    ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

    ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

    React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

    styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

    React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

    Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

    See more
    Antonio Kobashikawa
    Web developer | Blogger | Freelancer at Rulo Kobashikawa · | 6 upvotes · 239.4K views

    We are using Node.js and ExpressJS to build a REST services that is middleware of a legacy system. MongoDB as database. Vue.js helps us to make rapid UI to test use cases. Frontend is build for mobile with Ionic . We like using JavaScript and ES6 .

    I think next step could be to use Koa but I am not sure.

    See more
    Restify logo

    Restify

    80
    129
    1
    node.js REST framework specifically meant for web service APIs
    80
    129
    + 1
    1
    PROS OF RESTIFY
    • 1
      Semantically REST correctness
    CONS OF RESTIFY
      Be the first to leave a con

      related Restify posts

      hapi logo

      hapi

      433
      451
      87
      Server Framework for Node.js
      433
      451
      + 1
      87
      PROS OF HAPI
      • 27
        Makes me Hapi making REST APIs
      • 14
        Simpler than other REST libraries
      • 14
        Configuration
      • 13
        Quality Driven Ecosystem
      • 13
        Modularization
      • 5
        Easy testability
      • 1
        Better validation
      • 0
        Restify
      CONS OF HAPI
        Be the first to leave a con

        related hapi posts

        Tim Nolet

        Heroku Docker GitHub Node.js hapi Vue.js AWS Lambda Amazon S3 PostgreSQL Knex.js Checkly is a fairly young company and we're still working hard to find the correct mix of product features, price and audience.

        We are focussed on tech B2B, but I always wanted to serve solo developers too. So I decided to make a $7 plan.

        Why $7? Simply put, it seems to be a sweet spot for tech companies: Heroku, Docker, Github, Appoptics (Librato) all offer $7 plans. They must have done a ton of research into this, so why not piggy back that and try it out.

        Enough biz talk, onto tech. The challenges were:

        • Slice of a portion of the functionality so a $7 plan is still profitable. We call this the "plan limits"
        • Update API and back end services to handle and enforce plan limits.
        • Update the UI to kindly state plan limits are in effect on some part of the UI.
        • Update the pricing page to reflect all changes.
        • Keep the actual processing backend, storage and API's as untouched as possible.

        In essence, we went from strictly volume based pricing to value based pricing. Here come the technical steps & decisions we made to get there.

        1. We updated our PostgreSQL schema so plans now have an array of "features". These are string constants that represent feature toggles.
        2. The Vue.js frontend reads these from the vuex store on login.
        3. Based on these values, the UI has simple v-if statements to either just show the feature or show a friendly "please upgrade" button.
        4. The hapi API has a hook on each relevant API endpoint that checks whether a user's plan has the feature enabled, or not.

        Side note: We offer 10 SMS messages per month on the developer plan. However, we were not actually counting how many people were sending. We had to update our alerting daemon (that runs on Heroku and triggers SMS messages via AWS SNS) to actually bump a counter.

        What we build is basically feature-toggling based on plan features. It is very extensible for future additions. Our scheduling and storage backend that actually runs users' monitoring requests (AWS Lambda) and stores the results (S3 and Postgres) has no knowledge of all of this and remained unchanged.

        Hope this helps anyone building out their SaaS and is in a similar situation.

        See more
        Tim Nolet

        JavaScript Node.js hapi Vue.js Swagger UI Slate

        Two weeks ago we released the public API for Checkly. We already had an API that was serving our frontend Vue.js app. We decided to create an new set of API endpoints and not reuse the already existing one. The blog post linked below details what parts we needed to refactor, what parts we added and how we handled generating API documentation. More specifically, the post dives into:

        • Refactoring the existing Hapi.js based API
        • API key based authentication
        • Refactoring models with Objection.js
        • Validating plan limits
        • Generating Swagger & Slate based documentation
        See more
        Golang logo

        Golang

        22.2K
        13.7K
        3.3K
        An open source programming language that makes it easy to build simple, reliable, and efficient software
        22.2K
        13.7K
        + 1
        3.3K
        PROS OF GOLANG
        • 548
          High-performance
        • 395
          Simple, minimal syntax
        • 363
          Fun to write
        • 301
          Easy concurrency support via goroutines
        • 273
          Fast compilation times
        • 193
          Goroutines
        • 180
          Statically linked binaries that are simple to deploy
        • 150
          Simple compile build/run procedures
        • 136
          Backed by google
        • 136
          Great community
        • 53
          Garbage collection built-in
        • 45
          Built-in Testing
        • 44
          Excellent tools - gofmt, godoc etc
        • 39
          Elegant and concise like Python, fast like C
        • 37
          Awesome to Develop
        • 26
          Used for Docker
        • 25
          Flexible interface system
        • 24
          Deploy as executable
        • 24
          Great concurrency pattern
        • 20
          Open-source Integration
        • 18
          Easy to read
        • 17
          Fun to write and so many feature out of the box
        • 16
          Go is God
        • 14
          Easy to deploy
        • 14
          Powerful and simple
        • 14
          Its Simple and Heavy duty
        • 13
          Best language for concurrency
        • 13
          Concurrency
        • 11
          Rich standard library
        • 11
          Safe GOTOs
        • 10
          Clean code, high performance
        • 10
          Easy setup
        • 9
          High performance
        • 9
          Simplicity, Concurrency, Performance
        • 8
          Hassle free deployment
        • 8
          Single binary avoids library dependency issues
        • 7
          Gofmt
        • 7
          Cross compiling
        • 7
          Simple, powerful, and great performance
        • 7
          Used by Giants of the industry
        • 6
          Garbage Collection
        • 5
          Very sophisticated syntax
        • 5
          Excellent tooling
        • 5
          WYSIWYG
        • 4
          Keep it simple and stupid
        • 4
          Widely used
        • 4
          Kubernetes written on Go
        • 2
          No generics
        • 1
          Operator goto
        • 1
          Looks not fancy, but promoting pragmatic idioms
        CONS OF GOLANG
        • 42
          You waste time in plumbing code catching errors
        • 25
          Verbose
        • 23
          Packages and their path dependencies are braindead
        • 16
          Google's documentations aren't beginer friendly
        • 15
          Dependency management when working on multiple projects
        • 10
          Automatic garbage collection overheads
        • 8
          Uncommon syntax
        • 7
          Type system is lacking (no generics, etc)
        • 5
          Collection framework is lacking (list, set, map)
        • 3
          Best programming language
        • 1
          A failed experiment to combine c and python

        related Golang posts

        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
        Nick Parsons
        Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 3.9M views

        Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

        We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

        We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

        Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

        #FrameworksFullStack #Languages

        See more
        ExpressJS logo

        ExpressJS

        31.5K
        23.4K
        1.6K
        Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
        31.5K
        23.4K
        + 1
        1.6K
        PROS OF EXPRESSJS
        • 380
          Simple
        • 336
          Node.js
        • 244
          Javascript
        • 193
          High performance
        • 152
          Robust routing
        • 73
          Middlewares
        • 71
          Open source
        • 59
          Great community
        • 37
          Hybrid web applications
        • 16
          Well documented
        • 9
          Rapid development
        • 9
          Sinatra inspired
        • 7
          Socket connection
        • 7
          Isomorphic js.. superfast and easy
        • 5
          Light weight
        • 4
          Resource available for learning
        • 4
          Npm
        • 3
          Event loop
        • 3
          Callbacks
        • 2
          Data stream
        CONS OF EXPRESSJS
        • 27
          Not python
        • 17
          Overrated
        • 14
          No multithreading
        • 9
          Javascript
        • 5
          Not fast
        • 3
          Easily Insecure for Novices

        related ExpressJS posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.8M views

        Our whole Node.js backend stack consists of the following tools:

        • Lerna as a tool for multi package and multi repository management
        • npm as package manager
        • NestJS as Node.js framework
        • TypeScript as programming language
        • ExpressJS as web server
        • Swagger UI for visualizing and interacting with the API’s resources
        • Postman as a tool for API development
        • TypeORM as object relational mapping layer
        • JSON Web Token for access token management

        The main reason we have chosen Node.js over PHP is related to the following artifacts:

        • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
        • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
        • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
        • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
        See more

        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
        NestJS logo

        NestJS

        2.4K
        2.9K
        326
        A progressive Node.js framework for building efficient and scalable server-side applications by @kammysliwiec.
        2.4K
        2.9K
        + 1
        326
        PROS OF NESTJS
        • 54
          Powerful but super friendly to work with
        • 42
          Fast development
        • 40
          Easy to understand documentation
        • 36
          Angular style syntax for the backend
        • 32
          NodeJS ecosystem
        • 31
          Typescript
        • 27
          Its easy to understand since it follows angular syntax
        • 18
          Good architecture
        • 13
          Integrates with Narwhal Extensions
        • 12
          Typescript makes it well integrated in vscode
        • 8
          Graphql support easy
        • 7
          Agnosticism
        • 5
          Easily integrate with others external extensions
        • 1
          Official courses
        CONS OF NESTJS
        • 10
          Difficult to debug
        • 10
          User base is small. Less help on Stackoverflow
        • 5
          Angular-like architecture
        • 3
          Updates with breaking changes
        • 3
          Javascript
        • 1
          Frontend in backend
        • 1
          Unstable

        related NestJS posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.8M views

        Our whole Node.js backend stack consists of the following tools:

        • Lerna as a tool for multi package and multi repository management
        • npm as package manager
        • NestJS as Node.js framework
        • TypeScript as programming language
        • ExpressJS as web server
        • Swagger UI for visualizing and interacting with the API’s resources
        • Postman as a tool for API development
        • TypeORM as object relational mapping layer
        • JSON Web Token for access token management

        The main reason we have chosen Node.js over PHP is related to the following artifacts:

        • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
        • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
        • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
        • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
        See more
        Jan Vlnas
        Developer Advocate at Superface · | 12 upvotes · 323.6K views

        Our framework of choice for backend at Superface is NestJS. We also use AppSignal for APM and error tracking. While AppSignal provides some basic integration for Node.js, getting the monitoring to work with Nest was a bit tricky. Check out our blog post on Integrating AppSignal APM with NestJS how we made it work.

        See more
        JavaScript logo

        JavaScript

        352.3K
        268.2K
        8.1K
        Lightweight, interpreted, object-oriented language with first-class functions
        352.3K
        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.3K
        174.8K
        6.6K
        Fast, scalable, distributed revision control system
        291.3K
        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