So far, our solution uses a simple console application as the client. A more realistic scenario is for Orleans to be fronted by a Web API, such as ASP.NET Core.
Orleans should never be exposed directly to the Internet. Its interface is intended only for use on an internal network as it doesn’t deal with the authentication and authorization concerns required with public-facing services.
It’s not necessary to build a Web API for Orleans; it’s equally valid to use it in a completely headless deployment, such as processing ...
