Podcast Overview
InfoQ.com is a trusted source of information for over 1, 500, 000 software developers worldwide. Over the last 10 years we have covered all the hottest topics from the industry, in early stages, to make sure that we fulfill our mission to drive innovation in professional software development. On top of news, articles, presentations and minibooks we’ve recently started this podcast series dedicated to software engineers. We’ve interviewed some of the top CTOs, engineers and technology directors from the people behind InfoQ.com and QCon.
Podcast Episodes
Pony Language Designer Sylvan Clebsch on Pony’s Design, Garbage Collection, and Formal Verification
In this podcast Charles Humble talks to Sylvan Clebsch, who is the designer of the actor-model language Pony programming and now works at Microsoft Research in Cambridge in the Programming Language Principles group. They talk about the inspirations behind Pony, how the garbage collector avoids stop-the-world pauses, the queuing systems, work scheduler, and formal verification. Why listen to this podcast:* Pony scales from a Raspberry Pi through a 64 core half terabyte machine to a 4096 core SGI beast* An actor has a 256-byte overhead, so creating hundreds of thousands of actors is possible* Actors have unbounded queues to prevent deadlock* Each actor garbage collects its own heap, so global stop-the-world pauses are not needed* Because the type system is data-race free, it’s impossible to have concurrency problems in PonyMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2tZXcKEYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2tZXcKE
Download Episode
Kotlin Lead Language Designer Andrey Breslav on Android Support, Language Features and Future Plans
Why listen to this podcast:- Kotlin is an officially supported language on Google Android platforms - Kotlin Native and Kotlin JS will allow code reuse between server, client and mobile devices - Type safety means that references can be checked for nullability Great tooling is a driver in what kind of language features are (and aren’t) adopted - Coroutines provide a way of creating maintainable asynchronous systemsMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2sHyxqQYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2sHyxqQ
Download Episode
Sid Anand on Building Agari’s Cloud-native Data Pipelines with AWS Kinesis and Serverless
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 evolutionMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2rJU9nBYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2rJU9nB
Download Episode
Sachin Kulkarni Describes the Architecture Behind Facebook Live
Wesley Reisz talks to Sachin Kulkarni, Director of Engineering at Facebook, about the engineering challenges for Facebook live, and how it compares to the video upload platform at Facebook.Why listen to this podcast: - Facebook Infrastructure powers the board family of apps including the Facebook app, Messenger and Instagram. It is largely a C++ shop. There is some Java and Python, and the business logic is all done in PHP. The iOS apps are written in Objective C and the Android apps are in Java. - The video infra team at Facebook builds the video infrastructure across the whole company. Projects include a distributed video encoding platform which results in low latency video encoding, video upload and ingest. - Facebook Live does encoding on both the client and the server. The trade-off between encoding on the client side and the server side is mostly around the quality of the video vs. latency and reliability. - Facebook gets around 10x speed-up by encoding data in parallel compared to serial. - They also have an AI-based encoding system which resulted in 20% smaller files than raw H.264.You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2qrseG5You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2qrseG5Want more? Read InfoQ: http://bit.ly/2dcHmpu
Download Episode
Martijn Verburg on the JCP EC “No” Vote for the Java Modules
Wesley Reisz talks to Martijn Verburg, co-founder of the London Java Community and CEO of jClarity, about the JCP EC “no” vote on the Java Platform Module System (JPMS), which is due to be shipped as part of Java 9. The talk about what JPMS offers, how it works, what the no vote means and what happens next.Why listen to this podcast:- Jigsaw isn’t dead- The “no” vote was based on the submission being a bit early, and without expert group consensus that it should be submitted- Since the vote started, several amendments have been made which addressed some of the concerns listed by those who voted “no”- Daily calls with the expert group and interested parties will work to resolve the outstanding issues promptly- A resubmission is due within 30 days with a future vote expected to go throughMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2q20escYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extended shownotes? Check the landing page on InfoQ: http://bit.ly/2q20esc
Download Episode
Daniel Bryant on Microservices and Domain Driven Design
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/2pFYBiTYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2pFYBiT
Download Episode
Rossen Stoyanchev on Reactive Programming with Spring 5 and Spring WebFlux
Rossen Stoyanchev talks to Wesley Reisz about blocking and non-blocking architectures, upcoming changes in Spring including Spring WebFlux, the reactive web stack in Spring framework 5, due this summer. He also discusses the differences between rxJava and Reactor.Why listen to this podcast: - Spring Framework 5 is due to be released June 25 2017 - Spring Web Flux provides a web programming model designed for asynchronous APIs - Back-pressure is important in a server environment; less so within a UI environment - It’s possible to use a Spring Web Flux client within a Spring MVC applciation - Managing sets of thread pools is more complicated than having a scalable asynchronous systemMore on this: Quick scan our curated show notes on InfoQ http://bit.ly/2pPgq0GYou can subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2pPgq0G
Download Episode
Richard Feldman Discusses Elm and How It Compares to React.js for Front-end Programming
Why listen to this podcast: - Using a compiler to catch errors at compile time instead of at runtime means much easier refactoring of code. - Incrementally replacing small parts of an existing JavaScript application with Elm is a safer strategy than trying to write an entirely new application in Elm - Elm packages are semantically versioned and gated by the publishing process, so minor versions cannot remove functionality without bumping the major version. - The UI in an Elm application results in messages that transform the immutable state of the application; this allows a debugger to view the state transitions and the messages that triggered them, including record and replay of those messages. - Elm has been benchmarked as being faster than Angular and React whilst being smaller code, which is attributed to the immutable state and pure functional elements.More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2qmS2CTYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVqSubscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2qmS2CT
Download Episode
Jean Barmash on Inter-Service RPC with gRPC/Thrift, Designing Public APIs, & Lean/Constraint Theory
Jean Barmash is Director of Engineering at Compass, Founder & Co-Organizer, NYC CTO School Meetup. Live in New York City. He has over 15 years of experience in software industry, and has been part of 4 startups over the last seven years, 3 as CTO / VPE and one of which he co-founded. Prior to his entrepreneurial adventures, Jean held a variety of progressively senior roles in development, integration consulting, training, and team leadership. He worked for such companies as Trilogy, Symantec, Infusion and Alfresco, consulting to Fortune 100 companies like Ford, Toyota, Microsoft, Adobe, IHG, Citi, BofA, NBC, and Booz Allen Hamilton.Jean will speak at QCon New York 2017: http://bit.ly/2nN7KKoWhy listen to this podcast:- The Compass backend is mostly written in Java and Python, with Go increasingly a first class language. The main reason for Go being added was developer productivity. - The app is based on a Microservices architecture with around 40-50 services in total. - Binary RPC, originally Thrift and Finagle, is used as the communication protocol, but the company is gradually moving to gRPC still with Thrift. One advantage that gRPC offers is better Python support than Finagle. - The company has built a code generation framework which takes Thrift and converts it to a RESTful API for clients to consume. - Constraint theory is about how you manage the one constraint in a system or team that prevent you increasing throughput; for example if your software engineering team only has one front end engineer do you ask back-end engineers to pick off some front-end tasks, or bring in a contractor.Subscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq
Download Episode
Eric Horesnyi on High Frequency Trading and how Hedge Funds are Applying Deep Learning to Markets
Eric Horesnyi, CEO @streamdata.io, talks to Charles Humble about how hedge funds are applying deep learning as an alternative to the raw speed favoured by HFT to try and curve the market.Why listen to this podcast: - Streamdata.io was originally built for banks and brokers, but more recently hedge funds have begun using the service. - Whilst Hedge Funds like Renaissance Technologies have been using mathematical approaches for some time deep learning is now being applied to markets. Common techniques such as gradient descent and back propagation apply equally well to market analysis.- The data sources used are very broad. As well as market data the network might be using, sentiment analysis from social networks, social trading data, as well as more unusual data such as retail data, and IoT sensors from farms and factories. - By way of contrast High Frequency Trading focusses on latency. From an infrastructure stand-point you can play with propagation time, Serilization (the thickness of the pipe), and Processing time for any active component in chain. - One current battleground in HFT is around using FPGA to build circuits dedicated to feed handlers. Companies such as Novasparks are specialists in this area.More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2nv71M8Subscribe: www.youtube.com/infoqLike InfoQ on Facebook: bit.ly/2jmlyG8Follow on Twitter: twitter.com/InfoQFollow on LinkedIn: www.linkedin.com/company/infoqWant to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2nv71M8You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq
Download Episode