Microsoft SQL Server vs. MariaDB vs. Kyoto Tycoon

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?

수 백만개가 넘는 태그 키워드의 자동완성을 위해서 별도의 데이터베이스를 구축하였습니다. MariaDB 는 MySQL 을 포크한 프로젝트입니다. MySQL 과의 강력한 호환성을 지니며, 큰 튜닝 없이 강력한 성능을 보장합니다.

Replacement for MySQL

Legacy systems

Holds our user account and results data.

OTLP

Faster than MySQL

DB

We have query-builder for SQL, and mostly using it for MariaDB.

Database

mysql보다 mariaDB가 join면에서 우수하다는 문서를 읽었습니다. 이 부분은 저의 블로그에서도 다뤘고 저의 word press 블로그는 mysql 대신 mariaDB 를 사용합니다.

특히 limit 기능이 pagenation 처리를 할 때 너무 직관적이고 편해서 mariaDB, mysql을 사랑합니다.

Used MariaDB as drop-in replacement on AWS server to act as RESTful API database in web application.

Aside from Redis, we use MariaDB to store long-term information like user-data and big-data like regeneration-information for our open-world servers. We extensively use the relational aspects of MariaDB in joins, nested queries and unions.

MariaDB is our database service.

MariaDB is used the same way as MySQL, except that MariaDB is used on our arch-based servers.

Back-end storage

Data persistence

Used in Docker local development

MariaDB has allowed us to easily scale out our DB cluster. Also has better replication tools than MySQL

We use MariaDB because it is fast, free and integrates well with the frameworks we are using.

On our servers, we use MariaDB as alternative to MySQL.

MariaDB Galera Cluster is the primary data store

A much better solution for an efficient database (compared to standard mySQL).

Introduced in computer science course.

Free and Open Source

Database used on the server

We hate Oracle.