Buffalo vs Phoenix Framework: What are the differences?
Developers describe Buffalo as "MVC Web Framework for Go". Buffalo is Go web framework. Yeah, I hate the word "framework" too! Buffalo is different though. Buffalo doesn't want to re-invent wheels like routing and templating. Buffalo is glue that wraps all of the best packages available and makes them all play nicely together. On the other hand, Phoenix Framework is detailed as "Most web frameworks make you choose between speed and a productive environment. Phoenix gives you both". Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.
Buffalo and Phoenix Framework can be primarily classified as "Frameworks (Full Stack)" tools.
"Go" is the primary reason why developers consider Buffalo over the competitors, whereas "High performance" was stated as the key factor in picking Phoenix Framework.
Buffalo and Phoenix Framework are both open source tools. Phoenix Framework with 13.9K GitHub stars and 1.75K forks on GitHub appears to be more popular than Buffalo with 4.56K GitHub stars and 358 GitHub forks.
What is Buffalo?
What is Phoenix Framework?
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 Buffalo?
Sign up to get full access to all the companiesMake informed product decisions
The Framework is new but has what it takes to take your apps to the next level, right now rails 5 is beta with ActionCable to make real time but I must say ruby isn't the right tool for doing real time but Elixir is really fast and has great concurrency and other erlang features.