1
Fork 1

Change reporting example to a generic list

This commit is contained in:
Jake Howard 2024-06-05 09:22:22 +01:00
parent 67ebe2dc71
commit 9c594b8337
Signed by: jake
GPG key ID: 57AFB45680EDD477

View file

@ -271,21 +271,36 @@ background: https://images.unsplash.com/photo-1518770660439-4636190af475?q=80&w=
--> -->
--- ---
layout: cover layout: image-right
background: https://images.unsplash.com/photo-1711606815631-38d32cdaec3e?q=80&w=2070&auto=format&fit=crop&ixlib=rb-4.0.3 image: https://images.unsplash.com/photo-1711606815631-38d32cdaec3e?q=80&w=2070&auto=format&fit=crop&ixlib=rb-4.0.3
class: text-xl
--- ---
## Example: # Examples
# Complex reporting
- Compiling code
- Complex reporting
- File uploads
- Model training
- PDF generation
- Resizing images
- Sending email
- Transcoding video
- ... 🤯
<!-- <!--
- An example: Complex reporting - Background workers have a world of uses
- Something analytical, crunching lots of data - It's important to consider the scale when designing a feature
- It might be fast locally - It might be fine locally
- As your application grows, there'll be more data, so it'll likely take a lot longer - As your application grows, there'll be more data, so it'll likely take a lot longer
- Rather than force the user to wait, let them get the data when it's ready - The user shouldn't have to wait ages for your application
- They can get back on with their day - They can get back on with their day
- Web servers can get back to processing other requests - Web servers can get back to processing other requests
- This list is quite long
- And it's nowhere near complete
- It's a very generic tool
- When designing an app at scale with these features
- Maybe consider moving it to the background.
--> -->
--- ---