imbolc

4 ms·

1. 1.▲
   by imbolc 2y ago

   - FSM-based - each task is a granular state machine - Resumable - on error, after you fix the step logic or the external world, the task is able to pick up where it stopped - Postgres - a single table is enough to handle task scheduling, st
2. 2.▲
   Rust FSM-based Resumable Postgres tasks(github.com)

   5 points by imbolc 2y ago|1 comments
3. 3.▲
   Implementing a simple derive macro in Rust(github.com)

   1 points by imbolc 5y ago|0 comments
4. 4.▲
   Django-raw-API is async-capable now(github.com)

   1 points by imbolc 6y ago|0 comments
5. 5.▲
   by imbolc 6y ago

   Even bare ASGI app running on uvicorn would be a few times slower comparing to Japronto and also its memory footprint would be significantly higher. So I guess it depends on your use case. I'd say FastAPI is more for complicated, expos
6. 6.▲
   by imbolc 6y ago

   Yeah, but it's already good enough for performance-critical microservices
7. 7.▲
   by imbolc 6y ago

   I agree with your point in general. But in other hand explicit urls feel like repeating yourself.
8. 8.▲
   A bit of sugar for the fastest Python framework(github.com)

   18 points by imbolc 6y ago|7 comments
9. 9.▲
   Google Analytics for Sapper (Svelte)(github.com)

   2 points by imbolc 7y ago|0 comments