PySOA is deprecated, and is not a recommended solution. Please use another RPC protocol.
- Services and actions both have simple names, and are called from the client by name. You can call actions individually, or bundle multiple action calls into a "job" to be run serially (either aborting or continuing on error).
- Requests and responses are simply Python dictionaries, and PySOA uses our open source validation framework Conformity in order to verify their schema on the way in and out.
- Message bodies are encoded using MessagePack by default (however, you can define your own serializer), with a few non-standard types encoded using MessagePack extensions, such as dates, times, date-times, and amounts of currency (using our open source currint library).
- Requests have a
context, which is sourced from the original client context (web request, API request, etc.) and automatically chained down into subsequent client calls made inside the service. This is used for contextual request information like correlation IDs, authentication tokens, locales, etc. - We include "SOA Switches" as a first-party implementation of feature flags/toggles. Part of the context, they are bundled along with every request and automatically chained, and are packed as integers to ensure they have minimal overhead.
This intro summarizes some of the key concepts of using PySOA. For more thorough documentation, see the PySOA Documentation.
PySOA is licensed under the Apache License, version 2.0.
PySOA is available in PyPi and can be installing directly via Pip or listed in setup.py, requirements.txt, or Pipfile:
pip install 'pysoa~=1.2'install_requires=[
...
'pysoa~=1.2',
...
]pysoa~=1.2pysoa = {version="~=1.2"}The complete PySOA documentation is available on Read the Docs!