Summary: For our inaugural podcast QCon chair Wesley Reisz talks to Adrian Cockcroft, who works for Battery Ventures where he advises the firm and its portfolio companies about technology issues and also assists with deal sourcing and due diligence.
Why listen to this podcast
•	Over the last year a large number of frameworks and libraries for building microservices have emerged and we're seeing a lot of rapid change.
•	The stack you choose will often be based on the main language you use, so for example Netflix’s stack is language agnostic but the tooling is very Java-centric.
•	Architectural choices can have a profound impact on success, so some-thing as simple as an overly long timeout with retries can cause your system to suffer from a congestion collapse problem.  Have a large timeout at the edge, and progressively smaller and smaller timeouts as you get deeper into the system.
•	Start with a monolith and move to a distributed architecture when you need to because of team size or to get better separation of concerns.
•	Other disruptive trends include “serverless architecture” like AWS Lambda, and open source itself which is perhaps the true definition of disruptive.
More on this
•	You can access our in-depth coverage on microservices http://bit.ly/1SRnFz3.
•	You can also subscribe to our newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq
•	Attend Adrian Cockcroft 's session at QCon New York 2016, Jun 13-17. http://bit.ly/1TvzlDQ 


Show Notes

Adrian Cockcroft on Microservices, Terraservices and Serverless Computing

In this week's podcast QCon chair Wesley Reisz talks to Matt Ranney who is the Chief Systems Architect at Uber, where he's helping build and scale everything he can. 

Why listen to this podcast:

 - Expanding a company and team at this rate is genuinely hard. Lots of mistakes have been made along the way.
 - Microservices allow companies to grow rapidly but have a cost in terms of aggregate velocity.
 - Uber is gradually moving its marketplace development from Node.js to Go and Java. Java is used for the map services.
 - Aggressive failure testing is used extensively in Uber.
 - Some early design choices - like using JSON over HTTP - make formal verification basically impossible.

Notes and links can be found on InfoQ: http://bit.ly/1TH8app

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq

Attend Matt Ranney's session at QCon New York 2016, Jun 13-17: http://bit.ly/1TH75ht

Uber's Chief Systems Architect on their Architecture and Rapid Growth

In this episode of The New Stack at Scale embedded below, we explore how HyperDev is lowering the barriers to building scalable applications, why Rocana prioritizes showing enterprises how to build a better infrastructure, balancing agility across distributed teams, and how today’s developers and operations teams are using agile practices to meet the needs of today’s high-scale applications. The New Stack Founder Alex Williams and co-host New Relic Editor-in-Chief Fredric Paul sat down with Rocana CTO Eric Sammer and HyperDev Lead at Fog Creek software Daniel X. Moore for an in-depth discussion on these topics and more.

Show 11: Implementing Best Practices for Agility at Scale

Support the show, consider donating: 1JqE3eCwn7PeFNZUq6U2LExwxFqGBS9eqM (http://bit.ly/2gl9HIP)

In their relatively short lifespan, blockchain technologies have already undergone significant milestones. Bitcoin’s blockchain, often referred to as Blockchain 1.0, features a simple database ledger that records transactions in a chronological order and represents the state of the network to participants. Ethereum, or Blockchain 2.0, introduced the notion of smart contracts. Microsoft’s Bletchley Project introduces a new modular architecture which might mark a new milestone for blockchain technologies.

Marley Gray, Principal Program Manager Blockchain at Microsoft, joins us to talk about Microsoft’s approach to blockchain architecture. With enterprise in mind, Bletchley introduces the concept of “Cryptlets”, the core building blocks for introducing a secure middleware tier into blockchain application infrastructure. These computational units, running off-chain, on secure trusted container enclave hardware, could provide trusted data to on-chain smart contract logic.

Topics discussed in this episode:
- Marley’s background and experience at Microsoft
- Why Microsoft is aggressively pursuing blockchain technologies (compared to other large tech companies like Amazon, Google, Facebook, etc)
- Microsoft’s Azure Blockchain-as-a-Service offering
- Project Bletchley, its goals and the problems it is trying to address
- The primary use cases in which Bletchley may provide value
- How Bletchley addresses the issue of deploying consortium style blockchains
- What are Cryptlets and how do they relate to Bletchley
- How Cryptlets are different from Oracles
- How Cryptlets could provide data to Ethereum-style smart contracts

Links mentioned in this episode: 
- Bletchley Whitepaper: https://github.com/Azure/azure-blockchain-projects/blob/master/bletchley/bletchley-whitepaper.md
- Blockchain as a Service (BaaS) | Microsoft Azure: https://azure.microsoft.com/en-us/solutions/blockchain/

Sponsors: 
- Jaxx: Wallets that Unify the Blockchain Experience Across Devices - http://jaxx.io

This episode is also available on :
- Epicenter.tv: https://epicenter.tv/161
- YouTube: http://youtu.be/avAouD1UHH4
- Souncloud: http://soundcloud.com/epicenterbitcoin/eb-161

Watch or listen, Epicenter is available wherever you get your podcasts.

Epicenter is hosted by Brian Fabian Crain, Sébastien Couture & Meher Roy.

161 – Marley Gray: Project Bletchley - Microsoft's Blockchain 3.0 Architecture

In this week’s podcast, Thomas Betts talks with Chris Richardson, a developer, architect, Java Champion and author of POJOs in Action. Before his workshop on Microservices w/ Spring Boot and Docker at QCon San Francisco 2016, Richardson took time to discuss his ideas on how to use DDD and CQRS concepts as a guide for implementing a robust microservices architecture.

Why listen to this podcast:

 - "Microservice architecture" is a better term than "microservices".   The latter suggests that a single microservice is somehow interesting
 - The concepts discussed in Domain-Driven Design are an excellent guide for how to implement a microservices architecture
 - Bounded Contexts correspond well to individual microservices
 - Event sourcing and CQRS provide patterns for how to implement loosely coupled services
 - When converting a monolith to microservices, avoid a big bang rewrite, in favor of an iterative approach

Notes and links can be found on: http://bit.ly/2hZ8TM1

11m:51s - Microservices must be loosely coupled, usually creating a model with one database per service.
12m:45s - There is a business requirement to maintain data consistency across services, and using an event driven architecture is a good way to achieve that.
13m:38s - Event sourcing is specific technique for persisting domain objects as a series of events.
14m:11s - Just as transactions don’t like to be split across microservices, queries cannot simply join across multiple data sources. CQRS provides a solution that accommodates querying via microservices and materialized views.

More on this:
Quick scan our curated show notes on InfoQ. http://bit.ly/2hZ8TM1

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

InfoQ Podcast

Chris Richardson on Domain-Driven Microservices Design

Jonas Bonér, CTO of LightBend and creator Akka, discusses using Akka when developing distributed systems. He talks about the Actor Model, and how every Microservice needs to be viewed as a system to be successful. 

Why listen to this podcast:

 - Akka is JVM-based framework design for developing distributed systems leveraging the Actor Model - an approach for writing concurrent systems that treat actors as universal primitives and the most successful model with abstraction has been streaming
 - Circuit breakers in Akka are a backup and retry policy; they protect you by capturing failure data and allow you to roll back 
 - Every Microservice needs to be viewed as a system, it needs to have multiple parts that run on different machines in order to function and be fully resilient - thus is a Microsystem
 - Two different trends have emerged when it comes to hardware and environments: one is the trend toward Multi-core, the is a movement toward virtualized environments and the cloud
 - Saga pattern of managing long running transactions in a distributed system fits very well with messaging style architectures

Notes and links can be found on: http://bit.ly/2kwB2eB

Akka
The Actor Model
When Akka and the Actor Model is the perfect choice
Circuit breakers patterns in distributed systems
Two trends toward Multi-core
Reactive Manifesto
Event Driven vs. Message Driven
Reactive Programming and Streams
Microliths to Microsystems
What do you have to get right before you start trying to deploy a distributed systems?
Working with ML / AI at Lightbend to understand tracing through distributed system
Saga Pattern

More on this:
Quick scan our curated show notes on InfoQ http://bit.ly/2kwB2eB

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Jonas Bonér on the Actor Model, Akka, Reactive Programming, Microservices and Distributed Systems

In this interview NGINX's Chris Stetson describes some of the biggest pain points associated with microservices development and describes the various patterns and models - including the Circuit Breaker Pattern - covered in his new book, "Microservices Reference Architecture."  Chris also talks about the fundamental differences between microservices and SOA and how NGINX has extended the 12-Factor App to encompass microservices.  

Chris Stetson, Chief Architect of Microservices Engineering at NGINX, has architected applications for twenty years, including the first versions of Sirius Satellite Radio, Visa.com, Intel.com, Microsoft.com, and Lexus.com. He has built large monolithic systems, service-oriented architecture (SOA) applications, and most recently microservice-based systems. Most recently, Chris has authored The Microservices Reference Architecture eBook, a practical guide that helps solve many of the challenges of building microservices-based applications.

Chris Stetson on the Microservices Reference Architecture

Wesley Reisz talks to Daniel Bryant on moving from monoliths to micro-services, covering bounded contexts, when to break up micro-services, event storming, practices like observability and tracing, and more.

Why listen to this podcast:

- Migrating a monolith to micro-services is best done by breaking off a valuable but not critical part first.
 - Designing a greenfield application as micro-services requires a strong understanding of the domain.
 - When a request enters the system, it needs to be tagged with a correlation id that flows down to all fan-out service requests.
 - Observability and metrics are essential parts to include when moving micro-services to production.
 - A service mesh allows you to scale services and permit binary transports without losing observability.

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2pFYBiT

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2pFYBiT

Daniel Bryant on Microservices and Domain Driven Design

Wesley Reisz talks to Sid Anand, a data architect at cybersecurity company Agari, about building cloud-native data pipelines. The focus of their discussion is around a solution Agari uses that is built from Amazon Kinesis Streams, serverless functions, and auto scaling groups.

Sid Anand is an architect at Agari, and a former technical architect at eBay, Netflix, and LinkedIn.  He has 15 years of data infrastructure experience at scale, is a PMC for Apache Airflow, and is also a program committee chair for QCon San Francisco and QCon London.

Why listen to this podcast

 - Real-time data pipeline processing is very latency sensitive
 - Micro-batching allows much smaller amounts of data to be processed
 - Use the appropriate data store (or stores) to support the use of the dataIngesting data quickly into a clean database with minimal indexes can be fast
 - Communicate using a messaging system that supports schema evolution

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2rJU9nB

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2rJU9nB

Sid Anand on Building Agari’s Cloud-native Data Pipelines with AWS Kinesis and Serverless

This week Devin Hedge joins Dave Prior for another student question. This time about architecture and if the complexity of it would be better served by a waterfall approach:

The Question:

"How to plan for the Architecture effectively. With waterfall, we try to figure out all aspects of the business and the technical solution in advance before we start development. In Agile, we discover as we go. It's very likely that when we come to a certain, we'll find either the current business logic or the current technical framework cannot adapt our upcoming demands. There's a high opportunity that we'll need to destroy all the work that we've done. Talking in this perspective, isn't waterfall better than Agile?"

Show Notes

00:08 Interview Begins
00:51 This week’s question
02:00 What do we mean by architecture
02:29 The design principles and standards you need in place to support your work
03:35 If it isn’t loosely coupled, neither waterfall or agile can really help
04:17 Challenging the assumption that big up front planning could help you eliminate the risk of having to do rework and whether or not waterfall is actually supposed to do that
07:43 If we can’t eliminate the risk of not knowing everything up front, what can you do?
08:30 Devin puts on his architect hat - guardrails and guideposts
09:53 Reframing the problem 
10:40 How physical building architects are still designing even after the building is built - you never know what the tenants of the building will actually want
11:48 The risk of making decisions too early
12:18 Advice from Devin on how to reduce your risk of designing architecture up front and put up the guardrails and guideposts you need
14:14 How architects look at the work and decision making
17:02 Making decisions at the last possible responsible moment
17:43 Having a growth mindset vs. a fixed mindset
19:10 Is there value in waiting to make your decisions until you have all the information? What is your cost of delay of waiting to make the decisions?
20:57 Devin’s upcoming events: Agile Budgeting and Cost Tracking for the PMI North Carolina Chapter on July 11 and PMI South Carolina on July 20
21:57 How to get in touch with Devin
22:47 Interview Ends

Links from the podcast


Does Agile addresses the 25 point Federal IT Reformation plan? (June 29)
PMI Washington DC 
http://conta.cc/2sov4vn

Agile: Budgeting for Agile Financial cost planning/tracking (July 11)
PMI North Carolina
http://bit.ly/2tmVMZz

Jeff Bezos Memo about Cloud Services 
http://apievangelist.com/2012/01/12/the-secret-to-amazons-success-internal-apis/


Contacting Devin

LeadingAgile: www.leadingagile.com/guides/devin-hedge/
Twitter: twitter.com/agiledevin
LinkedIn: www.linkedin.com/in/devinhedge

Contacting Dave

LeadingAgile: www.leadingagile.com/guides/dave-prior/
Email: dave.prior@leadingagile.com
Twitter: twitter.com/mrsungo
Personal Blog: drunkenpm.net

LeadingAgile CSM & CSPO Classes

For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

Feedback/Questions

If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com

Student Q&A: Dealing with Architecture in Agile w/ Devin Hedge

Wesley Reisz talks with Sam Newman about microservices.  They explore the current state of the art with regards the architectural style and corresponding tooling and deployment platforms. They then discuss how microservices increase the surface area of where sensitive information can be read or manipulated, but also have the potential to create systems that are more secure.

Why listen to this podcast:

 - Different organisations have different risk appetites for new technology, so what may be appropriate for one organisation may not be appropriate technology choices for another. 
 - If you are deploying micro services then you need to know why you are doing it and what benefits you expect to get from deploying them.
 - Micro services are defined by their independently deployable units rather than their size. 
 - Using a cryptographic token that is verifiable off line is a common pattern for passing authentication contexts around to different services.
 - Serverless architectures redeuce the need to monitor server patching but does not diminish the need for monitoring application runtime or library dependencies from security patching.

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2v8NJg6

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2v8NJg6

Security Considerations and the State of Microservices with Sam Newman

This week's podcast features Simon Brown well known for his work training software architects. Topics include the differences between a tech lead and an architect, how much documentation is enough and what that looks like in a continuous delivery environment.

What you'll learn on this podcast:
•	As an industry we seem to have lost our knowledge of how to do architecture well in the context of modern agile software teams.
•	Architecture is about the expensive decisions; things that are costly to change later.
•	Ideally architects should code in the production code base. If you are not able to do this at least be involved in quality reviews and peer reviews in the production code so you can get feedback on your designs.
•	It is often said the the code is the only documentation you need but the code can’t tell you everything. You do need to document the things you can’t get from the code such as the architectural drivers, they key quality attributes and so on along with some high level diagrams and how you operate the system.
•	As you step into the role of architect go and find a mentor or a local meet-up. The major change is that you have to influence and lead people.

This podcast is sponsored by AppDynamics. Software architects play a critical role in designi¬¬¬ng, executing, and migrating large infrastructures to the cloud. Download AppDynamic’s FREE eBook “10 Tips for Enterprise Cloud Migration” and launch your migration project with a proven plan. Download the eBook now at http://infoq.link/web_sndcld_appdynamics 


Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2xvq7qM

Show notes

Simon Brown on the Role of the Software Architect in a Continuous Delivery Environment

Today, companies are on a journey to modernize their infrastructures and meet the changing demands of businesses. The cloud is becoming a strategic part of this initiative due to its potential to unlock cost savings and increase agility. However, the cloud also brings a new set of migration and data protection challenges.

In this episode, Michael Fal (Rubrik), David Klee (Heraflux Technologies), and John Morehouse (Denny Cherry & Associates) explore the database landscape in the cloud era and share protection best practices.

AWS

Onur Deler