Get Advice Icon

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

CouchDB
CouchDB

285
242
+ 1
136
Serverless
Serverless

451
357
+ 1
17
Add tool

CouchDB vs Serverless: What are the differences?

CouchDB: HTTP + JSON document database with Map Reduce views and peer-based replication. Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript; Serverless: 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.

CouchDB can be classified as a tool in the "Databases" category, while Serverless is grouped under "Serverless / Task Processing".

"JSON" is the top reason why over 42 developers like CouchDB, while over 10 developers mention "API integration " as the leading cause for choosing Serverless.

CouchDB and Serverless are both open source tools. Serverless with 30.9K GitHub stars and 3.43K forks on GitHub appears to be more popular than CouchDB with 4.24K GitHub stars and 835 GitHub forks.

According to the StackShare community, Serverless has a broader approval, being mentioned in 117 company stacks & 44 developers stacks; compared to CouchDB, which is listed in 61 company stacks and 32 developer stacks.

What is CouchDB?

Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript.

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 CouchDB?
Why do developers choose Serverless?

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

    Be the first to leave a con
      Be the first to leave a con
      What companies use CouchDB?
      What companies use Serverless?

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

      What tools integrate with CouchDB?
      What tools integrate with Serverless?

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

      What are some alternatives to CouchDB and Serverless?
      MongoDB
      MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
      Couchbase
      Developed as an alternative to traditionally inflexible SQL databases, the Couchbase NoSQL database is built on an open source foundation and architected to help developers solve real-world problems and meet high scalability demands.
      Cloudant
      Cloudant’s distributed database as a service (DBaaS) allows developers of fast-growing web and mobile apps to focus on building and improving their products, instead of worrying about scaling and managing databases on their own.
      MariaDB
      Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.
      RethinkDB
      RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.
      See all alternatives
      Decisions about CouchDB and Serverless
      Josh Dzielak
      Josh Dzielak
      Developer Advocate at DeveloperMode · | 5 upvotes · 15.1K views
      Cloudant
      Cloudant
      CouchDB
      CouchDB
      Pouchdb
      Pouchdb
      Firebase
      Firebase

      As a side project, I was building a note taking app that needed to synchronize between the client and the server so that it would work offline. At first I used Firebase to store the data on the server and wrote my own code to cache Firebase data in local storage and synchronize it. This was brittle and not performant. I figured that someone else must have solved this in a better way so I went looking for a better solution.

      I needed a tool where I could write the data once and it would write to client and server, and when clients came back on line they would automatically catch the client up. I also needed conflict resolution. I was thrilled to discover Pouchdb and its server-side counterpart CouchDB. Together, they met nearly all of my requirements and were very easy to implement - I was able to remove a ton of custom code and have found the synchronization to be very robust. Pouchdb 7 has improved mobile support too, so I can run the app on iOS or Android browsers.

      My Couchdb instance is actually a Cloudant instance running on IBM Bluemix. For my fairly low level of API usage, it's been totally free, and it has a decent GUI for managing users and replications.

      See more
      Nitzan Shapira
      Nitzan Shapira
      at Epsagon · | 11 upvotes · 93.4K 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 · 50.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
      Jonathan Pugh
      Jonathan Pugh
      Software Engineer / Project Manager / Technical Architect · | 17 upvotes · 127.8K views
      Pouchdb
      Pouchdb
      CouchDB
      CouchDB
      Font Awesome
      Font Awesome
      CSS 3
      CSS 3
      Apache Cordova
      Apache Cordova
      PhoneGap
      PhoneGap
      HTML5
      HTML5
      Ruby
      Ruby
      Babel
      Babel
      Webpack
      Webpack
      Visual Studio Code
      Visual Studio Code
      Figma
      Figma
      TypeScript
      TypeScript
      JavaScript
      JavaScript
      Framework7
      Framework7
      #Css
      #CSS3
      #SCSS
      #Sass
      #Less
      #Electron
      #HandleBars
      #Template7
      #Sketch
      #GraphQL
      #HTML5
      #GraphCool

      I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

      For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

      Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

      I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

      I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

      I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

      I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

      For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

      For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

      For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

      I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

      So that's my latest mobile stack. What tools do you use? Have you tried these ones?

      See more
      Julien DeFrance
      Julien DeFrance
      Full Stack Engineering Manager at ValiMail · | 2 upvotes · 12.1K 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 · 8.8K 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 · 59.7K 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 · 14.6K 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 · 98.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 CouchDB and Serverless
      No reviews found
      How developers use CouchDB and Serverless
      Avatar of King's Digital Lab
      King's Digital Lab uses CouchDBCouchDB

      Document (JSON) DB.

      • - queries must be pre-defined as views (not as flexible as query formulation on the fly)
      • - community and ecosystem not as large as mongodb
      • + PouchDB is an excellent JS library to interact with CouchDB or even work in offline-then-sync moce
      Avatar of Smileupps
      Smileupps uses CouchDBCouchDB

      By being built on, of, in and around CouchDB, Smileupps offers to its customers secure and reliable CouchDB hosting and a CouchDB-based app store to build and sell serious business-enabled web applications

      Avatar of betterPT
      betterPT uses ServerlessServerless

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

      Avatar of Giant Swarm
      Giant Swarm uses CouchDBCouchDB

      We use CouchDB in an internal analysis tool for usage data.

      Avatar of Mathias Vonende
      Mathias Vonende uses CouchDBCouchDB

      Storage for unstructured, linked and timeseries data.

      Avatar of Aaron Buchanan
      Aaron Buchanan uses CouchDBCouchDB

      json store + geo + _changes

      Avatar of JimmyCode
      JimmyCode uses ServerlessServerless

      Oh yeah! We run on lambdas.

      How much does CouchDB cost?
      How much does Serverless cost?
      Pricing unavailable
      Pricing unavailable
      News about CouchDB
      More news
      News about Serverless
      More news