GraPHP vs webapp2: What are the differences?
Developers describe GraPHP as "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. On the other hand, *webapp2** is detailed as "Lightweight Python web framework compatible with Google App Engine’s webapp". webapp2 is a simple. it follows the simplicity of webapp, but improves it in some ways: it adds better URI routing and exception handling, a full featured response object and a more flexible dispatching mechanism.
GraPHP and webapp2 can be primarily classified as "Frameworks (Full Stack)" tools.
Some of the features offered by GraPHP are:
- Full MVC. Zero boilerplate controllers, models, and views.
- Models are your schema. Defining data is up to you (but not required).
- No migrations. Team members can add new models independently without conflicts
On the other hand, webapp2 provides the following key features:
- Compatible with webapp
- Compatible with latest WebOb
- Full-featured response object
GraPHP is an open source tool with 135 GitHub stars and 5 GitHub forks. Here's a link to GraPHP's open source repository on GitHub.