3 years ago

Category: Database, Data, Architecture

When you build a large, multiservice application, deciding where you put the data is just as important as determining how you architect the application itself. An essential but often overlooked aspect of architecting service and microservice-based architectures is deciding where your application data resides.

Whether you are building a new application or migrating an existing application to a service-based architecture, it is critically important to be mindful of where you store data — and the rest of the application state — within your application or system.

A stateful service is a service that requires data (application state) retained during the life of the application, and multiple requests to the service use the data.

When architecting the structure of your application and the services that make up the application, it is essential to consider the data needs and requirements of those services.