PHPackages                             bfitech/zapcore - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. bfitech/zapcore

ActiveLibrary[Framework](/categories/framework)

bfitech/zapcore
===============

A very simple router and other utils.

2.3.1(5y ago)02.3k↓85.7%2MITPHPPHP >=7.0 <7.5CI failing

Since Mar 7Pushed 5y ago1 watchersCompare

[ Source](https://github.com/bfitech/zapcore)[ Packagist](https://packagist.org/packages/bfitech/zapcore)[ RSS](/packages/bfitech-zapcore/feed)WikiDiscussions master Synced yesterday

READMEChangelog (10)Dependencies (1)Versions (22)Used By (2)

zapcore
=======

[](#zapcore)

A very simple PHP router and other utilities.

[![Latest Stable Version](https://camo.githubusercontent.com/169aca4619305e28d24c9d56af0aa283f464d7d09cfb709539323222d47278f1/68747470733a2f2f706f7365722e707567782e6f72672f626669746563682f7a6170636f72652f762f737461626c65)](https://packagist.org/packages/bfitech/zapcore)[![Latest Unstable Version](https://camo.githubusercontent.com/9e65464ff18a456062a9095205fe562e7a6fa47167384311234263ef0814a008/68747470733a2f2f706f7365722e707567782e6f72672f626669746563682f7a6170636f72652f762f756e737461626c65)](https://packagist.org/packages/bfitech/zapcore)[![Build Status](https://camo.githubusercontent.com/419f5869118c2918cc6b3c685c98e39c879745ab5d32db087d6633480ad30045/68747470733a2f2f7472617669732d63692e6f72672f626669746563682f7a6170636f72652e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/bfitech/zapcore)[![Code Coverage](https://camo.githubusercontent.com/42a7d7df247d434f077b74d67454660ed71d0bbcfc1d4ad78bd41d62743daa19/68747470733a2f2f636f6465636f762e696f2f67682f626669746563682f7a6170636f72652f6272616e63682f6d61737465722f67726170682f62616467652e737667)](https://codecov.io/gh/bfitech/zapcore)[![GitHub license](https://camo.githubusercontent.com/7013272bd27ece47364536a221edb554cd69683b68a46fc0ee96881174c4214c/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6c6963656e73652d4d49542d626c75652e737667)](https://raw.githubusercontent.com/bfitech/zapcore/master/LICENSE)

---

0. Reason
---------

[](#0-reason)

[![but why?](https://camo.githubusercontent.com/f8b37d41932ef237dc3ab4106c824fdf3f78060f9b900b915e61f03bd2531670/687474703a2f2f732e62616e64756e6766652e6e65742f692f6275742d7768792e676966)](https://en.wikipedia.org/wiki/Category:PHP_frameworks)

Yeah, why another framework?

These are a few (hopefully good enough) reasons:

1. web service-oriented

    `zapcore` and in general `zap*` packages are geared towards HTTP RESTful APIs with very little emphasis on traditional HTML document serving. If you are building the back end of a single page web application, you'll feel immediately at home.
2. performance

    `zapcore` performance is guaranteed to be much faster than any popular batteries-included monolithic frameworks, and is at least on par with other microframeworks. **TODO**: Benchmark result.
3. idiosyncracy

    This is just a fancy way of saying, "Because that's the way we like it."

1. Installation
---------------

[](#1-installation)

Install it from Packagist:

```
$ composer -vvv require bfitech/zapcore
```

2. Hello, World
---------------

[](#2-hello-world)

Here's a bare-minimum `index.php` file:

```