Blog post topics

[tylerbutler]

I've been building a list of possible blog posts for the Fluid blog (see issue #8011).

I'd like input and feedback on the post ideas, so I am sharing them here. I've listed them in the rough priority order, but after the first 2-3 they're all about the same.

I want to start posting in January, with a monthly cadence initially.

Post Ideas

1. Getting to Fluid Framework 1.0 -- @tylerbutler

This will explain what we're focused on for 1.0, how we're planning and executing the work, and how folks can participate.

2. View model data vs. backend data schema -- @skylerjokiel

In many trivial Fluid examples, people use Fluid directly in the view model layer. This isn't necessary, and in fact, many apps moving to Fluid will have a separation between their view model schema and how they store their data in a permanent store. The same can apply to apps using Fluid.

3. Fluid, SignalR and Web Sockets (oh my!) -- @skylerjokiel

It's not immediately obvious what Fluid provides over vanilla web sockets or a library like SignalR. This post would explain the differences and tradeoffs.

4. How can Fluid safely make changes locally? How is eventual consistency ensured?

This post will deep dive into eventual consistency and how DDSes like SharedSequence ensure it while enabling local changes to be merged optimistically. A walk-through or animation of the merge-tree algorithm might be helpful as an illustration.

5. The progression of a Fluid Framework package

We have some packages that are experimental, and other packages that aren't. What's the difference? What's the process to get a package to be non-experimental?

6. How we think about upgrade

Upgrade in Fluid is interesting because of the combination of code and data. This post would share how we think about those challenges on the Framework side, and how we're adressing them.

7. Is Fluid for multiplayer games? Is Fluid netcode?

Fluid is not necessarily a great fit for games. Fluid is working under a different set of priorities and and scenarios than most game scenarios, and thus Fluid can offer more guarantees -- like eventual consistency -- than most games need. This post would epxlore the differences and why Fluid's model is useful in collaborative apps.

8. Using Fluid to explore operations-based systems

This is more of an academic post, focused on how to use Fluid as a tool to explore operations-based designs. Practically speaking this is creating a DDS, but the focus of the post would be using Fluid as an operations-based system to illustrate concepts or explore designs.