infoq

Summary: In this week's podcast QCon chair Wesley Reisz talks to Mads Torgersen who leads the C# language design process at Microsoft, where he has been involved in five versions of C#, and also contributed to TypeScript, Visual Basic, Roslyn and LINQ. Before he joined Microsoft a decade ago, he worked as a university professor in Aarhus, Denmark, doing research into programming language design and contributing to Java generics.
Why listen to this podcast
•	The overall theme for C# 7 will be features that make it easier to work with data, including language level support for tuples. 
Roslyn, the compiler and API, allows a much more agile evolution of the language.
•	The Omnisharp initiative aims to facilitate easier editing of C# code in other editors, including VS Code.
•	IoT and Artificial Intelligence are emerging as key disruptive trends.
•	The release may also include pattern matching for type switching.
•	C# 7 is the first new release of the language to be completely built in the open.

More on this
•	You can access our whole coverage on C#7 http://bit.ly/1ZlM4NI or have an overview on what's new on C# in general http://bit.ly/1rx6SGM.
•	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 Mads Torgersen's session at QCon New York 2016, Jun 13-17. http://bit.ly/1YcBgAY


Show Notes

Mads Torgersen on C# 7 and Beyond

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.

In this podcast, Shane Hastie, InfoQ Lead Editor for Culture & Methods, talks to Kent McDonald, Steve Adolph and Ryland Leyton about the state of business analysis and product management in agile product development. They were participants in a weekend workshop where the Agile Alliance and the International Institute of Business Analysis were collaborating to produce a revised version of the Agile Extension to the Business Analysis Body of Knowledge.

Why listen to this podcast:

- Analysis skills are necessary for successful product development
- We don’t question and challenge the rationale and strategic alignment of projects enough, which results in lots of waste from doing the wrong projects or building the wrong features in a project
- The best return on investment that you can get is to stop wasting your money
- Value is hard to define but crucial to identify; the definition of value will be different in every context
- Agile methods provide for learning and rapid feedback, which enables us to optimize value and ensure strategic alignment in product development
- User stories are conversation placeholders, not orders to be fulfilled

Notes and links can be found on InfoQ: bit.ly/2e32o5X

- 6m 20s Analysis skills reside in many different roles and doing analysis in agile development is far less prescriptive that has been the case.

- 6m 44s You need to have a very comprehensive toolkit and have the ability to relate the tool needed to the context of the work being done.

- 9m 13s Advanced organisations are changing when they utilise analysis skills to determine which initiatives should be worked on and how they align with organisation strategy; being able to review these decisions even after an initiative has started, stopping development work when it is no longer valuable.

More on this:

Quick scan our curated show notes on InfoQ. bit.ly/2e32o5X

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

InfoQ Podcast

Business Analysis & Product Management in Agile

In this interview, Anil Gaur, Group Vice President of Engineering at Oracle, sheds some light on Oracle’s Java EE strategy and roadmap.  He describes how the platform will evolve to support the cloud and companies wanting to move to the cloud, comments on the future of the Microprofile.IO, and explains why Java EE 8 is being delayed until the end of 2017.  Anil also provides his perspective on one of the popular choices for Java-based development on the cloud today - Spring Boot and Cloud Foundry - and what developers can expect from Java EE in the future.  

Anil is Group Vice President of Engineering at Oracle. Prior to joining Oracle, Anil led the global team that produced key middleware technologies at Sun Microsystems including the Java EE platform, GlassFish Server, and Java Message Queue. Anil has played an instrumental role in open-sourcing the Java EE platform through the GlassFish community. He has also led the integration of MySQL with Sun's middleware product portfolio.

The Future of Java EE and Java on the Cloud

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.

In this podcast, Shane Hastie, InfoQ Lead Editor for Culture & Methods, talks to Melissa Perri, a UX and Product Management expert and founder of Produx Labs.

Why listen to this podcast:

 - Put value first – it’s not about building more stuff but making sure we build the right thing for the right people
 - Product ownership is about optimising value for the organisation
 - Managers need to understand their role in product management
 - Identify outcomes and define pirate metrics for success
 - Empower teams to achieve the outcomes, not deliver features

Notes and links can be found on InfoQ: http://bit.ly/melissa-perri

3m:45s Management should communicate the metrics and goals to the product owner and let them work with the delivery team(s) to figure out how to achieve them

4m:20s Product owners told to make decisions but not actually empowered to do so

4m:35s Focus on training the managers on what they need to do to effectively support product ownership and how to communicate clear boundaries and goals

5m:20s A product strategy is not a plan

5m:55s Common approach is for managers to define the features and roadmap instead of identifying and communicating the goals, and trust the teams to figure out the best way to achieve the goals

Quick scan our curated show notes on InfoQ: http://bit.ly/melissa-perri

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

Melissa Perri on what's needed for Effective Product Management

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

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

infoq

User 507723872