Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Node.js
Node.js

38K
31.9K
+ 1
8K
Sinatra
Sinatra

443
342
+ 1
209
Add tool

Node.js vs Sinatra: What are the differences?

Node.js: A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices; Sinatra: Classy web-development dressed in a DSL. Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort.

Node.js can be classified as a tool in the "Frameworks (Full Stack)" category, while Sinatra is grouped under "Microframeworks (Backend)".

"Npm" is the primary reason why developers consider Node.js over the competitors, whereas "Lightweight" was stated as the key factor in picking Sinatra.

Node.js and Sinatra are both open source tools. It seems that Node.js with 35.5K GitHub stars and 7.78K forks on GitHub has more adoption than Sinatra with 10.6K GitHub stars and 1.89K GitHub forks.

reddit, Slack, and MIT are some of the popular companies that use Node.js, whereas Sinatra is used by SendGrid, thoughtbot, and New Relic. Node.js has a broader approval, being mentioned in 4055 company stacks & 3897 developers stacks; compared to Sinatra, which is listed in 92 company stacks and 33 developer stacks.

What is Node.js?

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

What is Sinatra?

Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Node.js?
Why do developers choose Sinatra?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    What companies use Node.js?
    What companies use Sinatra?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Node.js?
    What tools integrate with Sinatra?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Node.js and Sinatra?
    AngularJS
    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.
    PHP
    Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.
    Python
    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
    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.
    React
    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
    See all alternatives
    Decisions about Node.js and Sinatra
    Spenser Coke
    Spenser Coke
    Product Engineer at Loanlink.de · | 9 upvotes · 227.3K views
    atLoanlink GmbhLoanlink Gmbh
    Rails
    Rails
    AngularJS
    AngularJS
    .NET
    .NET
    Node.js
    Node.js
    React
    React
    GitHub
    GitHub
    Trello
    Trello
    Zapier
    Zapier
    Mailchimp
    Mailchimp
    Google Drive
    Google Drive
    Vue.js
    Vue.js
    HTML5
    HTML5

    When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

    The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

    We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

    We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

    See more
    Sparker73
    Sparker73
    Frontend Developer · | 7 upvotes · 23.2K views
    Node.js
    Node.js
    JavaScript
    JavaScript
    .NET
    .NET
    PHP
    PHP

    Node.js is my choice because it uses very few resources to run and it is capable to handle tons of connections simultaneously. Most developers already know JavaScript, the evolution of ECMAScript is immediately reflected to Node.js and all you have to do is update your Server's Node.js version without time and effort. Thousands of improvements that makes it very powerful especially in asynchronous programming. The web is full of courses, dev communities, free sample code, plunkers and many knowledge sources on Node.js that facilitates the learning curve. What else we can ask from a legendary language that is still evolving? I am learning Node.js by developing a simple REST WebAPI and using it as a playground to test situations in which the main objective is to challenge Node.js and compare results and performance with .NET implementations and certain well known fast PHP implementations. Until now the results are astonishing. Summarizing: Node.js for backend is so far (in my opinion) the most recommended solution to get positive achievements in size, speed, power, concurrency, scalability, deployment and running costs.

    See more
    Antonio Sanchez
    Antonio Sanchez
    CEO at Kokoen GmbH · | 13 upvotes · 214.3K views
    atKokoen GmbHKokoen GmbH
    PHP
    PHP
    Laravel
    Laravel
    MySQL
    MySQL
    Go
    Go
    MongoDB
    MongoDB
    JavaScript
    JavaScript
    Node.js
    Node.js
    ExpressJS
    ExpressJS

    Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

    Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

    By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

    Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

    There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

    We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

    As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

    See more
    Zarema Khalilova
    Zarema Khalilova
    Frontend Team Lead at Uploadcare · | 8 upvotes · 64K views
    atUploadcareUploadcare
    Django
    Django
    Node.js
    Node.js
    React
    React
    Gatsby
    Gatsby
    Netlify
    Netlify
    #Frontend
    #StaticSiteGenerators
    #StaticWebHosting

    Since 2011 our frontend was in Django monolith. However, in 2016 we decide to separate #Frontend from Django for independent development and created the custom isomorphic app based on Node.js and React. Now we realized that not need all abilities of the server, and it is sufficient to generate a static site. Gatsby is suitable for our purposes. We can generate HTML from markdown and React views very simply. So, we are updating our frontend to Gatsby now, and maybe we will use Netlify for deployment soon. This will speed up the delivery of new features to production.

    #StaticSiteGenerators #StaticWebHosting

    See more
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare · | 22 upvotes · 515.3K views
    atStackShareStackShare
    React
    React
    Glamorous
    Glamorous
    Apollo
    Apollo
    Node.js
    Node.js
    Rails
    Rails
    Heroku
    Heroku
    GitHub
    GitHub
    Amazon S3
    Amazon S3
    Amazon CloudFront
    Amazon CloudFront
    Webpack
    Webpack
    CircleCI
    CircleCI
    Redis
    Redis
    #StackDecisionsLaunch
    #