xakiy / muria Goto Github PK

When using persistent storage to store revoked jwt token, we need to clean it up regularly to free up some spaces. Thus we need to spawn specific task for that.

Since this is still early requirement we could use cron like worker to fire up some scripts. Or using some light thread via gevent thread or something.

Based on jsonschema-validate-10x-faster-in-python I think it worth comparing between them.

Besides that, jsonschema's schemas is just plain text that more coherent with plain json compared with marshmallow schemas.

Add auth middleware that handle JWT validation

For some cases client may send too many queries in a given time, this may lead to unnecessary load for the server. So to prevent this we need to limit client access for a given time.

When adding or fixing some resources sometimes we make schema changes and this changes are cumbersome to do it manually, so we need a migration tool to ease the work.
Link of pony migration tool, not released yet!

Consider removing marshmallow mixin from pony entities, and instead use pony own argument selector e.g. to_dict(exclude={'attr1', 'attr2']) or to_dict(only=['attr3', 'attr4']).

Currently we sanitize user input using marshmallow schema via mixin to pony entity. It need not be actually, because we can incorporate simple schema inside pony model. Thus making entity definition also contains json schema and validate user input by utilizing built-in before_insert method.