Fat-Free vs GraPHP: What are the differences?
What is GraPHP? *A PHP graph DB web framework *. The goal of this project is to build a lightweight web framework with a graph DB abstraction. It should be very easy to create the graph schema with no knowledge of of how the data is stored. Also, the schema should be incredibly flexible so you should never need migrations when adding new models (nodes), connections (edges), or data that lives in nodes.
Fat-Free and GraPHP can be categorized as "Frameworks (Full Stack)" tools.
Fat-Free and GraPHP are both open source tools. Fat-Free with 2.3K GitHub stars and 443 forks on GitHub appears to be more popular than GraPHP with 135 GitHub stars and 5 GitHub forks.
What is Fat-Free?
What is GraPHP?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose GraPHP?
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 GraPHP?
What companies use GraPHP?
Sign up to get full access to all the companiesMake informed product decisions
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.