Microsoft SQL Server vs Serverless

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Microsoft SQL Server
Microsoft SQL Server

3.8K
2.7K
+ 1
525
Serverless
Serverless

460
368
+ 1
17
Add tool

Microsoft SQL Server vs Serverless: 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, Serverless is detailed as "The most widely-adopted toolkit for building serverless applications". Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.

Microsoft SQL Server and Serverless are primarily classified as "Databases" and "Serverless / Task Processing" tools respectively.

"Reliable and easy to use" is the top reason why over 134 developers like Microsoft SQL Server, while over 10 developers mention "API integration " as the leading cause for choosing Serverless.

Serverless is an open source tool with 30.5K GitHub stars and 3.38K GitHub forks. Here's a link to Serverless's open source repository on GitHub.

According to the StackShare community, Microsoft SQL Server has a broader approval, being mentioned in 470 company stacks & 425 developers stacks; compared to Serverless, which is listed in 112 company stacks and 43 developer stacks.

- No public GitHub repository available -

What is Microsoft SQL Server?

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

What is Serverless?

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Microsoft SQL Server?
Why do developers choose Serverless?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use Microsoft SQL Server?
    What companies use Serverless?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Microsoft SQL Server?
    What tools integrate with Serverless?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to Microsoft SQL Server and Serverless?
    Oracle
    Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.
    Apache Aurora
    Apache Aurora is a service scheduler that runs on top of Mesos, enabling you to run long-running services that take advantage of Mesos' scalability, fault-tolerance, and resource isolation.
    PostgreSQL
    PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
    Microsoft Access
    It is an easy-to-use tool for creating business applications, from templates or from scratch. With its rich and intuitive design tools, it can help you create appealing and highly functional applications in a minimal amount of time.
    MySQL
    The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.
    See all alternatives
    Decisions about Microsoft SQL Server and Serverless
    Nitzan Shapira
    Nitzan Shapira
    at Epsagon · | 11 upvotes · 107.2K views
    atEpsagonEpsagon
    AWS Lambda
    AWS Lambda
    GitHub
    GitHub
    Java
    Java
    Go
    Go
    Node.js
    Node.js
    npm
    npm
    Serverless
    Serverless
    Python
    Python

    At Epsagon, we use hundreds of AWS Lambda functions, most of them are written in Python, and the Serverless Framework to pack and deploy them. One of the issues we've encountered is the difficulty to package external libraries into the Lambda environment using the Serverless Framework. This limitation is probably by design since the external code your Lambda needs can be usually included with a package manager.

    In order to overcome this issue, we've developed a tool, which we also published as open-source (see link below), which automatically packs these libraries using a simple npm package and a YAML configuration file. Support for Node.js, Go, and Java will be available soon.

    The GitHub respoitory: https://github.com/epsagon/serverless-package-external

    See more
    Michal Nowak
    Michal Nowak
    Co-founder at Evojam · | 7 upvotes · 63.6K views
    atEvojamEvojam
    Azure Functions
    Azure Functions
    Firebase
    Firebase
    AWS Lambda
    AWS Lambda
    Serverless
    Serverless

    In a couple of recent projects we had an opportunity to try out the new Serverless approach to building web applications. It wasn't necessarily a question if we should use any particular vendor but rather "if" we can consider serverless a viable option for building apps. Obviously our goal was also to get a feel for this technology and gain some hands-on experience.

    We did consider AWS Lambda, Firebase from Google as well as Azure Functions. Eventually we went with AWS Lambdas.

    PROS
    • No servers to manage (obviously!)
    • Limited fixed costs – you pay only for used time
    • Automated scaling and balancing
    • Automatic failover (or, at this level of abstraction, no failover problem at all)
    • Security easier to provide and audit
    • Low overhead at the start (with the certain level of knowledge)
    • Short time to market
    • Easy handover - deployment coupled with code
    • Perfect choice for lean startups with fast-paced iterations
    • Augmentation for the classic cloud, server(full) approach
    CONS
    • Not much know-how and best practices available about structuring the code and projects on the market
    • Not suitable for complex business logic due to the risk of producing highly coupled code
    • Cost difficult to estimate (helpful tools: serverlesscalc.com)
    • Difficulty in migration to other platforms (Vendor lock⚠️)
    • Little engineers with experience in serverless on the job market
    • Steep learning curve for engineers without any cloud experience

    More details are on our blog: https://evojam.com/blog/2018/12/5/should-you-go-serverless-meet-the-benefits-and-flaws-of-new-wave-of-cloud-solutions I hope it helps 🙌 & I'm curious of your experiences.

    See more
    Amazon ElastiCache
    Amazon ElastiCache
    Amazon Elasticsearch Service
    Amazon Elasticsearch Service
    AWS Elastic Load Balancing (ELB)
    AWS Elastic Load Balancing (ELB)
    Memcached
    Memcached
    Redis
    Redis
    Python
    Python
    AWS Lambda
    AWS Lambda
    Amazon RDS
    Amazon RDS
    Microsoft SQL Server
    Microsoft SQL Server
    MariaDB
    MariaDB
    Amazon RDS for PostgreSQL
    Amazon RDS for PostgreSQL
    Rails
    Rails
    Ruby
    Ruby
    Heroku
    Heroku
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk

    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

    See more
    Julien DeFrance
    Julien DeFrance
    Principal Software Engineer at Tophatter · | 2 upvotes · 14.3K views
    atSmartZipSmartZip
    Amazon SageMaker
    Amazon SageMaker
    Amazon Machine Learning
    Amazon Machine Learning
    AWS Lambda
    AWS Lambda
    Serverless
    Serverless
    #FaaS
    #GCP
    #PaaS

    Which #IaaS / #PaaS to chose? Not all #Cloud providers are created equal. As you start to use one or the other, you'll build around very specific services that don't have their equivalent elsewhere.

    Back in 2014/2015, this decision I made for SmartZip was a no-brainer and #AWS won. AWS has been a leader, and over the years demonstrated their capacity to innovate, and reducing toil. Like no other.

    Year after year, this kept on being confirmed, as they rolled out new (managed) services, got into Serverless with AWS Lambda / FaaS And allowed domains such as #AI / #MachineLearning to be put into the hands of every developers thanks to Amazon Machine Learning or Amazon SageMaker for instance.

    Should you compare with #GCP for instance, it's not quite there yet. Building around these managed services, #AWS allowed me to get my developers on a whole new level. Where they know what's under the hood. Where they know they have these services available and can build around them. Where they care and are responsible for operations and security and deployment of what they've worked on.

    See more
    Aviad Mor
    Aviad Mor
    CTO & Co-Founder at Lumigo · | 5 upvotes · 10.3K views
    atLumigoLumigo
    Serverless
    Serverless
    CircleCI
    CircleCI
    AWS Lambda
    AWS Lambda

    Our backend is serverless based, with many AWS Lambda , with CI/CD, using CircleCI and Serverless. This allows to develop with awesome agility and move fast. Since we update our lambdas daily, we needed a way to make sure we did not run into AWS's max limit of versions per lambda. We use the open source in link below to clear them out and stay clear of the limit.

    See more
    Aliadoc Team
    Aliadoc Team
    at aliadoc.com · | 5 upvotes · 88.6K views
    atAliadocAliadoc
    Bitbucket
    Bitbucket
    Visual Studio Code
    Visual Studio Code
    Serverless
    Serverless
    Google Cloud Storage
    Google Cloud Storage
    Google App Engine
    Google App Engine
    Cloud Functions for Firebase
    Cloud Functions for Firebase
    Firebase
    Firebase
    CloudFlare
    CloudFlare
    Create React App
    Create React App
    React
    React
    #Aliadoc

    In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

    For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

    For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

    We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

    Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

    See more
    Tim Nolet
    Tim Nolet
    Founder, Engineer & Dishwasher at Checkly · | 5 upvotes · 20.8K views
    atChecklyHQChecklyHQ
    Node.js
    Node.js
    Google Cloud Functions
    Google Cloud Functions
    Azure Functions
    Azure Functions
    Amazon CloudWatch
    Amazon CloudWatch
    Serverless
    Serverless
    AWS Lambda
    AWS Lambda

    AWS Lambda Serverless Amazon CloudWatch Azure Functions Google Cloud Functions Node.js

    In the last year or so, I moved all Checkly monitoring workloads to AWS Lambda. Here are some stats:

    • We run three core functions in all AWS regions. They handle API checks, browser checks and setup / teardown scripts. Check our docs to find out what that means.
    • All functions are hooked up to SNS topics but can also be triggered directly through AWS SDK calls.
    • The busiest function is a plumbing function that forwards data to our database. It is invoked anywhere between 7000 and 10.000 times per hour with an average duration of about 179 ms.
    • We run separate dev and test versions of each function in each region.

    Moving all this to AWS Lambda took some work and considerations. The blog post linked below goes into the following topics:

    • Why Lambda is an almost perfect match for SaaS. Especially when you're small.
    • Why I don't use a "big" framework around it.
    • Why distributed background jobs triggered by queues are Lambda's raison d'être.
    • Why monitoring & logging is still an issue.

    https://blog.checklyhq.com/how-i-made-aws-lambda-work-for-my-saas/

    See more
    Praveen Mooli
    Praveen Mooli
    Technical Leader at Taylor and Francis · | 11 upvotes · 164.5K views
    MongoDB Atlas
    MongoDB Atlas
    Amazon S3
    Amazon S3
    Amazon DynamoDB
    Amazon DynamoDB
    Amazon RDS
    Amazon RDS
    Serverless
    Serverless
    Docker
    Docker
    Terraform
    Terraform
    Travis CI
    Travis CI
    GitHub
    GitHub
    RxJS
    RxJS
    Angular 2
    Angular 2
    AWS Lambda
    AWS Lambda
    Amazon SQS
    Amazon SQS
    Amazon SNS
    Amazon SNS
    Amazon Kinesis Firehose
    Amazon Kinesis Firehose
    Amazon Kinesis
    Amazon Kinesis
    Flask
    Flask
    Python
    Python
    ExpressJS
    ExpressJS
    Node.js
    Node.js
    Spring Boot
    Spring Boot
    Java
    Java
    #Data
    #Devops
    #Webapps
    #Eventsourcingframework
    #Microservices
    #Backend

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

    See more
    Interest over time
    Reviews of Microsoft SQL Server and Serverless
    No reviews found
    How developers use Microsoft SQL Server and Serverless
    Avatar of Brillium, Inc.
    Brillium, Inc. uses Microsoft SQL ServerMicrosoft SQL Server

    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.

    Avatar of Andrew Miller
    Andrew Miller uses Microsoft SQL ServerMicrosoft SQL Server

    Defacto, industry standard for backend relational databases. Entity Framework makes designing, migrating & maintaining SQL Server databases a breeze. LocalDB is especially helpful during development.

    Avatar of David Flynn
    David Flynn uses Microsoft SQL ServerMicrosoft SQL Server

    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.

    Avatar of Olo
    Olo uses Microsoft SQL ServerMicrosoft SQL Server

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

    Avatar of betterPT
    betterPT uses ServerlessServerless

    We use AWS Lambda / Serverless as a Facade for out integrations with EMRs.

    Avatar of Arbor Health, LLC
    Arbor Health, LLC uses Microsoft SQL ServerMicrosoft SQL Server

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

    Avatar of JimmyCode
    JimmyCode uses ServerlessServerless

    Oh yeah! We run on lambdas.

    How much does Microsoft SQL Server cost?
    How much does Serverless cost?
    Pricing unavailable
    Pricing unavailable
    News about Serverless
    More news