PHPackages                             vaizard/glued-integrations - 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. [Utility & Helpers](/categories/utility)
4. /
5. vaizard/glued-integrations

ActiveLibrary[Utility & Helpers](/categories/utility)

vaizard/glued-integrations
==========================

Integrations manager.

07PHPCI passing

Since Sep 28Pushed 7mo ago2 watchersCompare

[ Source](https://github.com/vaizard/glued-if)[ Packagist](https://packagist.org/packages/vaizard/glued-integrations)[ RSS](/packages/vaizard-glued-integrations/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

glued-if
========

[](#glued-if)

IF is Glued's integration framework, message queue and scheduler.

**Implementation Overview:**

- `if microservice` is a set of methods implemented as a separate git project `glued-if-service_name` to interact with a foreign service
- `deployment` is a configuration and authorization context of an `if microservice` defined by a row/object of the `if__deployments` table
- `action` is a `deployment:microservice.method` map stored as a row in the `if__actions` table. actions are triggered by calling an API endpoint (webhook) or by the IF scheduler.
- `action state` makes a stateful history using `if__actions_states`
- `scheduler`is implemented as a set of cron-like rules with some extra sugarcoating (i.e. ttl) stored in the `if__scheduler` table and an associated producer that will periodically fill up the `message queue` with work and runner daemons that will subscribe to this queue and launch workers (perform the webhook api calls)
- `message queue` is implemented as the `if__mq_queue` table configuring message queues clients can subscribe to.
- `messages` are implemented as the `if__mq_messages` table which maps a queue to a message payload and message headers (i.e. ttl, requesting, replies, etc.)
- `notifications` are implemented using the pg\_notify capabilities and can be further extended with rabbitmq.
- `logging` is by default implemented using the monolog library.

Integrations
------------

[](#integrations)

IF orchestrates `if microservices` which facilitate integration with anything thats out there.

- Each `if microservice` implements working with a remote/external `service`.
- Each `if microservice` has associated `deployments` (a set of attributes describing usage of an `if microservice`), i.e:
    - deployment metadata (i.e. name, description, etc.)
    - deployment connection (i.e. remote host, auth tokens, rate limits, etc.)
    - deployment RBAC rules\* (i.e. who can use the if microservice)
- Methods implemented by an `if microservice` (i.e. CRUD operations against an external service) are associated to deployments as `actions` (actions are if microservice methods runnable in the context of a deployment configuration). actions
    - can run on-demand (i.e. provide a caching data transforming interface to external services such as glued-if-ares\_gov\_cz)
    - can run according to a schedule (by the scheduler)
    - can interact with each other (via the message queue)

\*) RBAC is provided by glued-core's authorization proxy

Scheduler
---------

[](#scheduler)

tbd

Message queue
-------------

[](#message-queue)

The message queue is loosely inspired by RabbitMQ to enable an easy transition between the builtin PostgreSQL based queue and Rabbit. The indented MQ usage is

- to distribute scheduled tasks to workers,
- to facilitate communication between the loosely coupled microservices
- to ensure internal notifications to users are send and individually delivered (with or without user confirmation)

IFMQ, when acting as a RabbitMQ-like message brooker, implements the concepts of

- `producers` / code responsible for generating messages - php implementation is part of glued-lib
- `queues` / 'message destinations' implemented via the `if__queues` table
- `consumers` / clients subscribed to queues
- `exchanges` / code responsible for delivering messages to queues - direct (unicast), fanout (multicast), header (rule based multicast)

Messges can be

###  Health Score

17

—

LowBetter than 6% of packages

Maintenance44

Moderate activity, may be stable

Popularity4

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity13

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/a1aa2bc3fba9509b58c205e11ef74ccf62f0fc6c5a798c4f89ff347d5cf5faa4?d=identicon)[killua-eu](/maintainers/killua-eu)

---

Top Contributors

[![killua-eu](https://avatars.githubusercontent.com/u/410734?v=4)](https://github.com/killua-eu "killua-eu (38 commits)")

### Embed Badge

![Health badge](/badges/vaizard-glued-integrations/health.svg)

```
[![Health](https://phpackages.com/badges/vaizard-glued-integrations/health.svg)](https://phpackages.com/packages/vaizard-glued-integrations)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)