Knex.js vs Microsoft SQL Server

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

Knex.js

145
331
+ 1
42
Microsoft SQL Server

13.4K
10K
+ 1
536
Add tool

Knex.js vs Microsoft SQL Server: What are the differences?

Developers describe Knex.js as "SQL query builder for Postgres, MySQL, MariaDB, SQLite3, and Oracle". Knex.js is a "batteries included" SQL query builder for Postgres, MySQL, MariaDB, SQLite3, and Oracle designed to be flexible, portable, and fun to use. It features both traditional node style callbacks as well as a promise interface for cleaner async flow control, a stream interface, full featured query and schema builders, transaction support (with savepoints), connection pooling and standardized responses between different query clients and dialects. On the other hand, Microsoft SQL Server is detailed as "A relational database management system developed by Microsoft". Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

Knex.js belongs to "Database Tools" category of the tech stack, while Microsoft SQL Server can be primarily classified under "Databases".

"Write once and then connect to almost any sql engine" is the primary reason why developers consider Knex.js over the competitors, whereas "Reliable and easy to use" was stated as the key factor in picking Microsoft SQL Server.

Knex.js is an open source tool with 9.79K GitHub stars and 1.22K GitHub forks. Here's a link to Knex.js's open source repository on GitHub.

According to the StackShare community, Microsoft SQL Server has a broader approval, being mentioned in 470 company stacks & 425 developers stacks; compared to Knex.js, which is listed in 10 company stacks and 9 developer stacks.

Advice on Knex.js and Microsoft SQL Server

I am a Microsoft SQL Server programmer who is a bit out of practice. I have been asked to assist on a new project. The overall purpose is to organize a large number of recordings so that they can be searched. I have an enormous music library but my songs are several hours long. I need to include things like time, date and location of the recording. I don't have a problem with the general database design. I have two primary questions:

  1. I need to use either MySQL or PostgreSQL on a Linux based OS. Which would be better for this application?
  2. I have not dealt with a sound based data type before. How do I store that and put it in a table? Thank you.
See more
Replies (6)

Hi Erin,

Honestly both databases will do the job just fine. I personally prefer Postgres.

Much more important is how you store the audio. While you could technically use a blob type column, it's really not ideal to be storing audio files which are "several hours long" in a database row. Instead consider storing the audio files in an object store (hosted options include backblaze b2 or aws s3) and persisting the key (which references that object) in your database column.

See more
Aaron Westley
Recommends
PostgreSQLPostgreSQL

Hi Erin, Chances are you would want to store the files in a blob type. Both MySQL and Postgres support this. Can you explain a little more about your need to store the files in the database? I may be more effective to store the files on a file system or something like S3. To answer your qustion based on what you are descibing I would slighly lean towards PostgreSQL since it tends to be a little better on the data warehousing side.

See more
Julien DeFrance
Principal Software Engineer at Tophatter · | 3 upvotes · 111.2K views
Recommends
Amazon AuroraAmazon Aurora

Hi Erin! First of all, you'd probably want to go with a managed service. Don't spin up your own MySQL installation on your own Linux box. If you are on AWS, thet have different offerings for database services. Standard RDS vs. Aurora. Aurora would be my preferred choice given the benefits it offers, storage optimizations it comes with... etc. Such managed services easily allow you to apply new security patches and upgrades, set up backups, replication... etc. Doing this on your own would either be risky, inefficient, or you might just give up. As far as which database to chose, you'll have the choice between Postgresql, MySQL, Maria DB, SQL Server... etc. I personally would recommend MySQL (latest version available), as the official tooling for it (MySQL Workbench) is great, stable, and moreover free. Other database services exist, I'd recommend you also explore Dynamo DB.

Regardless, you'd certainly only keep high-level records, meta data in Database, and the actual files, most-likely in S3, so that you can keep all options open in terms of what you'll do with them.

See more
Christopher Wray
Web Developer at Soltech LLC · | 3 upvotes · 111.6K views

Hey Erin! I would recommend checking out Directus before you start work on building your own app for them. I just stumbled upon it, and so far extremely happy with the functionalities. If your client is just looking for a simple web app for their own data, then Directus may be a great option. It offers "database mirroring", so that you can connect it to any database and set up functionality around it!

