Vitess: A Distributed Scalable Database Architecture

Vitess is a database clustering system for horizontal scaling of MySQL through sharding. By enabling shard-routing logic, Vitess allows application code and database queries to remain agnostic to data distribution onto multiple shards. With Vitess, you can split, merge, and migrate shards as your needs grow. With its compatibility with development frameworks and integration to open-source tools, Vitess has been a core component of several high-traffic OLTP sites worldwide and serves data across different platforms.

Alkin Tezuysal has extensive experience in enterprise relational databases, working in various sectors for large corporations. With more than 20 years of industry experience, he has acquired skills for managing large projects from the ground up to production. For the past decade, he’s been focused on e-commerce, SaaS, and MySQL technologies. Alkin has managed and architected database topologies for high-volume sites at eBay Intl. He has several years of experience in 24X7 support and operational tasks and improving database systems for major companies. He has led global operations teams on Tier 1/2/3 support for MySQL customers.
In late 2020, he joined PlanetScale’s expert engineering team over Vitess.

#vitess #database

What is GEEK

Buddha Community

Decentralized Databases Reduce Data Latency With Geographically Distributed Data Centers

More often than not, that external server is a monolithic database residing in a single cloud region. This article will dig into some of the existing architectures that cause this issue and provide solutions on how to resolve them.

Latency Defined

The Problem: A Centralized Database

Real-World Examples

IoT-based Smart Homes

Autonomous Vehicles

…

#database #cloud #architecture #distributed-systems #what-cause-latency #distributed-computing #databases #cloud-computing

Industries That Need a High Performing Low Latency Distributed Database

Many edge data solutions are not write optimized, global replication is slow, and options for horizontal scaling are limited.

There are certain industries that greatly benefit from high-performing, low-latency, geo-distributed technologies, while other organizations might be more focused on vertically scaling architectures. This is dependent on numerous factors including the data pipeline, network, data structure, type of product or solution, short and long-term goals, etc. While there are currently many databases and tools that provide vertical scaling capabilities, there are not many that focus on horizontal scaling – but there’s still a need for both.

Latency

Geo-Distributed

Scaling

Industry-Based Examples

…

#cloud #performance and monitoring #distributed computing #latency #database as a service #horizontal scalability #database choice #edge architecture #distributed data center #scaling applications

System Databases in SQL Server

Introduction

In SSMS, we many of may noticed System Databases under the Database Folder. But how many of us knows its purpose?. In this article lets discuss about the System Databases in SQL Server.

System Database

Fig. 1 System Databases

There are five system databases, these databases are created while installing SQL Server.

• Master
• Model
• MSDB
• Tempdb
• Resource

Master

• This database contains all the System level Information in SQL Server. The Information in form of Meta data.
• Because of this master database, we are able to access the SQL Server (On premise SQL Server)

Model

• This database is used as a template for new databases.
• Whenever a new database is created, initially a copy of model database is what created as new database.

MSDB

• This database is where a service called SQL Server Agent stores its data.
• SQL server Agent is in charge of automation, which includes entities such as jobs, schedules, and alerts.

TempDB

• The Tempdb is where SQL Server stores temporary data such as work tables, sort space, row versioning information and etc.
• User can create their own version of temporary tables and those are stored in Tempdb.
• But this database is destroyed and recreated every time when we restart the instance of SQL Server.

Resource

• The resource database is a hidden, read only database that holds the definitions of all system objects.
• When we query system object in a database, they appear to reside in the sys schema of the local database, but in actually their definitions reside in the resource db.

#sql server #master system database #model system database #msdb system database #sql server system databases #ssms #system database #system databases in sql server #tempdb system database

Vitess: A Distributed Scalable Database Architecture

Vitess is a database clustering system for horizontal scaling of MySQL through sharding. By enabling shard-routing logic, Vitess allows application code and database queries to remain agnostic to data distribution onto multiple shards. With Vitess, you can split, merge, and migrate shards as your needs grow. With its compatibility with development frameworks and integration to open-source tools, Vitess has been a core component of several high-traffic OLTP sites worldwide and serves data across different platforms.

Alkin Tezuysal has extensive experience in enterprise relational databases, working in various sectors for large corporations. With more than 20 years of industry experience, he has acquired skills for managing large projects from the ground up to production. For the past decade, he’s been focused on e-commerce, SaaS, and MySQL technologies. Alkin has managed and architected database topologies for high-volume sites at eBay Intl. He has several years of experience in 24X7 support and operational tasks and improving database systems for major companies. He has led global operations teams on Tier 1/2/3 support for MySQL customers.
In late 2020, he joined PlanetScale’s expert engineering team over Vitess.

#vitess #database

Five Principles That Guide TiDB and PingCAP

PingCAP’s CEO talks about the philosophy of TiDB’s evolution and how PingCAP built TiDB in the past five years using user feedback along the way.

This article is based on a talk given by Max Liu at PingCAP Infra Meetup.

TiDB is an open source, distributed SQL database started by PingCAP. As the CEO of PingCAP, I’m also TiDB’s principal product manager, with veto power on the important features of our product. Rather than adding more features, my duty at PingCAP is to cut down unnecessary features so that TiDB stays focused yet flexible.

In this post, I will talk about the philosophy behind TiDB’s evolution, and, as a product manager, how I figured out where TiDB would be going and how we finally got there.

TiDB’s Evolution Philosophy

What’s Next

#sql database #newsql #distributed architecture #database development #distributed sql databases #database development company