The InfoQ Podcast

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

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