Reactive applications with Akka.NET /

Chapter 8. Composing actor systems -- 8.1. Introducing Akka.NET remoting -- 8.2. Preparing to use remoting -- 8.3. Communicating with remote actors -- 8.4. Elastic scale across machines -- 8.5. Failure handling across machines -- 8.6. Akka. Remote security -- 8.7. Case study: Remoting, network appli...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Brown, Anthony (Software developer) (Autor)
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Shelter Island, NY : Manning Publications Co., [2019]
Temas:
Microsoft .NET Framework.
Microsoft .NET Framework
Application software > Development.
Object-oriented programming (Computer science)
Logiciels d'application > Développement.
Programmation orientée objet (Informatique)
Application software > Development
Acceso en línea:Texto completo (Requiere registro previo con correo institucional)
Tabla de Contenidos:
  • Intro
  • Copyright
  • Brief Table of Contents
  • Table of Contents
  • Preface
  • Acknowledgments
  • About this book
  • About the author
  • About the cover illustration
  • Part 1. The road to reactive
  • Chapter 1. Why reactive?
  • 1.1. The heart of the Reactive Manifesto
  • 1.2. Reactive systems vs. reactive programming
  • 1.3. Applying Akka.NET
  • 1.4. How does Akka.NET work?
  • Summary
  • Chapter 2. Reactive application design
  • 2.1. Basic reactive system design
  • 2.2. Reactive e-commerce application with actors
  • 2.3. Building on reactive foundations
  • Summary
  • Part 2. Digging in
  • Chapter 3. Your first Akka.NET application
  • 3.1. Setting up an application
  • 3.2. Actors
  • 3.3. Deploying an actor
  • 3.4. Communicating with actors
  • 3.5. Case study: Actors, concurrency, and phone billing
  • Summary
  • Chapter 4. State, behavior, and actors
  • 4.1. Preparing for the next message
  • 4.2. Setting appropriate runtime behaviors
  • 4.3. Finite state machines
  • 4.4. Case study: State machines, states and events, marketing analytics campaign
  • Summary
  • Chapter 5. Configuration, dependency injection, and logging
  • 5.1. Why do you need configuration?
  • 5.2. Configuring an actor deployment
  • 5.3. Dependency injection (DI)
  • 5.4. Configuring with HOCON
  • 5.5. Logging
  • 5.6. Case study: Configuration and distributed systems
  • Summary
  • Chapter 6. Failure handling
  • 6.1. Understanding failures
  • 6.2. Handling application-level failures
  • 6.3. Understanding transport-level failures
  • 6.4. Case study: Supervision, failure, chat bots
  • Summary
  • Chapter 7. Scaling in reactive systems
  • 7.1. Scaling up and scaling out
  • 7.2. Distributing work
  • 7.3. Routing strategies
  • 7.4. Case study: Scaling, throughput, advertising systems
  • 9.5. Case study: Testing, test-driven development, unit testing
  • Summary
  • Chapter 10. Integrating Akka.NET
  • 10.1. Integrating with ASP.NET
  • 10.2. Integrating with SignalR
  • 10.3. Custom integrations with akka.io
  • 10.4. Case study: IO, integration, IoT applications
  • Summary
  • Chapter 11. Storing actor state with Akka. Persistence
  • 11.1. Understanding event sourcing
  • 11.2. Using Akka. Persistence
  • 11.3. Akka. Persistence performance tuning
  • 11.4. Akka. Persistence performance tuning
  • 11.5. Case study: Persistence, storage, staged upgrades
  • Summary

Ejemplares similares