# ZendService Documentation

**URL:** <https://discourse.laminas.dev/t/zendservice-documentation/800>\
**Category:** Components & MVC\
**Created:** [October 22, 2018, 11:33am UTC](https://discourse.laminas.dev/t/zendservice-documentation/800 "2018-10-22T11:33:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevinsmith](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@kevinsmith](https://discourse.laminas.dev/u/kevinsmith)\
**Post date:** [October 22, 2018, 11:33am UTC](https://discourse.laminas.dev/t/zendservice-documentation/800/1 "2018-10-22T11:33:26Z")

</div>

Why are the ‘ZendService’ components e.g. ZendService\ReCaptcha, ZendService\Amazon, ZendsService\Rackspace etc. not listed in the current ZF Documentation?

They only seem to be in the ZF2 docs.

---

<div class="post-metadata">

**Author:** ![ocramius](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/ocramius/32/23_2.png) [@ocramius](https://discourse.laminas.dev/u/ocramius)\
**Post date:** [October 22, 2018, 11:45am UTC](https://discourse.laminas.dev/t/zendservice-documentation/800/2 "2018-10-22T11:45:26Z")

</div>

These have been long deprecated, and besides rare exceptions, are not actively maintained.

---

<div class="post-metadata">

**Author:** ![matthew](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/matthew/32/14_2.png) [@matthew](https://discourse.laminas.dev/u/matthew)\
**Post date:** [October 22, 2018, 2:14pm UTC](https://discourse.laminas.dev/t/zendservice-documentation/800/3 "2018-10-22T14:14:04Z")

</div>

A little history:

Most of these originated in ZF1. One of the problems we had was that these often needed to evolve faster than the framework, however, as the APIs they each targeted often evolved quickly. As such, we chose to separate them into discrete packages. (ZF2 was still distributed primarily as a monolith until version 2.5.)

One thing that happened, however, is that most of these API providers ended up bringing their clients in-house, which meant our effort was redundant. As such, the majority of these are de facto abandoned.

---

<div class="post-metadata">

**Author:** ![kevinsmith](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@kevinsmith](https://discourse.laminas.dev/u/kevinsmith)\
**Post date:** [October 22, 2018, 3:11pm UTC](https://discourse.laminas.dev/t/zendservice-documentation/800/4 "2018-10-22T15:11:39Z")

</div>

OK. Thanks for explaining.

---

<div class="post-metadata">

**Author:** ![Greg\_Bell](https://avatars.discourse-cdn.com/v4/letter/g/bcef8e/32.png) [@Greg\_Bell](https://discourse.laminas.dev/u/Greg_Bell)\
**Post date:** [October 28, 2018, 6:50am UTC](https://discourse.laminas.dev/t/zendservice-documentation/800/5 "2018-10-28T06:50:24Z")

</div>

> [@matthew](#):
>
> ended up bringing their clients in-house

Does this mean that they created their own PHP clients? Like [GitHub - rackspace/php-opencloud: The PHP SDK for OpenStack clouds](https://github.com/rackspace/php-opencloud/)

---

<div class="post-metadata">

**Author:** ![matthew](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.laminas.dev/matthew/32/14_2.png) [@matthew](https://discourse.laminas.dev/u/matthew)\
**Post date:** [October 29, 2018, 1:38pm UTC](https://discourse.laminas.dev/t/zendservice-documentation/800/6 "2018-10-29T13:38:42Z")

</div>

Yes, exactly. AWS, of course, has extensive API clients, as do services such as Azure, Rackspace, and others for which we provided early clients. We definitely recommend using those, as they will always be updated faster than what we can provide.