Libraries tagged by observer pattern

A library of common design patterns for building stateful server applications.

Go to Download

Installer-style Laravel package that scaffolds a clean, scalable, OOAD-based, OWASP-hardened architecture — layered services, repositories and policies behind a versioned JSON API, a server-rendered Blade UI, or both — into any Laravel 10, 11, 12 or 13 application.

Go to Download

A library and server-side implementation supporting a limited number of the COAR Notify pattern objects. Server-side implementation assumes MySQL. If you are looking for a full, generic implementation of the COAR Notify protocol see https://packagist.org/packages/cottagelabs/coarnotify

Go to Download

簡易的 MySQL database 伺服器存取類別，使用 POD 及 singleton pattern 實作，支援 Master-Slave 架構。 / Simple MySQL database server access class use PDO and singleton pattern, support Master-Slave database cluster.

Go to Download

PHP/Laravel SDK for OneHux Accounts SSO. Two patterns: the OAuth client/BFF (Authorization Code + PKCE, real hosted login page, RP-initiated logout) and a resource server verifying Bearer tokens against the platform's published JWKS for a PHP API sitting behind a separate frontend BFF.

Go to Download

A collection of Laravel API starter kits using the repository pattern. Very flexible and useful when developing medium to large scale applications.

Go to Download

Zend Server Nagios pugin

Go to Download

SpiderForm - Modern PHP Form Builder with Chain Pattern. Weaving perfect forms for Symfony & Laravel

Go to Download

Modern PHP Form Generator with Chain Pattern - Supports Symfony, Laravel, Twig, and Smarty

Go to Download

A Framework for the Dual Server Web Design Pattern

Go to Download

Singleton pattern to connect database Mysql, PostgreSQL, Oracle, SQL Server, and others.

Go to Download

Server-side response caching for Flarum's API. Configure regex-pattern rules with per-rule TTLs to short-circuit expensive endpoints (top-poster widgets, statistics aggregations, etc.) before they touch the database.

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download