Nick Pruehs's Blog
Technical Director of Daedalic Entertainment. Trading card game geek. Microsoft MVP. Thoughts are my own.
Expert Blogs
In the previous part of this series, we created the frontend, a small Universal Windows Platform game that accesses our backend. Finally, we'll be deploying the whole application to the cloud.
In the previous part of this series, we learned how to persist state to a scalable database. Next, we'll be creating the frontend, a small Universal Windows Platform game that accesses our backend.
In the previous part of this series, we added the web service that acts as interface between the frontend and the actual backend services. In this post, we learn how to persist state to a scalable database.
In the previous part of this series, we've started to create a small cloud backend with a single actor. In this post, we are adding the web service that is acts as interface between the frontend and the actual backend services.
Getting started with cloud development can be overwhelming at first. In this blog series, I'm walking you through the basics of getting your gaming backend up and running in the cloud and storing your player data in a scalable cloud storage.
Nick Pruehs's Comments
Comment In:
[Blog - 03/05/2017 - 09:20]
Hey Johan, r n r ...
Hey Johan, r n r nthanks for the feedback : r n r n1. Yes, actors may indeed save their own state. However, I personally prefer using another database, mainly for separation of concerns DocumentDB can be accessed from other sources as well . If you 're interested, you can ...
Comment In:
[Blog - 02/14/2017 - 09:33]
