Get Advice Icon

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

Kohana
Kohana

39
27
+ 1
15
Rails
Rails

8.7K
5.4K
+ 1
5.3K
Add tool

Kohana vs Rails: What are the differences?

Developers describe Kohana as "An elegant HMVC PHP5 framework". Kohana is an elegant, open source, and object oriented HMVC framework built using PHP5, by a team of volunteers. It aims to be swift, secure, and small. On the other hand, Rails is detailed as "Web development that doesn't hurt". Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Kohana and Rails belong to "Frameworks (Full Stack)" category of the tech stack.

"Open source" is the top reason why over 3 developers like Kohana, while over 822 developers mention "Rapid development" as the leading cause for choosing Rails.

Kohana and Rails are both open source tools. It seems that Rails with 43.6K GitHub stars and 17.5K forks on GitHub has more adoption than Kohana with 1.61K GitHub stars and 464 GitHub forks.

Airbnb, Twitter, and Instacart are some of the popular companies that use Rails, whereas Kohana is used by Huia, Zeel Networks Inc, and Plinga. Rails has a broader approval, being mentioned in 2321 company stacks & 796 developers stacks; compared to Kohana, which is listed in 3 company stacks and 3 developer stacks.

What is Kohana?

Kohana is an elegant, open source, and object oriented HMVC framework built using PHP5, by a team of volunteers. It aims to be swift, secure, and small.

What is Rails?

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.
Get Advice Icon

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

Why do developers choose Kohana?
Why do developers choose Rails?

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

    Be the first to leave a con

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

    What companies use Kohana?
    What companies use Rails?

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

    What tools integrate with Kohana?
    What tools integrate with Rails?

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

    What are some alternatives to Kohana and Rails?
    Laravel
    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.
    CodeIgniter
    CodeIgniter is a proven, agile & open PHP web application framework with a small footprint. It is powering the next generation of web apps.
    Yii
    Yii comes with: MVC, DAO/ActiveRecord, I18N/L10N, caching, authentication and role-based access control, scaffolding, testing, etc. It can reduce your development time significantly.
    Node.js
    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
    ASP.NET
    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
    See all alternatives
    Decisions about Kohana and Rails
    StackShare Editors
    StackShare Editors
    Rails
    Rails
    Node.js
    Node.js
    Python
    Python
    React
    React
    Java
    Java
    Ruby
    Ruby
    Go
    Go
    Swift
    Swift
    Objective-C
    Objective-C
    jQuery
    jQuery

    By mid-2015, around the time of the Series E, the Digital department at WeWork had grown to more than 40 people to support the company’s growing product needs.

    By then, they’d migrated the main website off of WordPress to Ruby on Rails, and a combination React, Angular, and jQuery, though there were efforts to move entirely to React for the front-end.

    The backend was structured around a microservices architecture built partially in Node.js, along with a combination of Ruby, Python, Bash, and Go. Swift/Objective-C and Java powered the mobile apps.

    These technologies power the listings on the website, as well as various internal tools, like community manager dashboards as well as RFID hardware for access management.

    See more
    Spenser Coke
    Spenser Coke
    Product Engineer at Loanlink.de · | 8 upvotes · 150.3K views
    atLoanlink GmbhLoanlink Gmbh
    Rails
    Rails
    AngularJS
    AngularJS
    .NET
    .NET
    Node.js
    Node.js
    React
    React
    GitHub
    GitHub
    Trello
    Trello
    Zapier
    Zapier
    Mailchimp
    Mailchimp
    Google Drive
    Google Drive
    Vue.js
    Vue.js
    HTML5
    HTML5

    When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

    The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

    We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

    We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

    See more
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare · | 19 upvotes · 242.3K views
    atStackShareStackShare
    React
    React
    Glamorous
    Glamorous
    Apollo
    Apollo
    Node.js
    Node.js
    Rails
    Rails
    Heroku
    Heroku
    GitHub
    GitHub
    Amazon S3
    Amazon S3
    Amazon CloudFront
    Amazon CloudFront
    Webpack
    Webpack
    CircleCI
    CircleCI
    Redis
    Redis
    #StackDecisionsLaunch
    #SSR
    #Microservices
    #FrontEndRepoSplit

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more
    Julien DeFrance
    Julien DeFrance
    Principal Software Engineer at Tophatter · | 16 upvotes · 497.8K views
    atSmartZipSmartZip
    Rails
    Rails
    Rails API
    Rails API
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Capistrano
    Capistrano
    Docker
    Docker
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS