I think it's always very important to think about transaction and especially with polyglot persistence, multiple data types. How do you have this in a distributed manner? So maybe from your view, how should we think about managing all these transactions? Maybe multiple databases, if they are involved, right? Is there any special thing that we have to think about? Yeah. I think that is always such a use case specific discussion that needs to be had with the business.
“The notion of transaction, consistency, and ACID compliance are many times tech imposed. It should be the business that makes the decision. We as technologists should not make that decision."
Pramod Sadalage is a Director at ThoughtWorks and the co-author of the Jolt Award winning “Refactoring Databases”. In this episode, we discussed data essentials in software architecture. Pramod started by explaining why dealing with data is hard in software architecture and some data related concerns we should think about when making architecture decisions. He then shared the thought process of how we can choose the right database for our purpose and shared insights on data modeling differences between SQL and NoSQL. Pramod also touched on the important considerations in managing transactions and the trade-offs between ACID and eventual consistency. Towards the end, Pramod shared practical advice on the step-by-step how we can split a monolithic database through database refactoring.
Listen out for:
- Career Journey - [00:04:23]
- Data is Hard - [00:15:57]
- Data Related Architecture Concerns - [00:18:36]
- Choosing the Right Database - [00:24:19]
- Data Modeling in SQL vs NoSQL - [00:30:28]
- Managing Transactions - [00:37:31]
- Tradeoff Between ACID & Eventual Consistency - [00:44:06]
- Refactoring Database - [00:46:58]
- 3 Tech Lead Wisdom - [00:54:58]
_____
Pramod Sadalage’s Bio
Pramod Sadalage is Director at ThoughtWorks where he enjoys the rare role of bridging the divide between database professionals and application developers. In the early 00’s he developed techniques to allow relational databases to be designed in an evolutionary manner based on version-controlled schema migrations. He is co-author of Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures, co-author for Building Evolutionary Architectures - Automated Software Governance, co-author of Refactoring Databases: Evolutionary Database Design, co-author of NoSQL Distilled: A Brief Guide to the Emerging World of Polyglot Persistence, author of Recipes for Continuous Database Integration and continues to speak and write about the insights he and his clients learn.
Follow Pramod Sadalage:
- Twitter – @pramodsadalage
- LinkedIn – linkedin.com/in/pramodsadalage
- Website – sadalage.com
- Database Refactoring – databaserefactoring.com
- DevOps for DBA – devopsfordba.com
- Agile Data – agiledata.org
_____
Our Sponsors
Are you looking for a new cool swag? Tech Lead Journal now offers you some swags that you can purchase online. These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available. Check out all the cool swags available by visiting techleadjournal.dev/shop. And don't forget to brag yourself once you receive any of those swags.
Like this episode?
Show notes & transcript: techleadjournal.dev/episodes/131
Follow @techleadjournal on LinkedIn, Twitter, and Instagram.
Buy me a coffee or become a patron.
