Kore vs Puma: What are the differences?
What is Kore? A fast web server for writing web apps in C. Kore is an easy to use web application framework for writing scalable web APIs in C. Its main goals are security, scalability and allowing rapid development and deployment of such APIs. Because of this Kore is an ideal candidate for building robust, scalable and secure web things.
What is Puma? A Modern, Concurrent Web Server for Ruby. Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.
Kore and Puma belong to "Web Servers" category of the tech stack.
Kore and Puma are both open source tools. Puma with 5.78K GitHub stars and 987 forks on GitHub appears to be more popular than Kore with 3.09K GitHub stars and 282 GitHub forks.
What is Kore?
What is Puma?
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 Kore?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kore?
What tools integrate with Puma?
We switched from Unicorn (process model) to Puma (threaded model) to decrease the memory footprint of our Rails production web server. Memory indeed dropped from 6GB to only 1GB!
We just had to decrease our worker count and increase our thread count instead. Performance (response time and throughput) remained the same, if not slightly better. We had no thread-safety errors, which was good.
Free bonus points are:
- Requests are blazing fast on our dev and staging environments!
- Puma has first-class support for WebSockets, so we know for sure that Rails ActionCable or GraphQL subscriptions will work great.
- Being on Puma makes us even more "default Rails"-compliant since it is the default Rails web server these days.