Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Microservices with Azure

You're reading from   Microservices with Azure Build highly maintainable and scalable enterprise-grade apps

Arrow left icon
Product type Paperback
Published in Jun 2017
Publisher Packt
ISBN-13 9781787121140
Length 360 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
 Rai Rai
Author Profile Icon Rai
Rai
Namit Tanasseri Namit Tanasseri
Author Profile Icon Namit Tanasseri
Namit Tanasseri
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

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 FREE CHAPTER 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

Remindable Actors


Problem

An Actor based application may need to send several messages to an Actor instance. For example, an e-commerce application may require an Actor instance to update the user shopping cart. The Actor instance might be busy completing the process of adding a previous item to the cart. Since, the Actor operations are single threaded, the application will need to wait for the Actor to finish its previous operation to proceed with the next one.

The wait to complete operations degrades performance of application and affects user experience:

Remindable Actor (Problem)

Solution

All Actors in the system should message themselves when they receive a request. In the above example, the shopping cart Actor can accept the request to add more items to the shopping cart and send a message to itself with the details of item to add to the shopping cart. Once the Actor instance is done processing the previous request, it can consume a message from the queue and add the item to the shopping...

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 £13.99/month. Cancel anytime
Visually different images