IronDB vs Microsoft SQL Server

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

IronDB

1
11
+ 1
0
Microsoft SQL Server

12.6K
9.4K
+ 1
535
Add tool

IronDB vs Microsoft SQL Server: What are the differences?

Developers describe IronDB as "A resilient key-value store for the browser". IronDB is the best way to store persistent key-value data in the browser. Data saved to IronDB is redundantly stored in Cookies, IndexedDB, LocalStorage, and SessionStorage, and relentlessly self heals if any data therein is deleted or corrupted. 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.

IronDB and Microsoft SQL Server belong to "Databases" category of the tech stack.

IronDB is an open source tool with 5 GitHub stars and 1 GitHub forks. Here's a link to IronDB's open source repository on GitHub.

Advice on IronDB 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
PostgreSQL

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 · 66.8K views
Recommends
Amazon 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 · 67.2K 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
PostgreSQL

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 · 66.8K views
Recommends
PostgreSQL

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 IronDB
Pros of Microsoft SQL Server
    Be the first to leave a pro
    • 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 IronDB
    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

      - No public GitHub repository available -

      What is IronDB?

      IronDB is the best way to store persistent key-value data in the browser. Data saved to IronDB is redundantly stored in Cookies, IndexedDB, LocalStorage, and SessionStorage, and relentlessly self heals if any data therein is deleted or corrupted.

      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 IronDB?
      What companies use Microsoft SQL Server?
        No companies found
        See which teams inside your own company are using IronDB 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 IronDB?
        What tools integrate with Microsoft SQL Server?
          No integrations found

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

          What are some alternatives to IronDB and Microsoft SQL Server?
          InfluxDB
          InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.
          MySQL
          The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
          PostgreSQL
          PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
          MongoDB
          MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
          SQLite
          SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.
          See all alternatives