forked from slides/empowering-django-with-background-workers
This commit is contained in:
parent
8ff0aa4a69
commit
07d4b6f274
1 changed files with 42 additions and 6 deletions
46
slides.md
46
slides.md
|
@ -884,6 +884,34 @@ image: /pypi.png
|
|||
- The more testing done now, the better
|
||||
-->
|
||||
|
||||
---
|
||||
layout: center
|
||||
---
|
||||
|
||||
## Since Djangocon Europe 2024:
|
||||
|
||||
<br>
|
||||
|
||||
- Database worker 🚀
|
||||
- Improved testing on SQLite, PostgreSQL and MySQL
|
||||
- Improved testing on Windows, macOS and Linux
|
||||
- Add `manage.py check` support
|
||||
- Django Admin support for database backend
|
||||
- Store enqueued, started, and finished at times
|
||||
- Store task exceptions (with stacktrace)
|
||||
- Define task `priority` range and semantics
|
||||
- Prune completed database tasks
|
||||
- Transaction management
|
||||
- Soft and hard worker termination
|
||||
|
||||
<!--
|
||||
- This package was originally unveiled at Djangocon Europe 2024
|
||||
- Since then, a lot has changed
|
||||
- And there's more in open PRs
|
||||
- Many of these have been contributed by the community
|
||||
- I can't be more grateful
|
||||
-->
|
||||
|
||||
---
|
||||
layout: section
|
||||
---
|
||||
|
@ -893,7 +921,8 @@ layout: section
|
|||
<!--
|
||||
- There's still work to do
|
||||
- Features
|
||||
- Writing task queues takes time
|
||||
- Writing task queues takes time!
|
||||
- Writing _good_ task queues takes even longer
|
||||
- Improvements
|
||||
- Performance
|
||||
- Scalability
|
||||
|
@ -902,7 +931,10 @@ layout: section
|
|||
- Upstreaming
|
||||
- That's the big benefit
|
||||
- Else it really is just another standard
|
||||
- Once `django-tasks` is in a better state, it can become `django.tasks`
|
||||
- I've been told throwing 4500 lines of Python over the wall at Natalia and Sarah is a bad idea
|
||||
- So the interface will come first, then the DB backend
|
||||
- Whether it's separate releases too, we'll see
|
||||
- Then `django-tasks` can become `django.tasks`
|
||||
- Hopefully in time for the 5.2 release window
|
||||
- Adoption
|
||||
- The more people know about this, the better it is for everyone
|
||||
|
@ -930,10 +962,12 @@ background: /celery.svg
|
|||
- Is this the end for Celery and alike?
|
||||
- Not at all!
|
||||
- It's a great choice
|
||||
- Depending on your opinions
|
||||
- They have quite a head start
|
||||
- This is much more about usability and flexibility
|
||||
- If you need certain features, keep using them!
|
||||
- If you need certain features only available in Celery, keep using them!
|
||||
- Now you have the option of a Django-native API
|
||||
- Integrating deeply with your application
|
||||
- Which could even be Celery under the hood
|
||||
-->
|
||||
|
||||
|
@ -966,6 +1000,7 @@ class: flex justify-center flex-col text-xl
|
|||
- Doesn't mean they'll never come
|
||||
- With your help, we can make these happen
|
||||
- Except swappable argument serialization
|
||||
- It's JSON - it's fine
|
||||
- `pickle` is a bad idea
|
||||
-->
|
||||
|
||||
|
@ -1016,8 +1051,9 @@ layout: section
|
|||
- There have been many great contributors so far
|
||||
- There's plenty of work to do
|
||||
- And I can't do it alone!
|
||||
- If you maintain a worker library
|
||||
- Have interesting use cases
|
||||
- If you have interesting use-cases
|
||||
- Have built a worker library
|
||||
- Have used one in an interesting way
|
||||
- Or have been burned by one
|
||||
- ...
|
||||
-->
|
||||
|
|
Loading…
Reference in a new issue