See more
Recommends
PostgreSQLPostgreSQL

Hi Erin,

  • Coming from "Big" DB engines, such as Oracle or MSSQL, go for PostgreSQL. You'll get all the features you need with PostgreSQL.
  • Your case seems to point to a "NoSQL" or Document Database use case. Since you get covered on this with PostgreSQL which achieves excellent performances on JSON based objects, this is a second reason to choose PostgreSQL. MongoDB might be an excellent option as well if you need "sharding" and excellent map-reduce mechanisms for very massive data sets. You really should investigate the NoSQL option for your use case.
  • Starting with AWS Aurora is an excellent advise. since "vendor lock-in" is limited, but I did not check for JSON based object / NoSQL features.
  • If you stick to Linux server, the PostgreSQL or MySQL provided with your distribution are straightforward to install (i.e. apt install postgresql). For PostgreSQL, make sure you're comfortable with the pg_hba.conf, especially for IP restrictions & accesses.

Regards,

See more
Klaus Nji
Staff Software Engineer at SailPoint Technologies · | 1 upvotes · 111.2K views
Recommends
PostgreSQLPostgreSQL

I recommend Postgres as well. Superior performance overall and a more robust architecture.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Knex.js
Pros of Microsoft SQL Server
  • 9
    Write once and then connect to almost any sql engine
  • 8
    Faster
  • 7
    Flexibility in what engine you choose
  • 7
    Nice api, Migrations/Seeds
  • 7
    Free
  • 4
    Multi support and easy to use
  • 137
    Reliable and easy to use
  • 101
    High performance
  • 94
    Great with .net
  • 65
    Works well with .net
  • 56
    Easy to maintain
  • 21
    Azure support
  • 17
    Always on
  • 17
    Full Index Support
  • 10
    Enterprise manager is fantastic
  • 9
    In-Memory OLTP Engine
  • 2
    Security is forefront
  • 1
    Columnstore indexes
  • 1
    Great documentation
  • 1
    Faster Than Oracle
  • 1
    Decent management tools
  • 1
    Easy to setup and configure
  • 1
    Docker Delivery

Sign up to add or upvote prosMake informed product decisions

Cons of Knex.js
Cons of Microsoft SQL Server
    Be the first to leave a con
    • 4
      Expensive Licensing
    • 2
      Microsoft

    Sign up to add or upvote consMake informed product decisions

    What is Knex.js?

    Knex.js is a "batteries included" SQL query builder for Postgres, MySQL, MariaDB, SQLite3, and Oracle designed to be flexible, portable, and fun to use. It features both traditional node style callbacks as well as a promise interface for cleaner async flow control, a stream interface, full featured query and schema builders, transaction support (with savepoints), connection pooling and standardized responses between different query clients and dialects.

    What is Microsoft SQL Server?

    Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

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

    What companies use Knex.js?
    What companies use Microsoft SQL Server?
    See which teams inside your own company are using Knex.js or Microsoft SQL Server.
    Sign up for Private StackShareLearn More

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

    What tools integrate with Knex.js?
    What tools integrate with Microsoft SQL Server?

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

    What are some alternatives to Knex.js and Microsoft SQL Server?
    Sequelize
    Sequelize is a promise-based ORM for Node.js and io.js. It supports the dialects PostgreSQL, MySQL, MariaDB, SQLite and MSSQL and features solid transaction support, relations, read replication and more.
    Slick
    It is a modern database query and access library for Scala. It allows you to work with stored data almost as if you were using Scala collections while at the same time giving you full control over when a database access happens and which data is transferred.
    Spring Data
    It makes it easy to use data access technologies, relational and non-relational databases, map-reduce frameworks, and cloud-based data services. This is an umbrella project which contains many subprojects that are specific to a given database.
    DataGrip
    A cross-platform IDE that is aimed at DBAs and developers working with SQL databases.
    Microsoft SQL Server Management Studio
    It is an integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. It provides tools to configure, monitor, and administer instances of SQL Server and databases. Use it to deploy, monitor, and upgrade the data-tier components used by your applications, as well as build queries and scripts.
    See all alternatives