filmov
tv
Software Architecture in Golang: Shared Database vs Database Per Service?
Показать описание
What's the difference between Shared Database and Database Per Service?
When we are talking about the Shared Database Pattern, we are talking about using one single datastore for the implemented services; in the case of Database Per Service pattern this means defining dedicated datastores per service with he end goal is to make this datastore only available to the service directly, no other direct access is allowed.
== Relevant Links
== All Go/Golang Playlists
== Socials
00:00 - Introduction to Shared Database vs Database Per Service
00:35 - Shared Database Pros
01:26 - Shared Database Cons
01:59 - Database Per Service Pros
02:32 - Database Per Service Cons
03:52 - Conclusion
=== Who am I?
Hello👋🏼! I'm Mario, a Hands-on Software Architect and Lead Backend Engineer with more than 16 years of professional experience building all kinds of software including on-premise Industrial Automation Systems, Linux Accessibility Desktop and Browser Components as well as Distributed Advertising Microservices.
Every week I will share with you different topics I've learned while working for small startups and large companies including the processes I've followed over the years for successfully delivering complex enterprise systems from start to end.
Subscribe if you like Software Development, Software Architecture and Systems Design!
Keep it up. Don't give up!
#golang #softwarearchitecture #systemdesign
=== Our Vlog Channel
=== Affiliate links
DISCLAIMER: Some of the links shared above are affiliate links. As a member of these affiliate programs, I earn a small commission from your purchases at no additional cost to you. Thank you in advance for your support!
When we are talking about the Shared Database Pattern, we are talking about using one single datastore for the implemented services; in the case of Database Per Service pattern this means defining dedicated datastores per service with he end goal is to make this datastore only available to the service directly, no other direct access is allowed.
== Relevant Links
== All Go/Golang Playlists
== Socials
00:00 - Introduction to Shared Database vs Database Per Service
00:35 - Shared Database Pros
01:26 - Shared Database Cons
01:59 - Database Per Service Pros
02:32 - Database Per Service Cons
03:52 - Conclusion
=== Who am I?
Hello👋🏼! I'm Mario, a Hands-on Software Architect and Lead Backend Engineer with more than 16 years of professional experience building all kinds of software including on-premise Industrial Automation Systems, Linux Accessibility Desktop and Browser Components as well as Distributed Advertising Microservices.
Every week I will share with you different topics I've learned while working for small startups and large companies including the processes I've followed over the years for successfully delivering complex enterprise systems from start to end.
Subscribe if you like Software Development, Software Architecture and Systems Design!
Keep it up. Don't give up!
#golang #softwarearchitecture #systemdesign
=== Our Vlog Channel
=== Affiliate links
DISCLAIMER: Some of the links shared above are affiliate links. As a member of these affiliate programs, I earn a small commission from your purchases at no additional cost to you. Thank you in advance for your support!
0:04:08
Software Architecture in Golang: Shared Database vs Database Per Service?
0:14:06
Software Architecture in Golang: Testability
0:13:13
Software Architecture in Golang: Resilience in HTTP Servers
0:12:27
Software Architecture in Golang: Measuring Instability as Software Package Metrics
0:07:01
Software Architecture in Golang: Cache-Aside Cloud Design Pattern for Scalability
0:05:56
Software Architecture in Golang: Throttling Cloud Design Pattern for Scalability and Security
0:19:01
Software Architecture in Golang: Security - Dependencies
0:07:31
Software Architecture in Golang: Caching Pattern: Write-Through for Scalability
0:06:02
Top 7 Coohom Features Every Designer & Architect Should Know | Interior Design Software 2025
0:13:07
Software Architecture in Golang: Orchestrator Pattern
0:11:35
Software Architecture in Golang: Externalized Configuration Pattern
0:11:40
Software Architecture in Golang: Choreography Pattern
0:08:30
Software Architecture in Golang: Architecture Decision Records (ADRs)
0:08:29
Software Architecture in Golang: Vulnerability Management with govulncheck
0:12:15
Software Architecture in Golang: Circuit Breaker Cloud Design Pattern for Reliability
0:14:35
Software Architecture in Golang: Security - Databases, SQL Injection and Permissions
0:11:08
Software Architecture in Golang: Observability
0:05:23
Software Architecture in Golang: Claim Check / Reference Based Messaging Pattern
0:08:55
Multi-Tenant: Database Per Tenant or Shared?
0:16:04
Software Architecture in Golang: C4 Model for Diagraming and Documentation
0:02:56
Software Architecture in Golang: Scalability vs Elasticity
0:06:11
Software Architecture in Golang: Anti-Corruption Layer Pattern
0:06:47
Software Architecture in Golang: Quality Attributes, Non-Functional Requirements and ilities
0:09:54
Software Architecture in Golang: Health Check Pattern (gRPC Example)
Комментарии