Download the PHP package zemd/micro without Composer
On this page you can find all versions of the php package zemd/micro. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package micro
Short Description Microservices router and handler component
License MIT
Homepage https://reactive.world
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package micro
Micro
Lightweight domain driven rest api architecture
Installation
Usage
This is lightweight approach to manage rest api calls translate them into pretty domain objects and route to handler. Such approach lets to avoid messy boilerplate code during handling api requests.
So you have some specific code that handles "requests" and returns some data. It is independent code that can be placed
in rabbitMQ consumer or elsewhere on the net. Let's call it handler and define that each such handler must implement
simple method handle.
As such handler doesn't know about http requests it receives in it's parameter some command object. It nothing else
than serializable object that can be transferred via any transport mechanism without data loss.
To make it accessible to some router that will look up for handlers there need to be passed some meta information about your endpoint and it's destination. In systems where endpoint can be physically be placed in different servers, you can share meta information in your target services, and return collected info in instance of HandlerMetaInterface interface.
Do not forget to tag your meta provider in services.yml
Now we have information and handler, we can continue with building Command. Commands are building automatically with CommandBuilder, so you should only define it with passing additional information using annotations and make command available to builder and handler.
@RequestParam - says that prop's value is defined in request under desired alias, can define custom pattern to validate,
and set if this parameter is required to build command.
@Type - says that prop is defined as object type
You can defined your own annotations if you wish.
As you can see this class is plain domain without any complexity.
So now we have handler, meta and command and we already can launch our command pipe. We can define one controller action that will be responsible for handling all api calls.
Advanced usage
For now we built simple handler that is placed on the same machine. But what if we want to make it distributed and asynchronous.
You can achieve this by implementing CommandDispatcherInterface. By default CommandDispatcher supports rabbitmq via
old_sound_rabbit_mq package. This requires to implement you Consumer, inside of it you should transfer command to
handler and return response using rabbitmq xml/rpc mechanism. In such architecture you can implement simple map/reduce handler
or run several heavy computations asynchronously inside handler and then return result back.
License
Micro is released under the MIT license.
Donate
