Type
New feature
Description
Request to highlight internally developed patterns for CF primitives.
Benefit
I am a huge fan of the CF Dev YouTube channel, and I appreciate all the hard work y’all put into it. I think some form of this already exists in some sense in terms of what you post (specifically some of the lightning talks I’ve seen on there) but it’d be awesome to get some insight into how you all use your own tools. Now, to be clear, I’m not asking for y’all to reveal a bunch of trade secrets, however, I do get the sense that y’all dogfood very heavily, and I imagine there are some patterns and SOPs that have been developed internally that go a bit beyond what you already highlight in the most highly trafficked videos on the channel (which in turn seem to inform or be informed by the docs) while still being abstractable enough to be something closer to established conventions or patterns.
For example, I often find myself starting a project using several workers deployed discretely until I reach a tipping point when I start to consolidate things in a way that makes sense so the project doesn’t get bogged down in endless deployments – a primer on project structure for specific use cases would give a lot of insight on how to take full advantage of CF’s offerings in a structured way (e.g. a pages app that uses functions and queues – afaik this is a quirky setup that requires at least two deployments since pages functions can’t run a queue consumer).
I completely understand if the point is to keep the primitives, well, primitive and unprescriptive. By the same token, seeing how some of these primitives can be organized or marshalled in the context of shipped, scaled projects would be super helpful for folks who are familiar with mid to large scale dev but not CF’s offerings specifically.