{"id":36,"date":"2024-02-13T14:06:09","date_gmt":"2024-02-13T11:06:09","guid":{"rendered":"http:\/\/caitiem.com\/?p=36"},"modified":"2024-02-13T15:28:50","modified_gmt":"2024-02-13T12:28:50","slug":"creating-restful-services-using-orleans","status":"publish","type":"post","link":"http:\/\/www.caitiem.com\/2014\/04\/04\/creating-restful-services-using-orleans\/","title":{"rendered":"Creating RESTful Services using\u00a0Orleans"},"content":{"rendered":"\n

After the announce of the Orleans preview, there was a lot of discussion on Twitter. \u00a0One comment in particular caught my eye.<\/p>\n\n\n\n

\n

.NET\u2019s actor model uses static factories, RPC Interfaces and code-gen client proxies for comms, WCF all over again: http:\/\/t.co\/PyIq291Kvh<\/p>\n\n\n\n

\u2014 Demis Bellot (@demisbellot) April 3, 2014<\/p>\n<\/blockquote>\n\n\n\n

I think this is a bit of a misunderstanding of how Orleans can and should be used in production services, this blog post is an attempt to clarify and demonstrate how to build RESTful, loosely coupled services using Orleans.<\/p>\n\n\n\n

Orleans Programming Model<\/h3>\n\n\n\n

Orleans is a runtime and programming model for building distributed systems, based on the actor model.  In the programming model there are a few key terms.<\/p>\n\n\n\n