Architecting a microservices solution in .NET | Richard Banks at DDD Sydney 2016 - SSW TV - Learn from Professional Software Developers

SSW TV brings you all the best content from the 2016 DDD event in Sydney.

In this presentation, Richard Banks talks about designing and building microservices in .NET.

Talk outline:

“Buzz word! More buzz words! And another buzz word!! Now that that’s out of the way, if you’re thinking of heading down the microservices path, then how do you do it? How do you build the services? What do you need to think about if you’re starting from scratch? What if you’re converting a legacy app? How do we deal with versioning? Do we have to use a NoSQL solution, just because Netflix does? Do we need to use docker/containers? What about the code? Show me the code! Well, that’s what this session is all about. Designing and building microservices in .NET and then handling a bunch of other concerns that a microservices approach will force you to think about. Sounds interesting, doesn’t it? You betcha. See you in the session!”

We hope you enjoy this content. You can watch more of DDD on SSW TV.

Take the Poll!

A question about the topic

About the speakers

Mr Microservices

Richard Banks has developed software for the last 20 years for a wide range of industries and development platforms and over the years and has filled many roles including developer, team lead, project manager and CIO/CTO. He is a Professional Scrum Trainer, author of the Visual Studio 2012 Cookbook, runs the Sydney Alt.Net user group and the Talking Shop Down Under podcast, owns and contributes to a few open source projects and has spoken at Microsoft Tech.Ed and a number of other events and user groups around the country.

If you want to get in touch he tweets at @rbanks54 and blogs at https://www.richard-banks.org/. He currently works as a Principal Consultant for Readify and is a Microsoft Visual Studio ALM MVP.

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings. In this video, Adam Cogan shares practical etiquette tips to help meetings run more smoothly—from introducing people who join the room, to announcing yourself when joining a call, using screen sharing respectfully, and ending meetings with a recorded summary that can automatically create a Product Backlog Item (PBI).

These simple communication habits improve collaboration, reduce confusion, and make hybrid meetings more inclusive and productive.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!