Microsoft SQL Server vs. CouchDB vs. Citus

We'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.

Product back end and reporting

Managing script output and input, as well as data cleansing.

Main transactional database. SQL Server 2012 Enterprise with AlwaysOn Availability Groups for high availability and disaster recovery.

Users and companies are stored in SQL Server

Integration with LOB systems.

Our beloved DB.

Back End: DataBase

社内サーバー

This is database for all Windows applications.

Stores rules for PRS

Datastorage

My go to database when working with Microsoft Technologies.

Data source from the data warehouse.

UI & administration data.

Azure SQL service to use as a main storage

for BI

Backing database for several distinct APIs

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

Everyone needs a robust database, right?

By being built on, of, in and around CouchDB, Smileupps offers to its customers secure and reliable CouchDB hosting and a CouchDB-based app store to build and sell serious business-enabled web applications

Storage for unstructured, linked and timeseries data.

We use CouchDB in an internal analysis tool for usage data.

json store + geo + _changes

Document (JSON) DB.

• - queries must be pre-defined as views (not as flexible as query formulation on the fly)
• - community and ecosystem not as large as mongodb
• + PouchDB is an excellent JS library to interact with CouchDB or even work in offline-then-sync moce