Rename global/non-global to async and sync

[thrawn01]

Purpose

Global can be a confusing term and doesn't convey what it actually does. Change gubernator to use async and sync instead of Global behavior. Also, we should default to async behavior by default.

[dimaqq]

+1 on global/async being the default.

Perhaps if the default is reasonable, the naming is less of an issue.

Personally, I don't feel that sync/async labels are good user-facing or operator-facing description, it feels more like an implementation detail. I wonder if some other terminology could be borrowed, e.g. write-through/write-behind, or immediate/batched?

[thrawn01]

Hurm, the more I think about it, we are really talking about write concerns.

I asked ChatGPT about it.

Renaming the "global" behavior in your rate limiting service, Gubernator, to better convey its functionality can improve clarity and understanding for users. Here are a few suggestions based on the description of how it works:

• EventuallyConsistent: This name directly reflects the behavior of the write being queued and forwarded to the owning node, ensuring eventual consistency.
• QueuedWrite: This name highlights the queuing mechanism used to handle writes, which is a key aspect of the "global" behavior.
• DistributedWrite: This name emphasizes the distributed nature of the write process, where the write is not immediately forwarded to the owning node but rather handled in a distributed manner.
• AsyncWrite: This name suggests that the write is handled asynchronously, which aligns with the queuing and eventual forwarding mechanism.
• CentralizedQueue: This name emphasizes the central queuing mechanism used to manage writes, which is a key aspect of the "global" behavior.

These suggestions aim to provide a more accurate and descriptive name for the "global" behavior in your rate limiting service. 😆

Not too bad, any thoughts @Baliedge ?

[Baliedge]

I'm partial to EventuallyConsistent because it does exactly what it sounds like. And more descriptive than simply Async. The AGI description fits, too.

Then for default behavior, you will need the converse term. Perhaps FullyConsistent?

[dimaqq]

My preference would be for "Eventually Consistent" and "Synchronous".

Both are clear and well-established jargon in databases and distributed systems.