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

Actors in Service Fabric


Each Reliable Actor service you write is a partitioned and stateful Reliable Service. Service Fabric API provides a asynchronous and single-threaded programming model to implement Actors. You only need to work on the Actor implementation, the platform takes care of lifecycle, upgrades, scale, activation, and so on.

Actors closely resemble objects in object-oriented programming. Similar to the way a .NET object is an instance of a .NET type, every Actor is defined as an instance of an Actor type. For example, there may be an Actor type that implements the functionality of a sensor monitor and there could be many Actors of that type that are distributed on various nodes across a cluster. Each such Actor is uniquely identified by an Actor ID. Repeated calls to the same Actor ID are routed to the same Actor instance. For this reason, Actor services are always stateful services.

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}