Skip to Content
Software Architect's Handbook
book

Software Architect's Handbook

by Joseph Ingeno
August 2018
Beginner
594 pages
22h 33m
English
Packt Publishing
Content preview from Software Architect's Handbook

Stateless versus stateful microservices

Each microservice can either be stateless or stateful. A system that uses microservices typically has a stateless web and/or mobile application that uses stateless and/or stateful services.

Stateless microservices do not maintain any state within the services across calls. They take in a request, process it, and send a response back without persisting any state information. A stateful microservice persists state in some form in order for it to function.

Rather than store this state internally, a microservice should store state information externally, in some type of data store. Examples of a data store to persist state include a relational database management system (RDBMS), a NoSQL database, or some ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Solutions Architect's Handbook

Solutions Architect's Handbook

Saurabh Shrivastava, Neelanjali Srivastav
Solutions Architect's Handbook - Second Edition

Solutions Architect's Handbook - Second Edition

Saurabh Shrivastava, Neelanjali Srivastav
Software Architecture in Practice, 4th Edition

Software Architecture in Practice, 4th Edition

Len Bass, Paul Clements, Rick Kazman
Solutions Architect's Handbook - Third Edition

Solutions Architect's Handbook - Third Edition

Saurabh Shrivastava, Neelanjali Srivastav

Publisher Resources

ISBN: 9781788624060Other