kashifrazzaqui/vyked

A python asyncio driven service oriented architecture framework

vyked's Issues

registry should be able to dump the register in json

• one goal is to make a tool that can print a dependency graph of the services

Pot which is a top like tool for vyked services

• Pot which is a top like tool for vyked services

add websocket support

modify service instance versioning strategy at registry

registry should provide an instance of the exact same version if available, else provide the next highest non breaking version

• should not broadcast new version availability as that will cause a denial of service because all clients will upgrade immediately, let the changes propagate naturally

remember to relax packet matching to comply with this logic at service-host and service-client

All service/app name comparisons should be case insensitive

Provide asyncio debug mode activation method/property in vyked

Don't use recursion in pinger

Service should close cleanly when receiving SIGKILL

provide support for weights in registry load balancing

both random and routed load should support weighted loads

Ping Pong between registry client and registry

development server mode

auto restart service upon code changes.

use UDP for metrics, external pings

Add examples

Hide/encapsulate aiohttp for http services

by providing vyked request and response objects

Add docs and improve readme

• Sphinx setup #29
• automate inclusion of docstrings.
• dev environment setup instructions

add default endpoints for service checkup and stats in both HTTP and TCP

add support for REST services

• allow marking entities as resources
• enforce rest urls by auto-generating

[refactoring] move configuration parameters like host / port to another file.

constants shouldn't be hidden inside __main__

registry should have a command to invalidate some or all mapping at a registry client

setup sphinx

Registry should inform a service if all the instances of a service it depends on are down

using bdist_wheel from setuptools instead of distutils for distribution.

distutils is outdated and according to readthedocs/readthedocs.org#1029 (comment) the problem at readthedocs (https://readthedocs.org/builds/vyked/3098727/) is happening because of it.

@nerandell
If it works with bdist_wheel, I shall change the distribution method.

make available implementations of boiler plate services

• identify boilerplate services (eg timer service)
• make source code available as components in vyked (like registry)

setup centralized logging infra

ELK or loggly or alternative

auto generate postman collections

write service mocks to be used for testing by service authors

Persistent registry

Use postgres as store

support api deprecation

when calling a deprecated api, the client should receive a warning

redis host and port should be configurable.

Registry assumes it would find the `redis-server running on the same machine as itself which is fine for the development box but not for staging / production.
Lets make it configurable via command line options / config files / environment variables.

@kashifrazzaqui @nerandell
views?

Config files for services

log time taken by each api call

libpq-dev as system requirement

pip install vyked expects libpq-dev i.e postgres development library to be installed on the system.
needs to be specified in the readme at least.

make '0.0.0.0' the default value for ip address in service __init__

create a cookiecutter template

• plain: without postgres stuff and only HTTP
• standard (default): with postgres boilerplate and HTTP and TCP

Clear up logs

• rotating logs
• log levels to shrink the volume.

setup pytest and travis ci

Refactoring

Add tests

• setup pytest #30
• write mocks
• write tests

Highly available registry

Add a global lock manager

retrial of bus packets on failure

Use metaclasses to reduce boilerplate service code

requirements.txt for python dependencies.

write graphite plugin

add new subscription strategies

@subscribe allows ALL instances to receive the publication and it does not offer reliability guarantees

@xsubscribe allows one instance to reliably receive a publication. It has two strategies

• RANDOM (only one random instance)
• LEADER (one fixed leader)

and is implemented by local queueing at the publisher which is only cleared on ack by subscriber

@xsubscribe(strategy=RANDOM)
def some_api():
    pass

add trace_id to all packets

this must happen automatically

Make a transaction manager to support two phase commits

• A component to support transaction management
• support in the protocol for transaction based apis

Add ssl support for TCP

improve error messages

• some way to detect if tcp client is connecting to http service and report appropriate error.

Distinguish between routing bus and control bus