[Avalaxy]

Not necessarily cloud, but a lot of these patterns have to do with asynchronous distributed systems design (for example leader election, all the queueing patterns, sharding, circuit-breaker). CQRS is part of that (eventual consistency, scalability, etc.). Distributed systems are not necessarily tied to the cloud, but it's a very good fit because of the flexibility the cloud offers.

[talles]

There's a lot of people out there doing distributed systems that are hosted "indoors" (Or should I say "on earth"? What's the opposite of "cloud"?). A lot.

Don't you agree that putting "cloud" on the title may be misleading?

[arethuza]

'What's the opposite of "cloud"'

"on-premise"

[_ea1k]

So what is an on-premise cloud?

[softawre]

Lol. Or "private clouds" as our CFO calls them...

[mynameisvlad]

Not really. Them being cloud design patterns says nothing about being able to to be used outside the cloud, just that the people who made them designed them for the cloud.

[talles]

> designed them for the cloud

I guess I have a different understanding of designing for than you them.

[mynameisvlad]

Yes, you clearly do. If they were thinking about the cloud and what patterns might be appropriate for it, then it's being designed for the cloud. As I said before, just because it's designed for A doesn't mean it isn't also applicable to X, Y, Z, just that they weren't specifically thinking about those when they wrote the document.