List who uses Orleans in production about orleans

[MovGP0]

I guess currently that's only 343 Industries.

[ReubenBond]

There are more. We use it in production for example, & I know of others.

[gabikliot]

There are multiple (at least 10) production usages within Microsoft, in various groups and divisions, in different domains.
We have usages in gaming, social, monitoring, real-time analytics, IoT, to name a few.
And multiple usages outside Microsoft.

[pherbel]

I guess that it is good to know and help if somebody is thinking about the usage. like node.js usage list

@gabikliot Could you please create a list about the Microsoft usage if it is not confidential?
@ReubenBond and others would expand this list later.

[sergeybykov]

At least some internal Microsoft usages are confidential for various reasons. To err on the safe side, we need to treat them all as confidential, unless the product groups themselves decide to speak up.

[wmattlong]

We used Orleans on an interesting High Altitude Balloon experiment, http://pegasusmission.com, to perform real-time IOT from 85K ft in the upper atmosphere. Orleans allowed to be not only transfer telemetry from our high altitude payload to a Web site in ~20ms, it also allowed us to control operations during the flight in the remote and hostile environment of Near Space (10km-200km) above the surface of the earth. Additionally, we used Orleans to help track the payload in real-time on an updateable Bing Map. Blog posts, photos, and video are on the site mentioned above.

[pherbel]

I've created a md file for this list. You can find here: List
I don't know which is the right place for this maybe the wiki.
@gabikliot Could you put it into the wiki?
Thanks

[gabikliot]

Thank you.
Lets host it as an md file under https://github.com/dotnet/orleans/tree/master/misc.
That way others will be able to submit pull requests against it (I don't think one can submit pull request against Wikis right?).
Can you please submit a PR to include this file in Orleans/misc?

[gabikliot]

I guess we can close this issue now. Thank you @pherbel!