Libraries tagged by Query Bus

gnugat/pomm-search-engine

0 Favers
70 Downloads

A Pomm Foundation implemenation of SearchEngine

Go to Download


streak/streak-bundle

2 Favers
5906 Downloads

Go to Download


phpgears/cqrs-async-queue-interop

1 Favers
14 Downloads

Queue-interop async decorator for CQRS command bus

Go to Download


simplycodedsoftware/integration-messaging-cqrs

1 Favers
977 Downloads

Provides cqrs on top of integration messaging

Go to Download


mmasiukevich/domain-common

0 Favers
1854 Downloads

Service bus domain layer

Go to Download


arnulfosolis/qcharts

1 Favers
62 Downloads

Business tool design to aid the analysis of SQL data in a graphical way to empower users among a team.

Go to Download


busenov/database

0 Favers
4 Downloads

PHP class library for simple, convenient, fast and safe work with MySql database, using PHP mysqli extension and imitation of prepared queries.

Go to Download


pupadevs/laramain

0 Favers
19 Downloads

Install CQRS with DDD folder structure and Command/Query Buses for the specified entity

Go to Download


dinecat/cqrs

0 Favers
65 Downloads

Provide Command, Event and Query buses and functionality.

Go to Download


milhojas/messaging

1 Favers
299 Downloads

A Messaging component for apps, with CommandBus, EventBus and QueryBus

Go to Download


runmybusiness/laravel-simpleassets

4 Favers
348 Downloads

Suffixes assets with a query string to bust the browser cache.

Go to Download


etel/cqrs-contracts

0 Favers
3 Downloads

A set of abstractions related to commands/queries/events message buses and CQRS pattern.

Go to Download


garlic/graphql

3 Favers
2503 Downloads

GraphQL Bundle uses for sending and receiving graphql queries among microservices through Garlic Message Bus.

Go to Download


nodeum-io/nodeum-sdk-php

0 Favers
0 Downloads

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download


cbeyersdorf/easybill

3 Favers
1 Downloads

The first version of the easybill REST API. [CHANGELOG](https://api.easybill.de/rest/v1/CHANGELOG.md) ## Authentication You can choose between two available methods: `Basic Auth` or `Bearer Token`. In each HTTP request, one of the following HTTP headers is required: ``` # Basic Auth Authorization: Basic base64_encode(':') # Bearer Token Authorization: Bearer ``` ## Limitations ### Request Limit * PLUS: 10 requests per minute * BUSINESS: 60 requests per minute If the limit is exceeded, you will receive the HTTP error: `429 Too Many Requests` ### Result Limit All result lists are limited to 100 by default. This limit can be increased by the query parameter `limit` to a maximum of 1000. ## Query filter Many list resources can be filtered. In `/documents` you can filter e.g. by number with `/documents?number=111028654`. If you want to filter multiple numbers, you can either enter them separated by commas `/documents?number=111028654,222006895` or as an array `/documents?number[]=111028654&number[]=222006895`. **Warning**: The maximum size of an HTTP request line in bytes is 4094. If this limit is exceeded, you will receive the HTTP error: `414 Request-URI Too Large` ### Escape commas in query You can escape commans in query `name=Patrick\, Peter` if you submit the header `X-Easybill-Escape: true` in your request. ## Property login_id This is the login of your admin or employee account. ## Date and Date-Time format Please use the timezone `Europe/Berlin`. * **date** = *Y-m-d* = `2016-12-31` * **date-time** = *Y-m-d H:i:s* = `2016-12-31 03:13:37` Date or datetime can be `null` because the attributes have been added later and the entry is older.

Go to Download


<< Previous