Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Microservices with Azure

You're reading from  Microservices with Azure

Product type Book
Published in Jun 2017
Publisher Packt
ISBN-13 9781787121140
Pages 360 pages
Edition 1st Edition
Languages
Authors (2):
Rahul Rai Rahul Rai
Profile icon Rahul Rai
Namit Tanasseri Namit Tanasseri
Profile icon Namit Tanasseri
View More author details

Table of Contents (23) Chapters

Title Page
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
Part 1 – Laying The Foundation
Part 2 – Microsoft Azure Service Fabric
Part 3 – Microservice Architecture Patterns
Part 4 – Supplementary Learning
1. Microservices – Getting to Know the Buzzword 2. Microsoft Azure Platform and Services Primer 3. Understanding Azure Service Fabric 4. Hands-on with Service Fabric – Guest Executables 5. Hands on with Service Fabric – Reliable Services 6. Reliable Actors 7. Microservices Architecture Patterns Motivation 8. Microservices Architectural Patterns 9. Securing and Managing Your Microservices 10. Diagnostics and Monitoring 11. Continuous Integration and Continuous Deployment 12. Serverless Microservices

What is an Actor?


An Actor is a specialized service that is much more granular in intent than the typical services that we build. The Actor programming model ensures that individual entities in your solution are highly cohesive and decoupled. An Actor is designed to work within a set of constraints:

  • The various Actors of an application can only interact through asynchronous message passing. The messages that are exchanged between Actors should be immutable.
  • An Actor can function within the boundary of domain that it is designed for. For instance, a shopping cart actor cannot implement or expose functionality of a product listing Actor.
  • An Actor can only change its state when it receives and processes a message.
  • An Actor should be single-threaded and it should process only one message at a time. Another message should be picked up by the Actor only when the Actor operation has completed.
  • An Actor may spawn new Actors and send a finite number of messages to the other Actors in the application...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}