When comparing Firebase vs Hapi, the Slant community recommends Hapi for most people. In the question“What are the best backend web frameworks?” Hapi is ranked 27th while Firebase is ranked 31st. The most important reason people chose Hapi is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro One command deploys and rollbacks
The content is deployed immediately through the Firebase CLI. Once it's uploaded, the content is served immediately. If you have made a mistake, you don't need to re-upload a new version, through the Admin dashboard you can easily rollback to a previous version.
Pro Assured future support
Google acquired Firebase in Oct. 2014. This gives Firebase a degree of trustworthiness in their service and future support since they are backed by such a large company.
Pro Well documented
The documentation and quick start guides are informative and easy to learn.
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 Hosted
Firebase locks you in to Google's service; you can't run it on your own servers.
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.