From a3d48c2be94969abe350346ee5bf5363b2d5d158 Mon Sep 17 00:00:00 2001 From: Jake Howard Date: Sun, 2 Jun 2024 22:13:25 +0100 Subject: [PATCH] Refine speaker notes --- slides.md | 197 ++++++++++++++++++++++++++++++------------------------ 1 file changed, 109 insertions(+), 88 deletions(-) diff --git a/slides.md b/slides.md index e5d9eb1..39fdf30 100644 --- a/slides.md +++ b/slides.md @@ -20,8 +20,8 @@ themeConfig: @@ -157,8 +157,8 @@ flowchart TD - They keep requests quick - Move the slow bits somewhere else - - So the user doesn't have to wait - - This improves throughput and latency + - User doesn't have to wait + - Improves throughput and latency --> --- @@ -197,7 +197,7 @@ layout: section - But that doesn't mean they're useful for everything, all the time - As with all great things: "It depends" - - The added complexity may not be worth it + - Trade-off between complexity and functionality - A few things to consider --> @@ -209,12 +209,12 @@ background: https://images.unsplash.com/photo-1518729371765-043e54eb5674?q=80&w= # Does it take time?{.text-right} --- @@ -247,11 +247,11 @@ flowchart BT --- @@ -263,11 +263,11 @@ background: https://images.unsplash.com/photo-1518770660439-4636190af475?q=80&w= --- @@ -281,12 +281,11 @@ background: https://images.unsplash.com/photo-1711606815631-38d32cdaec3e?q=80&w= --- @@ -381,15 +380,14 @@ for user in page.subscribers.iterator(): - [click]This works perfectly fine - Scales _relatively_ well - - But has some issues - - If connecting to the email server takes a while, the user has to wait - - Usually only a few ms - - Might take a few seconds - - Subsequent emails are delayed whilst we process the earlier ones - - If something goes wrong with one email, the others won't send - - What if your email gateway is down altogether - do your requests start erroring? - - How do you handle it if they do? - - That web worker (eg gunicorn) can't process any other requests until this is done +- But has some issues + - If connecting to the email server takes a while, the user has to wait + - Usually only a few ms + - Might take a few seconds + - If something goes wrong with one email, the others won't send + - What if your email gateway is down altogether - do your requests start erroring? + - How do you handle it if they do? +- That web worker (eg gunicorn) can't process any other requests until this is done --> --- @@ -508,7 +506,7 @@ for user in page.subscribers.iterator(): - Its own features - Its own configuration - Its own caveats / implementation details -- What if we wanted to switch to Celery? +- What if we wanted to use Celery instead? - [click]Well, that's easy - [click]Just change a few lines - [click]But there in lies the problem @@ -525,22 +523,21 @@ backgroundSize: 50% --- @@ -551,8 +548,10 @@ backgroundSize: 49% @@ -735,11 +734,11 @@ class: flex justify-center text-2xl flex-col - As I've been told whilst working on this DEP - Why not just vendor something existing? - If not Celery, then something else - - That's not really the goal - - Shared API contract is - - The built-in version will hopefully become great - - But must be done with careful planning and consideration - - Django needs to remain the stable and reliable base it always has been +- That's not really the goal + - Shared API contract is + - The built-in version will hopefully become great + - But must be done with careful planning and consideration + - Django needs to remain the stable and reliable base it always has been --> --- @@ -760,25 +759,25 @@ class: flex justify-center text-xl flex-col @@ -836,12 +835,11 @@ layout: center - And I've had many times - ElasticSearch is quite likely better for the ~10% of people who need it - But that doesn't mean the other 90% of people won't be happy with PostgreSQL - - And probably wouldn't benefit from ElasticSearch anyway - - And definitely won't get a return on the extra hosting cost and complexity + - Probably wouldn't benefit from ElasticSearch anyway + - Definitely won't get a return on the extra hosting cost and complexity - They'll be perfectly happy with Postgres FTS - Let them get started the easiest way possible - We can still invite them into ElasticSearch when they're ready - --> --- @@ -850,6 +848,10 @@ layout: section # Where are we now? + + --- layout: image image: /dep.png @@ -873,7 +875,7 @@ layout: section - The ORM backend is where the magic happens - Tell me about all the bugs in my code - The more testing we can do now, the better - - There are still features to implement and improve +- There's still work to do --> --- @@ -885,15 +887,14 @@ layout: section --- @@ -913,12 +914,13 @@ background: /celery.svg --- @@ -941,11 +943,13 @@ class: flex justify-center flex-col text-xl --- @@ -958,14 +962,16 @@ background: https://images.unsplash.com/photo-1519187903022-c0055ec4036a?q=80&w= --- @@ -975,12 +981,7 @@ layout: section # What's next?
- +
+--- +layout: center +class: text-center text-xl +--- + +# Let's chat! + + + +
+ +
+ + + --- layout: end --- END - -
- -