TeecStudy

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 Keith Adams, chief architect at Slack. Prior he was an engineer at Facebook where he worked on the search type live backend, and is well-known for the HipHop VM [hhvm.com]. Adams presented How Slack Works at QCon SanFrancisco 2016.

Why listen to this podcast:

 - Group messaging succeeds when it feels like a place for members to gather, rather than just a tool
 - Having opt-in group membership scales better than having to define a group on the fly, like a mailing list instead of individually adding people to a mail
 - Choosing availability over consistency is sometimes the right choice for particular use cases
 - Consistency can be recovered after the fact with custom conflict resolution tools
 - Latency is important and can be solved by having proxies or edge applications closer to the user

Notes and links can be found on: http://bit.ly/keith-adams

3m:30s Voice and video interactions are impacted by latency; the same is true of messaging clients
4m:00s The user interface can provide indications of presence, through avatars indicating availability and typing indicators
4m:15s Latency is important; sometimes the difference is between 100ms and 200ms so the message channel monitors ping timeout between server and client
4m:40s 99th percentile is less than 100ms ping time
5m:15s If the 99th percentile is more than 100ms then it may be server based, such as needing to tune the Java GC
5m:25s Network conditions of the mobile clients are highly variable&nbsp;
6m:20s Mobile clients can suffer intermittent connectivity

More on this:
Quick scan our curated show notes on InfoQ. http://bit.ly/keith-adams

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

Keith Adams on the Architecture of Slack, using MySql, Edge Caching, & the backend Messaging Server

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

Chris Richardson on Domain-Driven Microservices Design

In this week’s podcast, Robert Blumen talks to Oliver Gould at QCon San Francsico 2016. Oliver is the CTO of Buoyant where he leads open source development efforts. Prior to Buoyant he was a Staff Infrastructure Engineer at Twitter where he was technical lead on Observability, Traffic, Configuration and Co-ordination teams.

Why listen to this podcast:

 - Stratification allows applications to own their logic while libraries take care of the different mechanisms, such as service discovery and load balancing
 - Cascading failures can’t be tested or protected against, so having a fast time to recovery is important
 - Having developers own their services with on-call mechanisms improves the reliability of the service; it’s best to optimise automatic restarts so problems can be addressed during normal working hours
 - Post mortem analysis of failures are important to improve run books or checklists and to share learning between teams
 - Incremental roll out of features with feature flags or weighted routing provides agility while testing with production load, which highlights issues that aren’t seen during limited developer testing

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

4m:05s - Each domain has different failure and operating modes, and the layered approach to resiliency means that the layer handles this automatically
4m:30s - Large systems may fail in unexpected ways
4m:35s - Twitter originally had the “Fail Whale” but this has been phased out as the system has become more stable
4m:50s - As Twitter grew, it needed to move quicker, with more engineers and less whale time
5m:10s - Automation and social tools were needed to improve the situation

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

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

Oliver Gould About Architecting to Avoid and Recover from Failure

Liam Crilly, Director of Product Management at NGINX, talks about the impact microservices is having on API gateways and how a CI/CD pipeline should interface with API gateways.  He describes how API gateways help with messaging and event-driven architectures, how they integrate with IoT devices and real-time streaming, and shares some API trends he expects to see in 2020.

Liam Crilly on the Future of API Gateways

Software is changing the world and we think our mission is to help progressive software-development teams adopt new technologies and practices. We do this by providing our audience with unbiased, practitioner-driven conferences, content, and an online community.

Liam Crilly on the Future of API Gateways

InfoQ Industry Solutions Podcast