meta_pixel
Tapesearch Logo
Log in
Thoughtworks Technology Podcast

DevOps and Microservices: Architectural Considerations

Thoughtworks Technology Podcast

Thoughtworks

Technology, Careers, Business

4.558 Ratings

🗓️ 10 March 2015

⏱️ 22 minutes

🧾️ Download transcript

Summary

In this episode of the ThoughtWorks Podcast, Neal Ford explains to Johannes Thönes what architectural considerations can be derived from the DevOps movement. This episode is a quick introduction to what Microservices are, what kind of architectural principles can be used to implement them, what a good test strategy for microservices can can look like. We also explain why you should have a continuous delivery practice running before starting to develop Microservices.

Transcript

Click on a timestamp to play from that location

0:00.0

All right. So I'm sitting here with Neil Ford.

0:04.6

Neil, why don't you just start by introducing yourself?

0:08.5

Okay. I'm Neil Ford. I am a director at ThoughtWorks. I've been here about 10 years. I'm also a software architect.

0:16.3

Most of my consulting work now is in the intersection of continuous delivery and architecture.

0:22.5

And I also have as part of my title, Meme Rangler, which is an unusual title in the tradition

0:27.8

of ThoughtWorks' unusual titles.

0:30.4

Meme is the Richard Dawkins term for viral unit of thoughts.

0:33.4

So a meme wrangler is someone who spreads thoughts around.

0:35.8

So that's part of my job at ThoughtWorks as well.

0:38.0

So what is the thought you would like to spread today?

0:41.3

Well, it's really the kind of observation.

0:43.7

There's really a lot of interest in the microservice style architecture out in the world right now.

0:49.1

It's really kind of the realization of why that's so popular, and I think it's because it's really the first post DevOps revolution architecture.

0:58.7

It's the first architectural style that really fully embraces all these lessons we learn from

1:03.5

DevOps and the continuous delivery.

1:05.6

I think all architecture going forward have to take those things to account because

1:10.8

traditionally the thing that's been

1:12.1

tricky about architecture it's hard to change later in fact that's one of the common kind of

1:17.2

colloquial definitions out in the world for software architectures the parts that are hard to change later

1:22.2

but if you look at someone like netflix or amazon they've actually built changeability into

1:27.2

their architecture,

1:28.2

making change relatively easy in those worlds. So I think that by embracing those kind of operational

...

Please login to see the full transcript.

Disclaimer: The podcast and artwork embedded on this page are from Thoughtworks, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Thoughtworks and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.

Copyright © Tapesearch 2026.