Microsoft SQL Server vs PerconaXtraDBCluster: What are the differences?
Developers describe Microsoft SQL Server 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. On the other hand, PerconaXtraDBCluster is detailed as "Percona XtraDB Cluster is an active/active high availability and high scalability open source solution for MySQL® clustering". Percona XtraDB Cluster is an active/active high availability and high scalability open source solution for MySQL® clustering. It integrates Percona Server and Percona XtraBackup with the Codership Galera library of MySQL high availability solutions in a single package that enables you to create a cost-effective MySQL high availability cluster.
Microsoft SQL Server and PerconaXtraDBCluster can be primarily classified as "Databases" tools.
What is Microsoft SQL Server?
What is PerconaXtraDBCluster?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose PerconaXtraDBCluster?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using PerconaXtraDBCluster?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with PerconaXtraDBCluster?
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
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.
Defacto, industry standard for backend relational databases. Entity Framework makes designing, migrating & maintaining SQL Server databases a breeze. LocalDB is especially helpful during development.
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.
Main transactional database. SQL Server 2012 Enterprise with AlwaysOn Availability Groups for high availability and disaster recovery.
Managing script output and input, as well as data cleansing.