Fat-Free vs Hoodie: What are the differences?
Fat-Free and Hoodie belong to "Frameworks (Full Stack)" category of the tech stack.
"Open source" is the primary reason why developers consider Fat-Free over the competitors, whereas "JSON" was stated as the key factor in picking Hoodie.
Fat-Free and Hoodie are both open source tools. It seems that Hoodie with 3.51K GitHub stars and 314 forks on GitHub has more adoption than Fat-Free with 2.3K GitHub stars and 443 GitHub forks.
What is Fat-Free?
What is Hoodie?
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 Fat-Free?
What are the cons of using Hoodie?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Hoodie?
This compact framework provided me flexibility. I can implement my own design pattern either MVC or something else. What caught my attention the most was its built-in ORM that can accommodate SQL and NoSql database. That means I can have my MongoSql and SQL queries written by those compatible raw sql statements but still creates ORM models the same way as nosql. Consider for example: $user=new DB\SQL\Mapper($db,'users');// for sql db $user=new DB\Mongo\Mapper($db,'users'); // for mongo db then $user = $user->load('id = 1');
Thanks to its high modularity, I can add more fat to my liking. There's also Cortex ORM f3 extension which handles join tables. Also, handles sessions, routing, and config with ease and let you organize them neatly. That's just a few of the handful features without much weight and with fast performance. One drawback is smaller community, but didn't disappoint me.