OdeToCode IC Logo

Interview on CloudSkills.fm

Thursday, April 18, 2019

CloudSkills.fm podcast

There's a new episode of the CLoudSkills.fm podcast available, and the episode features yours truly!

In this episode I talk with Scott Allen about building and running applications in the Azure cloud. Scott is a legendary software developer, conference speaker, trainer, and Pluralsight author.

I hope you enjoy the show.

Gravatar Ian Thursday, May 30, 2019
Scott, I enjoyed this discussion and am curious to know a little more on the SQL/NoSQL point you covered because I run into similar situations frequently. In the podcast you described a patient record that when stored in a SQL Server database, required a large number of joins to retrieve the full record (which might then be returned by an API, etc.) You then, if I'm remembering correctly described how storing it in a document DB made that retrieval much easier but led to a problem when implementing reporting of aggregate data. So I'm curious in general how you prefer approaching that situation now in new development. If SQL Server is the go-to storage at my company, and I'm now looking at storing e.g. a customer record which will have a bunch of associated data such that retrieving a customer by ID would need a lot of joins- Would you lean toward going with SQL Server and creating a database view to join up the customer data? Just live with the joins in the query? Or would you rather store customers in a document DB and aggregate data into a data warehouse for reporting?
Gravatar scott Monday, June 3, 2019
I'd go with the option of storing customers in a document database and having another data source for reporting. In the cloud this is easy (perhaps more expensive, but it is easy to provision as many data storage platforms as you need).
Comments are closed.