When comparing Pyramid vs Hapi, the Slant community recommends Pyramid for most people. In the question“What are the best backend web frameworks?” Pyramid is ranked 15th while Hapi is ranked 27th. The most important reason people chose Pyramid is:
Pyramid can be used for creating small applications quickly and easily, but it also powers up large enterprise-scale applications such as Dropbox.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very flexible
Pyramid can be used for creating small applications quickly and easily, but it also powers up large enterprise-scale applications such as Dropbox.
Pro Persistence agnostic
Either NoSQL and SQL (including SQLAlchemy plugin).
Pro Comes with security included
Includes authorization and authentication with multiple backends.
Pro Backed by a major corporation
Hapi was developed and is still being used by Walmart. Being backed by such a major company means that it will not lose support any time soon and most importantly it's being developed by professionals and that you will always get support for it.
Pro Consistency across applications
Hapi's philosophy is that configuration is more important than code. This is especially useful for very large teams because it helps developers maintain consistency and reusability throughout their code.
Cons
Con The great number of options it offers can become intimidating
One of Pyramid's greatest drawbacks is that it requires a lot of set up in the beginning of a project. This can feel overwhelming and can keep people away from using it.
Con Requires too much boilerplate
Hapi seems to be made with large applications in mind. The sheer amount of boilerplate code it requires is simply not practical for a small web app. This also means that there are few examples of Hapi applications around for beginners to learn from.
