Python development services
Python services for operations teams: rules people edit themselves, processes spread over many machines, live figures and alerts that carry them.
- Python
- Redis
- Telegram
Python development at quadevs means the services a small team runs every day: a language for the rules it changes, checks that stop a bad change before release, real-time feeds and paging. Our trading operations platform is written this way, and one person operates it.
Python work we take on
-
Rule and strategy DSLs
A small language for the rules your team edits, read and checked before anything runs.
-
Validation at admission
Each new parameter set runs through a test suite in CI on its way to production.
-
Real-time feeds
Live figures pushed to the screen over WebSocket, with working state kept in Redis.
-
Processes on many servers
One control point for bots and workers that run on dozens of machines.
-
On-call alerts
Telegram pages that bring the figures a person needs to decide.
-
Daily deploys
A CI pipeline that releases every day once its test gate passes.
Python in production
-
Trading operations terminalDozens of trading bots on dozens of servers answer to one Python platform, and a single operator changes their strategies with no engineer in the loop.
How a Python project starts
-
The running system
Tell us what runs today, on how many servers, and which change costs the most effort.
-
Rules and checks
We write down the rules your team edits and the tests a release has to pass.
-
First service
One part moves to the new service with its test suite while the old setup stays in place.
And much more. Ask about your project
Common questions
Can you take over an existing Python codebase?
Python or .NET for a new service?
What does your Python system run today?
Name the servers, the jobs on them and the change your team waits on.