From the course: Software Development Life Cycle (SDLC)

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Microservices: Deployment scenarios

Microservices: Deployment scenarios

From the course: Software Development Life Cycle (SDLC)

Start my 1-month free trial Buy for my team

Microservices: Deployment scenarios

“

- [Instructor] Now that we are familiar with the basic concepts of microservices, let's take a moment to review a few architectural and implementation patterns. Let's talk about data management first. You could have a single database for multiple services. The advantage with this approach is that you do not need to worry about any data replication across multiple databases. But the disadvantage is that there are multiple services with dependencies on a single database. There is a higher risk of any database change causing issues with multiple services. You can minimize this risk by writing code that is agnostic of database schemas with a data access layer, but there's always some risk. Another disadvantage is that not all services require identical types of databases. For example, a service may need transactional rights and fixed schema, and thereby would need a relational database, whereas another service could only need storing key value pairs, and so a NoSQL database would be more…

Contents