Need advice about which tool to choose?Ask the StackShare community!
InfluxDB vs Microsoft SQL Server: What are the differences?
What is InfluxDB? An open-source distributed time series database with no external dependencies. 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..
What is Microsoft SQL Server? 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.
InfluxDB and Microsoft SQL Server can be categorized as "Databases" tools.
"Time-series data analysis" is the top reason why over 35 developers like InfluxDB, while over 134 developers mention "Reliable and easy to use" as the leading cause for choosing Microsoft SQL Server.
InfluxDB is an open source tool with 16.6K GitHub stars and 2.37K GitHub forks. Here's a link to InfluxDB'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 InfluxDB, which is listed in 116 company stacks and 38 developer stacks.
What is InfluxDB?
What is Microsoft SQL Server?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose InfluxDB?
Why do developers choose Microsoft SQL Server?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using InfluxDB?
What are the cons of using Microsoft SQL Server?
What companies use InfluxDB?
What companies use Microsoft SQL Server?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Microsoft SQL Server?
Sign up to get full access to all the tool integrationsMake informed product decisions
We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.
We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.
In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.
Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache
InfluxDBInflux doesn't currently natively support horizontal distribution. Hard to recommend it until they implement that.
InfluxDBWe use InfluxDB as a store for our data that gets fed into Grafana. It's ideal for this as it's a lightweight storage engine that can be modified on the fly by scripts without having to log into the server itself and manage tables. The HTTP API also makes it ideal for integrating with frontend services.
Microsoft SQL ServerWe've always counted on SQL Server as our database backend. It has served us well over the years. It isn't the cheapest part of our stack, but with the plethora of tools provided by 3rd parties, we have found an incredible and scalable method of keeping our data available and easy to maintain.
Microsoft SQL ServerDefacto, industry standard for backend relational databases. Entity Framework makes designing, migrating & maintaining SQL Server databases a breeze. LocalDB is especially helpful during development.
Microsoft SQL ServerOur core systems that we integrate with are using SQL Server 2012 / 2016 database servers. We use database views on core system databases to help build our domain model.
Microsoft SQL ServerMain transactional database. SQL Server 2012 Enterprise with AlwaysOn Availability Groups for high availability and disaster recovery.
InfluxDBTo track time-series of course, utilizing few retention rules and continuous queries to keep time-series data fast and maintanable
InfluxDBInfluxDB ingests information from various sources (mostly Telegraf instances) into one place for monitoring purposes.
InfluxDBAll our metrics go through InfluxDB, both applicative and system
Microsoft SQL ServerManaging script output and input, as well as data cleansing.