Amazon ElastiCache vs Microsoft SQL Server: What are the differences?
Developers describe Amazon ElastiCache as "Deploy, operate, and scale an in-memory cache in the cloud". ElastiCache improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory caches, instead of relying entirely on slower disk-based databases. ElastiCache supports Memcached and Redis. On the other hand, Microsoft SQL Server is detailed 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.
Amazon ElastiCache belongs to "Managed Memcache" category of the tech stack, while Microsoft SQL Server can be primarily classified under "Databases".
"Redis" is the top reason why over 53 developers like Amazon ElastiCache, while over 134 developers mention "Reliable and easy to use" as the leading cause for choosing Microsoft SQL Server.
According to the StackShare community, Microsoft SQL Server has a broader approval, being mentioned in 470 company stacks & 425 developers stacks; compared to Amazon ElastiCache, which is listed in 342 company stacks and 79 developer stacks.
What is Amazon ElastiCache?
What is Microsoft SQL Server?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon ElastiCache?
Sign up to get full access to all the companiesMake informed product decisions
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 decided to use MemCachier as our Memcached provider because we were seeing some serious PostgreSQL performance issues with query-heavy pages on the site. We use MemCachier for all Rails caching and pretty aggressively too for the logged out experience (fully cached pages for the most part). We really need to move to Amazon ElastiCache as soon as possible so we can stop paying so much. The only reason we're not moving is because there are some restrictions on the network side due to our main app being hosted on Heroku.
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.
I use a micro elesticache instance as a shared session store between the Node.js clusters of dojo.zerotoherojs.com and nightly.zerotoherojs.com
Main transactional database. SQL Server 2012 Enterprise with AlwaysOn Availability Groups for high availability and disaster recovery.
Audit the ElastiCache configurations for best practices and standards.
Managing script output and input, as well as data cleansing.