Lily Mara

In today's episode Thomas Betts talks to Lily Mara, Engineering Manager at OneSignal in San Mateo, California. She manages the infrastructure services team, which is responsible for in-house services used by other OneSignal engineering teams. They will discuss how to build a reliable Kafka data processing pipeline.Read a transcript of this interview: https://bit.ly/3ONTM63Subscribe to the Software Architects’ Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnlUpcoming Events:QCon San Franciscohttps://qconsf.com/ Oct 2-6, 2023QCon Londonhttps://qconlondon.com/ April 8-10, 2024Follow InfoQ:- Mastodon: https://techhub.social/@infoq- Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

In today's episode Thomas Betts talks to Lily Mara, Engineering Manager at OneSignal in San Mateo, California. She manages the infrastructure services team, which is responsible for in-house services used by other OneSignal engineering teams. They will discuss how to build a reliable Kafka data processing pipeline. Read a transcript of this interview: <a href="https://bit.ly/3ONTM63" rel="nofollow" target="_blank">https://bit.ly/3ONTM63</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="http://www.infoq.com/software-architect…mpaign=architectnl" rel="nofollow" target="_blank">www.infoq.com/software-architect…mpaign=architectnl</a> Upcoming Events: QCon San Francisco <a href="https://qconsf.com/" rel="nofollow" target="_blank">https://qconsf.com/</a> Oct 2-6, 2023 QCon London <a href="https://qconlondon.com/" rel="nofollow" target="_blank">https://qconlondon.com/</a> April 8-10, 2024 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="http://www.infoq.com/write-for-infoq/?u…aign=writeforinfoq" rel="nofollow" target="_blank">www.infoq.com/write-for-infoq/?u…aign=writeforinfoq</a>

Building a Reliable Kafka Data Processing Pipeline With Lily Mara

In this episode of the podcast, members of the InfoQ editorial staff and friends of InfoQ will be discussing the current trends in the domain of cloud and DevOps as part of the process of creating our annual trends report. These reports provide InfoQ readers with a high-level overview of the topics to pay attention to and also help the editorial team focus on innovative technologies. In addition to the report and the trends graph available on InfoQ.com, this podcast is a chance to hear our raw conversation and the stories our expert practitioners shared.Read a transcript of this interview: https://bit.ly/3XHM6FnSubscribe to the Software Architects’ Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnlUpcoming Events:QCon San Francisco:qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23Oct 2-6, 2023Follow InfoQ:- Mastodon: https://techhub.social/@infoq- Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

In this episode of the podcast, members of the InfoQ editorial staff and friends of InfoQ will be discussing the current trends in the domain of cloud and DevOps as part of the process of creating our annual trends report. These reports provide InfoQ readers with a high-level overview of the topics to pay attention to and also help the editorial team focus on innovative technologies. In addition to the report and the trends graph available on <a href="http://InfoQ.com" rel="nofollow" target="_blank">InfoQ.com</a>, this podcast is a chance to hear our raw conversation and the stories our expert practitioners shared. Read a transcript of this interview: <a href="https://bit.ly/3XHM6Fn" rel="nofollow" target="_blank">https://bit.ly/3XHM6Fn</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="http://www.infoq.com/software-architect…mpaign=architectnl" rel="nofollow" target="_blank">www.infoq.com/software-architect…mpaign=architectnl</a> Upcoming Events: QCon San Francisco: <a href="http://qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="http://www.infoq.com/write-for-infoq/?u…aign=writeforinfoq" rel="nofollow" target="_blank">www.infoq.com/write-for-infoq/?u…aign=writeforinfoq</a>

InfoQ Cloud and DevOps Trends 2023

Ben Dart

Live from the venue of the International Conference on Robotics and Automation (ICRA), we are talking with Ben Dart about the trends in robotics. In this podcast, Ben and Roland discuss the latest robotics technology as showcased at ICRA, and discuss where this technology is on the hype cycle. They also discuss how to get started with robotics yourself.Read a transcript of this interview: bit.ly/3XGQAMhSubscribe to the Software Architects’ Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnlUpcoming Events:QCon San Francisco:qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23Oct 2-6, 2023Follow InfoQ:- Mastodon: https://techhub.social/@infoq- Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

Live from the venue of the International Conference on Robotics and Automation (ICRA), we are talking with Ben Dart about the trends in robotics. In this podcast, Ben and Roland discuss the latest robotics technology as showcased at ICRA, and discuss where this technology is on the hype cycle. They also discuss how to get started with robotics yourself. Read a transcript of this interview: <a href="http://bit.ly/3XGQAMh" rel="nofollow" target="_blank">bit.ly/3XGQAMh</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="http://www.infoq.com/software-architect…mpaign=architectnl" rel="nofollow" target="_blank">www.infoq.com/software-architect…mpaign=architectnl</a> Upcoming Events: QCon San Francisco: <a href="http://qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="http://www.infoq.com/write-for-infoq/?u…aign=writeforinfoq" rel="nofollow" target="_blank">www.infoq.com/write-for-infoq/?u…aign=writeforinfoq</a>

Ben Dart on 2023 Trends in Robotics at ICRA

Rebecca Parsons

In Evolutionary Architectures, the book she co-authored, Dr. Rebecca Parsons described the principles and practices that allow architecture to evolve. In this episode of the podcast, we talk about those principles, how they’ve changed between the first and second editions of the book, and what changes we might see in the next few years.Read a transcript of this interview: https://bit.ly/3IUg5U6Subscribe to the Software Architects’ Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnlUpcoming Events:QCon New Yorkqconnewyork.com/?utm_source=sound…tm_campaign=qny23June 13-15, 2023QCon San Francisco:qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23Oct 2-6, 2023Follow InfoQ:- Mastodon: techhub.social/@infoq- Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

In Evolutionary Architectures, the book she co-authored, Dr. Rebecca Parsons described the principles and practices that allow architecture to evolve. In this episode of the podcast, we talk about those principles, how they’ve changed between the first and second editions of the book, and what changes we might see in the next few years. Read a transcript of this interview: <a href="https://bit.ly/3IUg5U6" rel="nofollow" target="_blank">https://bit.ly/3IUg5U6</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="http://www.infoq.com/software-architect…mpaign=architectnl" rel="nofollow" target="_blank">www.infoq.com/software-architect…mpaign=architectnl</a> Upcoming Events: QCon New York <a href="http://qconnewyork.com/?utm_source=sound…tm_campaign=qny23" rel="nofollow" target="_blank">qconnewyork.com/?utm_source=sound…tm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="http://qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="http://www.infoq.com/write-for-infoq/?u…aign=writeforinfoq" rel="nofollow" target="_blank">www.infoq.com/write-for-infoq/?u…aign=writeforinfoq</a>

The Evolution of Evolutionary Architecture with Rebecca Parsons

Live from the venue of the QCon London Conference, we are talking with Mehrnoosh Sameki. In this podcast, Mehrnoosh discusses the importance of responsible AI, the principles behind it, and the challenges in ensuring fairness and transparency in AI systems. She also highlights various open-source tools and approaches for developers to incorporate responsible AI practices into their machine learning models and ensure better decision-making and ethical outcomes.Read a transcript of this interview: https://bit.ly/3BzWtASSubscribe to the Software Architects’ Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnlUpcoming Events:QCon New Yorkqconnewyork.com/?utm_source=sound…tm_campaign=qny23June 13-15, 2023QCon San Francisco:qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23Oct 2-6, 2023Follow InfoQ:- Mastodon: techhub.social/@infoq- Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

Live from the venue of the QCon London Conference, we are talking with Mehrnoosh Sameki. In this podcast, Mehrnoosh discusses the importance of responsible AI, the principles behind it, and the challenges in ensuring fairness and transparency in AI systems. She also highlights various open-source tools and approaches for developers to incorporate responsible AI practices into their machine learning models and ensure better decision-making and ethical outcomes. Read a transcript of this interview: <a href="https://bit.ly/3BzWtAS" rel="nofollow" target="_blank">https://bit.ly/3BzWtAS</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="http://www.infoq.com/software-architect…mpaign=architectnl" rel="nofollow" target="_blank">www.infoq.com/software-architect…mpaign=architectnl</a> Upcoming Events: QCon New York <a href="http://qconnewyork.com/?utm_source=sound…tm_campaign=qny23" rel="nofollow" target="_blank">qconnewyork.com/?utm_source=sound…tm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="http://qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="http://www.infoq.com/write-for-infoq/?u…aign=writeforinfoq" rel="nofollow" target="_blank">www.infoq.com/write-for-infoq/?u…aign=writeforinfoq</a>

Mehrnoosh Sameki on Responsible AI

Rosemary Wang

Commiting to the journey of running in the cloud is quite as simple as moving your code or writing a new application on a cloud offering. Between a diverse service catalog, greater developer autonomy, rapid provisioning, surprise billing, and changing security requirements, you might find that hosting applications on the cloud does not make the most of the cloud.In this episode of the podcast, Rosemary Wang talks about the patterns and practices that help you move from cloud-hosted to cloud-native architecture and maximize the benefit and use of the cloud. The discussion covers essential application and infrastructure considerations, as well as cost and security concerns you need to think about when approaching a cloud-native architecture.Read a transcript of this interview: https://bit.ly/3LQKzY2Subscribe to the Software Architects’ Newsletter [monthly]: www.infoq.com/software-architect…mpaign=architectnlUpcoming Events:QCon New Yorkqconnewyork.com/?utm_source=sound…tm_campaign=qny23June 13-15, 2023QCon San Francisco:qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23Oct 2-6, 2023Follow InfoQ:- Mastodon: techhub.social/@infoq- Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.www.infoq.com/write-for-infoq/?u…aign=writeforinfoq

Commiting to the journey of running in the cloud is quite as simple as moving your code or writing a new application on a cloud offering. Between a diverse service catalog, greater developer autonomy, rapid provisioning, surprise billing, and changing security requirements, you might find that hosting applications on the cloud does not make the most of the cloud. In this episode of the podcast, Rosemary Wang talks about the patterns and practices that help you move from cloud-hosted to cloud-native architecture and maximize the benefit and use of the cloud. The discussion covers essential application and infrastructure considerations, as well as cost and security concerns you need to think about when approaching a cloud-native architecture. Read a transcript of this interview: <a href="https://bit.ly/3LQKzY2" rel="nofollow" target="_blank">https://bit.ly/3LQKzY2</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="http://www.infoq.com/software-architect…mpaign=architectnl" rel="nofollow" target="_blank">www.infoq.com/software-architect…mpaign=architectnl</a> Upcoming Events: QCon New York <a href="http://qconnewyork.com/?utm_source=sound…tm_campaign=qny23" rel="nofollow" target="_blank">qconnewyork.com/?utm_source=sound…tm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="http://qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">qconsf.com/?utm_source=soundcl…&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="http://www.infoq.com/write-for-infoq/?u…aign=writeforinfoq" rel="nofollow" target="_blank">www.infoq.com/write-for-infoq/?u…aign=writeforinfoq</a>

From Cloud-Hosted to Cloud-Native with Rosemary Wang

Hien Luu

Live from the venue of the QCon London Conference, we are talking with Hien Luu, head of ML Platform at DoorDash. In this podcast, Hien discusses the main principles and strategies that DoorDash uses to scale and evolve MLOps, as well as some tips for those who want to get started with MLOps.Read a transcript of this interview:  https://bit.ly/3pkOiFLSubscribe to the Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl Upcoming Events:QCon New Yorkhttps://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23 June 13-15, 2023QCon San Francisco:https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23 Oct 2-6, 2023Follow InfoQ:- Mastodon: https://techhub.social/@infoq - Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq

Live from the venue of the QCon London Conference, we are talking with Hien Luu, head of ML Platform at DoorDash. In this podcast, Hien discusses the main principles and strategies that DoorDash uses to scale and evolve MLOps, as well as some tips for those who want to get started with MLOps. Read a transcript of this interview: <a href="https://bit.ly/3pkOiFL" rel="nofollow" target="_blank">https://bit.ly/3pkOiFL</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl" rel="nofollow" target="_blank">https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl</a> Upcoming Events: QCon New York <a href="https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23" rel="nofollow" target="_blank">https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq" rel="nofollow" target="_blank">https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq</a>

Hien Luu on ML Principles at DoorDash

Leslie Miley

Live from the venue of the QCon London Conference, we are talking with Leslie Miley, a technical advisor to the CTO at Microsoft. In this podcast, Leslie shares his insights on AI bias, sustainability, and the potential impact of AI on society. He emphasizes the importance of understanding and mitigating the harm these technologies can cause, while also discussing the responsibilities of developers, tech companies, and individuals in ensuring a more responsible and ethical approach to AI development.Read a transcript of this interview: https://bit.ly/3LopSlTSubscribe to the Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl Upcoming Events:QCon New Yorkhttps://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23 June 13-15, 2023QCon San Francisco:https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23 Oct 2-6, 2023Follow InfoQ:- Mastodon: https://techhub.social/@infoq - Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq

Live from the venue of the QCon London Conference, we are talking with Leslie Miley, a technical advisor to the CTO at Microsoft. In this podcast, Leslie shares his insights on AI bias, sustainability, and the potential impact of AI on society. He emphasizes the importance of understanding and mitigating the harm these technologies can cause, while also discussing the responsibilities of developers, tech companies, and individuals in ensuring a more responsible and ethical approach to AI development. Read a transcript of this interview: <a href="https://bit.ly/3LopSlT" rel="nofollow" target="_blank">https://bit.ly/3LopSlT</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl" rel="nofollow" target="_blank">https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl</a> Upcoming Events: QCon New York <a href="https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23" rel="nofollow" target="_blank">https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq" rel="nofollow" target="_blank">https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq</a>

Leslie Miley on AI Bias and Sustainability

Tomáš Neubauer

Live from the venue of the QCon London Conference we are talking with Tomáš Neubauer. He will talk about Quix Streams, an open-source Python library that simplifies real-time machine learning pipelines. In his presentation, Tomáš will discuss various architecture designs, their pros and cons, and demonstrate a real use case of detecting a cyclist crash using Quix Streams and a TensorFlow model.Read a transcript of this interview: https://bit.ly/3L87BckSubscribe to the Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl Upcoming Events:QCon New Yorkhttps://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23 June 13-15, 2023QCon San Francisco:https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23 Oct 2-6, 2023Follow InfoQ:- Mastodon: https://techhub.social/@infoq - Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq

Live from the venue of the QCon London Conference we are talking with Tomáš Neubauer. He will talk about Quix Streams, an open-source Python library that simplifies real-time machine learning pipelines. In his presentation, Tomáš will discuss various architecture designs, their pros and cons, and demonstrate a real use case of detecting a cyclist crash using Quix Streams and a TensorFlow model. Read a transcript of this interview: <a href="https://bit.ly/3L87Bck" rel="nofollow" target="_blank">https://bit.ly/3L87Bck</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl" rel="nofollow" target="_blank">https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl</a> Upcoming Events: QCon New York <a href="https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23" rel="nofollow" target="_blank">https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq" rel="nofollow" target="_blank">https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq</a>

Real Time ML Pipelines Using Quix with Tomáš Neubauer

In this episode of the podcast, members of the InfoQ editorial staff will be discussing the current trends in software architecture and design, as part of the process to create our annual trends report. These reports provide the InfoQ readers with a high-level overview of the topics to pay attention to, and also help the editorial team focus on innovative technologies. In addition to the report and the trends graph available on InfoQ.com, this podcast is a chance to hear our conversation and some stories our expert practitioners have observed. Read a transcript of this interview: https://bit.ly/3JHEg7OSubscribe to the Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl Upcoming Events:QCon New Yorkhttps://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23 June 13-15, 2023QCon San Francisco:https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23 Oct 2-6, 2023Follow InfoQ:- Mastodon: https://techhub.social/@infoq - Twitter: twitter.com/InfoQ- LinkedIn: www.linkedin.com/company/infoq- Facebook: bit.ly/2jmlyG8- Instagram: @infoqdotcom- Youtube: www.youtube.com/infoqWrite for InfoQ- Join a community of experts.- Increase your visibility.- Grow your career.https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq

In this episode of the podcast, members of the InfoQ editorial staff will be discussing the current trends in software architecture and design, as part of the process to create our annual trends report. These reports provide the InfoQ readers with a high-level overview of the topics to pay attention to, and also help the editorial team focus on innovative technologies. In addition to the report and the trends graph available on <a href="http://InfoQ.com" rel="nofollow" target="_blank">InfoQ.com</a>, this podcast is a chance to hear our conversation and some stories our expert practitioners have observed. Read a transcript of this interview: <a href="https://bit.ly/3JHEg7O" rel="nofollow" target="_blank">https://bit.ly/3JHEg7O</a> Subscribe to the Software Architects’ Newsletter [monthly]: <a href="https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl" rel="nofollow" target="_blank">https://www.infoq.com/software-architects-newsletter/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=architectnl</a> Upcoming Events: QCon New York <a href="https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23" rel="nofollow" target="_blank">https://qconnewyork.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qny23</a> June 13-15, 2023 QCon San Francisco: <a href="https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23" rel="nofollow" target="_blank">https://qconsf.com/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=qsf23</a> Oct 2-6, 2023 Follow InfoQ: - Mastodon: https://techhub.social/@infoq - Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> - LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> - Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> - Instagram: @infoqdotcom - Youtube: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Write for InfoQ - Join a community of experts. - Increase your visibility. - Grow your career. <a href="https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq" rel="nofollow" target="_blank">https://www.infoq.com/write-for-infoq/?utm_source=soundcloud&amp;utm_medium=podcast&amp;utm_campaign=writeforinfoq</a>

InfoQ Podcast - 2023 InfoQ Software Architecture & Design Trends

Software engineers, architects and team leads have found inspiration to drive change and innovation in their team by listening to the weekly InfoQ Podcast. They have received essential information that helped them validate their software development map. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 1,200,000 downloads in the last 3 years.

Good content and I have been listening to it for a while. Unable to play any podcasts since last few days. The download or streaming gets stuck with error.

Access to podcasts is broken

This is another highly informative Podcast about the latest innovation in software technology

Software Architect

The InfoQ Podcast

Bryan Liles

In this podcast, Daniel Bryant sat down with Bryan Liles, senior staff engineer at VMware. Topics covered included: the challenges with deploying applications into Kubernetes, using the open source Octant tool to increase a user’s understanding of Kubernetes clusters, and how “serverless” technologies may influence the future approaches to building software.Why listen to this podcast: - Octant is a highly extensible platform for developers to better understand the complexity of Kubernetes clusters. Octant runs locally, using the local Kubernetes credentials. It currently displays information about a Kubernetes cluster and related applications as a web page. Soon this tool and resulting display will be provided as a standalone application. - The goal of Octant is to enable users to discover what they need to discover. The tool aims to provide context relevant to where a user is and what they are trying to achieve. The Octant plugin system allows integration with other tooling, such as logging and metrics frameworks. This aims to facilitate quick problem detection and resolution. - Cloud native platforms like Kubernetes are complicated, as there are lots of moving parts. The most important challenge to be tackled to increase the adoption of platforms like Kubernetes is “how do we move code from our IDEs to wherever it needs to run with the least amount of friction?”. Testing needs to be implicit, as does security verification, and the acts of deployment. Kubernetes needs its “Ruby on Rails” moment. - Creating “serverless” systems is an interesting approach, but we may currently be using this technology in a non-optimal way. For example, creating web applications using this technology enables scalability, but can lead to the creation of difficult to understand systems that also require a lot of boilerplate configuration. Arguably, a more interesting use case is implementing large-scale batch processing using simple event-driven models.- The Cloud Native Computing Foundation (CNCF) has created a series of communities of practice called Special Interest Groups (SIGs), such as SIG App Delivery. This allows folks with similar interests to work together as a community, focusing on solving a specific set of well-scoped problems. There are many ways to get involved, from discussions, to coding and creating documentation.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/37iUwIGYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/37iUwIG

In this podcast, Daniel Bryant sat down with Bryan Liles, senior staff engineer at VMware. Topics covered included: the challenges with deploying applications into Kubernetes, using the open source Octant tool to increase a user’s understanding of Kubernetes clusters, and how “serverless” technologies may influence the future approaches to building software. Why listen to this podcast: - Octant is a highly extensible platform for developers to better understand the complexity of Kubernetes clusters. Octant runs locally, using the local Kubernetes credentials. It currently displays information about a Kubernetes cluster and related applications as a web page. Soon this tool and resulting display will be provided as a standalone application. - The goal of Octant is to enable users to discover what they need to discover. The tool aims to provide context relevant to where a user is and what they are trying to achieve. The Octant plugin system allows integration with other tooling, such as logging and metrics frameworks. This aims to facilitate quick problem detection and resolution. - Cloud native platforms like Kubernetes are complicated, as there are lots of moving parts. The most important challenge to be tackled to increase the adoption of platforms like Kubernetes is “how do we move code from our IDEs to wherever it needs to run with the least amount of friction?”. Testing needs to be implicit, as does security verification, and the acts of deployment. Kubernetes needs its “Ruby on Rails” moment. - Creating “serverless” systems is an interesting approach, but we may currently be using this technology in a non-optimal way. For example, creating web applications using this technology enables scalability, but can lead to the creation of difficult to understand systems that also require a lot of boilerplate configuration. Arguably, a more interesting use case is implementing large-scale batch processing using simple event-driven models. - The Cloud Native Computing Foundation (CNCF) has created a series of communities of practice called Special Interest Groups (SIGs), such as SIG App Delivery. This allows folks with similar interests to work together as a community, focusing on solving a specific set of well-scoped problems. There are many ways to get involved, from discussions, to coding and creating documentation. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/37iUwIG" rel="nofollow" target="_blank">https://bit.ly/37iUwIG</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/37iUwIG" rel="nofollow" target="_blank">https://bit.ly/37iUwIG</a>

Bryan Liles on Making Kubernetes Easier for Developers, the CNCF, and “Serverless”

Keith Adams

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 userNotes and links can be found on: http://bit.ly/keith-adams3m:30s Voice and video interactions are impacted by latency; the same is true of messaging clients4m:00s The user interface can provide indications of presence, through avatars indicating availability and typing indicators4m:15s Latency is important; sometimes the difference is between 100ms and 200ms so the message channel monitors ping timeout between server and client4m:40s 99th percentile is less than 100ms ping time5m:15s If the 99th percentile is more than 100ms then it may be server based, such as needing to tune the Java GC5m:25s Network conditions of the mobile clients are highly variable 6m:20s Mobile clients can suffer intermittent connectivityMore on this:Quick scan our curated show notes on InfoQ. http://bit.ly/keith-adamsYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

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 [<a href="http://hhvm.com" rel="nofollow" target="_blank">hhvm.com</a>]. 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: <a href="http://bit.ly/keith-adams" rel="nofollow" target="_blank">http://bit.ly/keith-adams</a> 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  6m:20s Mobile clients can suffer intermittent connectivity More on this: Quick scan our curated show notes on InfoQ. <a href="http://bit.ly/keith-adams" rel="nofollow" target="_blank">http://bit.ly/keith-adams</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a>

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

Martin Fowler

Martin Fowler chats about the work he’s done over the last couple of years on the rewrite of the original Refactorings book. He discusses how this thought process has changed and how that’s affected the new edition of the book. In addition to discussing Refactors, Martin and Wes discuss his thoughts on evolutionary architecture, team structures, and how the idea of refactors can be applied in larger architecture contexts.Why listen to this podcast: -    Refactoring is the idea of trying to identify the sequence of small steps that allows you to make a big change. That core idea hasn’t changed. - Several new refactorings in the book deal with the idea of transforming data structures into other data structures, Combine Functions into Transform for example. - Several of the refactorings were removed or not added to the book in favor of adding them to a web edition of the book. - A lot of the early refactorings are like cleaning the dirt off the glass of a window. You just need them to be able to see where the hell you are and then you can start looking at the broader ones. - Refactorings can be applied broadly to architecture evolution. Two recent posts How to break a Monolith into Microservices, by Zhamak Dehghani,  and How to extract a data-rich service from a monolith by Praful Todkar on MartinFowler.com deal with this specifically. - Evolutionary architecture is a broad principle that architecture is constantly changing. While related to Microservices, it’s not Microservices by another name. You could evolve towards or away from Microservices for example.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2QbdHejYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/2QbdHej

Martin Fowler chats about the work he’s done over the last couple of years on the rewrite of the original Refactorings book. He discusses how this thought process has changed and how that’s affected the new edition of the book. In addition to discussing Refactors, Martin and Wes discuss his thoughts on evolutionary architecture, team structures, and how the idea of refactors can be applied in larger architecture contexts. Why listen to this podcast: - Refactoring is the idea of trying to identify the sequence of small steps that allows you to make a big change. That core idea hasn’t changed. - Several new refactorings in the book deal with the idea of transforming data structures into other data structures, Combine Functions into Transform for example. - Several of the refactorings were removed or not added to the book in favor of adding them to a web edition of the book. - A lot of the early refactorings are like cleaning the dirt off the glass of a window. You just need them to be able to see where the hell you are and then you can start looking at the broader ones. - Refactorings can be applied broadly to architecture evolution. Two recent posts How to break a Monolith into Microservices, by Zhamak Dehghani, and How to extract a data-rich service from a monolith by Praful Todkar on <a href="http://MartinFowler.com" rel="nofollow" target="_blank">MartinFowler.com</a> deal with this specifically. - Evolutionary architecture is a broad principle that architecture is constantly changing. While related to Microservices, it’s not Microservices by another name. You could evolve towards or away from Microservices for example. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/2QbdHej" rel="nofollow" target="_blank">https://bit.ly/2QbdHej</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2QbdHej" rel="nofollow" target="_blank">https://bit.ly/2QbdHej</a>

Martin Fowler Discusses New Edition of Refactoring, Along With Thoughts on Evolutionary Architecture

Bryan Cantrill

Bryan Cantrill is the CTO of Joyent and well known for the development of DTrace at Sun Microsystems. Today on the podcast, Bryan discusses with Wes Reisz a bit about the origins of DTrace and then spends the rest of the time discussing why he feels Rust is the “biggest development in systems development in his career.” The podcast wraps with a bit about why Bryan feels we should be rewriting parts of the operating system in Rust.Why listen to the podcast:• DTrace came down to a desire to use Dynamic Program Text Modification to instrument running systems (much like debuggers do) and has its origins to when Bryan was an undergraduate.• When a programming language delivers something to you, it takes it from you in the runtime. The classic example of this is garbage collection. The programming language gives you the ability to use memory dynamically without thinking of how the memory is stored in the system, but then it’s going to exact a runtime cost.• One of the issues with C is that it just doesn’t compose well. You can’t just necessarily pull a library off the Internet and use it well. Everyone’s C is laden with some many idiosyncrasies on how it’s used and the contract on how memory is used.• Ownership is statically tracking who owns the structure. It’s ownership and the absence of GC that allows you to address the composability issues found in C.• It’s really easy in C to have integer overflow which leads to memory safety issues that can be exploited by an attacker. Rust makes this pretty much impossible because it’s very good at how it determines how you use signed vs unsigned types.• You don’t want people solving the same problems over and over again. You want composability. You want abstractions. What you don’t want is where you’ve removed so much developer friction that you develop code that is riddled with problems. For example, it slows a developer down to force them to run a linter, but it results in better artifacts. Rust effective builds a lot of that linter checking into the memory management/type checking system.• While there’s some learning curve to Rust. It’s not that bad if you realize there are several core concepts you need to understand to understand Rust. Rust is one of those languages that you really need to learn in a structured way. Sit down with a book and learn it.• Rust struggles when you have objects that are multiply owned (such as a Doubly Linked List). It’s because it doesn’t know who owns what. While Rust supports unsafe operations, you should resist the temptation to develop with a lot of unsafe operations if you want the benefits of what Rust offers developers.• Firmware is a great spot for growing Rust development in a process of replacing bits of what we think of as the operating system.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2uZ5QHZYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/2uZ5QHZ

Bryan Cantrill is the CTO of Joyent and well known for the development of DTrace at Sun Microsystems. Today on the podcast, Bryan discusses with Wes Reisz a bit about the origins of DTrace and then spends the rest of the time discussing why he feels Rust is the “biggest development in systems development in his career.” The podcast wraps with a bit about why Bryan feels we should be rewriting parts of the operating system in Rust. Why listen to the podcast: • DTrace came down to a desire to use Dynamic Program Text Modification to instrument running systems (much like debuggers do) and has its origins to when Bryan was an undergraduate. • When a programming language delivers something to you, it takes it from you in the runtime. The classic example of this is garbage collection. The programming language gives you the ability to use memory dynamically without thinking of how the memory is stored in the system, but then it’s going to exact a runtime cost. • One of the issues with C is that it just doesn’t compose well. You can’t just necessarily pull a library off the Internet and use it well. Everyone’s C is laden with some many idiosyncrasies on how it’s used and the contract on how memory is used. • Ownership is statically tracking who owns the structure. It’s ownership and the absence of GC that allows you to address the composability issues found in C. • It’s really easy in C to have integer overflow which leads to memory safety issues that can be exploited by an attacker. Rust makes this pretty much impossible because it’s very good at how it determines how you use signed vs unsigned types. • You don’t want people solving the same problems over and over again. You want composability. You want abstractions. What you don’t want is where you’ve removed so much developer friction that you develop code that is riddled with problems. For example, it slows a developer down to force them to run a linter, but it results in better artifacts. Rust effective builds a lot of that linter checking into the memory management/type checking system. • While there’s some learning curve to Rust. It’s not that bad if you realize there are several core concepts you need to understand to understand Rust. Rust is one of those languages that you really need to learn in a structured way. Sit down with a book and learn it. • Rust struggles when you have objects that are multiply owned (such as a Doubly Linked List). It’s because it doesn’t know who owns what. While Rust supports unsafe operations, you should resist the temptation to develop with a lot of unsafe operations if you want the benefits of what Rust offers developers. • Firmware is a great spot for growing Rust development in a process of replacing bits of what we think of as the operating system. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/2uZ5QHZ" rel="nofollow" target="_blank">https://bit.ly/2uZ5QHZ</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2uZ5QHZ" rel="nofollow" target="_blank">https://bit.ly/2uZ5QHZ</a>

Bryan Cantrill on Rust and Why He Feels It’s The Biggest Change In Systems Development in His Career

Pat Kua

In this podcast we discuss a holistic approach to technical leadership, and Pat provides guidance on everything from defining target operating models, cultivating culture, and supporting people in developing the career they would like. There are a bunch of great stories, several book recommendations, and additional resources to follow up on.* Cultivating organisational culture is much like gardening: you can’t force things, but you can set the right conditions for growth. The most effective strategy is to communicate the vision and goals, lead the people, and manage the systems and organisational structure.* N26, a challenger bank based in Berlin has experienced hypergrowth over the past two years. Both the number of customers and the amount of employees have increased over threefold. This provides lots of opportunities for ownership of product and projects, and it creates unique leadership challenges.* A target operating model (TOM) is a blueprint of a firm's business vision that aligns operating capacities and strategic objectives and provides an overview of the core business capabilities, internal factors, and external drivers, strategic and operational levers. This should be shared widely within an organisation* Pat has curated a “trident operating” model for employee growth. In addition to the class individual contributor (IC) and management tracks, he believes that a third “technical leadership” track provides many benefits.* People can switch between these tracks as their personal goals change. However, this switch can be challenging, and an organisation must support any transition with effective training.* Pat recommends the following books for engineers looking to make the transition to leadership: The Manager’s Path, by Camille Fournier; Resilient Management, by Lara Hogan; Elegant Puzzle, by Will Larson; and Leading Snowflakes by Oren Ellenbogen. Pat has also written his own book, Talking with Tech Leads.* It is valuable to define organisation values upfront. However, these can differ from actual culture, which more about what behaviours you allow, encourage, and stop.* Much like the values provided by Netflix’s Freedom and Responsibility model, Pat argues that balancing autonomy and alignment within an organisation is vital for success. Managers can help their team by clearly defining boundaries for autonomy and responsibility.* Developing the skills to influence people is very valuable for leaders. Influence is based on trust, and this must be constantly cultivated. Trust is much like a bank account, if you don’t regular deposit actions to build trust, you may find yourself going overdrawn when making a deposit. This can lead to bad will and defensive strategies being employed.

In this podcast we discuss a holistic approach to technical leadership, and Pat provides guidance on everything from defining target operating models, cultivating culture, and supporting people in developing the career they would like. There are a bunch of great stories, several book recommendations, and additional resources to follow up on. * Cultivating organisational culture is much like gardening: you can’t force things, but you can set the right conditions for growth. The most effective strategy is to communicate the vision and goals, lead the people, and manage the systems and organisational structure. * N26, a challenger bank based in Berlin has experienced hypergrowth over the past two years. Both the number of customers and the amount of employees have increased over threefold. This provides lots of opportunities for ownership of product and projects, and it creates unique leadership challenges. * A target operating model (TOM) is a blueprint of a firm's business vision that aligns operating capacities and strategic objectives and provides an overview of the core business capabilities, internal factors, and external drivers, strategic and operational levers. This should be shared widely within an organisation * Pat has curated a “trident operating” model for employee growth. In addition to the class individual contributor (IC) and management tracks, he believes that a third “technical leadership” track provides many benefits. * People can switch between these tracks as their personal goals change. However, this switch can be challenging, and an organisation must support any transition with effective training. * Pat recommends the following books for engineers looking to make the transition to leadership: The Manager’s Path, by Camille Fournier; Resilient Management, by Lara Hogan; Elegant Puzzle, by Will Larson; and Leading Snowflakes by Oren Ellenbogen. Pat has also written his own book, Talking with Tech Leads. * It is valuable to define organisation values upfront. However, these can differ from actual culture, which more about what behaviours you allow, encourage, and stop. * Much like the values provided by Netflix’s Freedom and Responsibility model, Pat argues that balancing autonomy and alignment within an organisation is vital for success. Managers can help their team by clearly defining boundaries for autonomy and responsibility. * Developing the skills to influence people is very valuable for leaders. Influence is based on trust, and this must be constantly cultivated. Trust is much like a bank account, if you don’t regular deposit actions to build trust, you may find yourself going overdrawn when making a deposit. This can lead to bad will and defensive strategies being employed.

Pat Kua on Technical Leadership, Cultivating Culture, and Career Growth

Chris Richardson

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 approachNotes and links can be found on: http://bit.ly/2hZ8TM111m: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/2hZ8TM1You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

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: <a href="http://bit.ly/2hZ8TM1" rel="nofollow" target="_blank">http://bit.ly/2hZ8TM1</a> 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. <a href="http://bit.ly/2hZ8TM1" rel="nofollow" target="_blank">http://bit.ly/2hZ8TM1</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a>

Chris Richardson on Domain-Driven Microservices Design

Ryan Kitchens

In today’s podcast we sit down with Ryan Kitchens, a senior site reliability engineer and member of the CORE team at Netflix. This team is responsible for the entire lifecycle of incident management at Netflix, from incident response to memorialising an issue.Why listen to this podcast: - Top level metrics can be used as a proxy for user experience, and can be used to determine that issue should be alerted on an investigated. For example, at Netflix if the customer playback initiation “streams per second” metric declines rapidly, this may be an indication that something has broken. - Focusing on how things go right can provide valuable insight into the resilience within your system e.g. what are people doing everyday that helps us overcome incidents. Finding sources of resilience is somewhat “the story of the incident you didn’t have”. - When conducting an incident postmortem, simply reconstructing an incident is often not sufficient to determine what needs to be fixed; there is no root cause with complex socio-technical systems as found at Netflix and most modern web-based organisations. Instead, teams must dig a little deeper, and look for what went well, what contributed to the problem, and where are the recurring patterns. - Resilience engineering is a multidisciplinary field that was established in the early 2000s, and the associated community that has emerged is both academic and deeply practical. Although much resilience engineering focuses on domains such as aviation, surgery and military agencies, there is much overlap with the domain of software engineering. - Make sure that support staff within an organisation have a feedback loop into the product team, as these people providing support often know where all of the hidden problems are, the nuances of the systems, and the workarounds.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2LLwk8TYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/2LLwk8T

In today’s podcast we sit down with Ryan Kitchens, a senior site reliability engineer and member of the CORE team at Netflix. This team is responsible for the entire lifecycle of incident management at Netflix, from incident response to memorialising an issue. Why listen to this podcast: - Top level metrics can be used as a proxy for user experience, and can be used to determine that issue should be alerted on an investigated. For example, at Netflix if the customer playback initiation “streams per second” metric declines rapidly, this may be an indication that something has broken. - Focusing on how things go right can provide valuable insight into the resilience within your system e.g. what are people doing everyday that helps us overcome incidents. Finding sources of resilience is somewhat “the story of the incident you didn’t have”. - When conducting an incident postmortem, simply reconstructing an incident is often not sufficient to determine what needs to be fixed; there is no root cause with complex socio-technical systems as found at Netflix and most modern web-based organisations. Instead, teams must dig a little deeper, and look for what went well, what contributed to the problem, and where are the recurring patterns. - Resilience engineering is a multidisciplinary field that was established in the early 2000s, and the associated community that has emerged is both academic and deeply practical. Although much resilience engineering focuses on domains such as aviation, surgery and military agencies, there is much overlap with the domain of software engineering. - Make sure that support staff within an organisation have a feedback loop into the product team, as these people providing support often know where all of the hidden problems are, the nuances of the systems, and the workarounds. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/2LLwk8T" rel="nofollow" target="_blank">https://bit.ly/2LLwk8T</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2LLwk8T" rel="nofollow" target="_blank">https://bit.ly/2LLwk8T</a>

Ryan Kitchens on Learning from Incidents at Netflix, the Role of SRE, and Sociotechnical Systems

Peter Bourgon

Paxos

Peter Bourgon discusses his work at Weaveworks, discovering and imlemeting CRDTs for time-stamped events at Soundcloud, Microservices in Go with Go Kit and the state of package management in Go.Why listen to this podcast: - We’ve hit the limits of Moore’s law so when we want to scale we have to think about how we do communication across unreliable links between unreliable machines. - In an AP algorithm like Gossip you still make forward progress in case of a failure. In Paxos you stop and return failures. - CRDTs give us a rigours set of rules to accommodate failures for maps, sets etc. in communication that result in am eventually consistent system. - Go is optimised to readers/maintainers vs. making the programmers’ life easier. Go is closer to C than Java in that it allows you to layout memory very precisely, allowing you to, for example, optimise cache lines in your CPU.  - Bourgon started a project called Go Kit, which is designed for building microservices in Go. It takes inspiration from Tiwtter’s Scala-based Finagle which solved a lot of Micoservice concerns.  - Go has a number of community-maintained package managers but no good solution; work in ongoing to try and resolve this.Notes and links can be found on: http://bit.ly/2kaHC9kWork at WeaveworksGossip vs. PaxosCRDTs at SoundCloudGoGo in large teamsGo and Java package managementMicroservices in Go with Go KitLogging and tracing in a distributed environmentMore on this:Quick scan our curated show notes on InfoQ. http://bit.ly/2kaHC9kYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Peter Bourgon discusses his work at Weaveworks, discovering and imlemeting CRDTs for time-stamped events at Soundcloud, Microservices in Go with Go Kit and the state of package management in Go. Why listen to this podcast: - We’ve hit the limits of Moore’s law so when we want to scale we have to think about how we do communication across unreliable links between unreliable machines. - In an AP algorithm like Gossip you still make forward progress in case of a failure. In Paxos you stop and return failures. - CRDTs give us a rigours set of rules to accommodate failures for maps, sets etc. in communication that result in am eventually consistent system. - Go is optimised to readers/maintainers vs. making the programmers’ life easier. Go is closer to C than Java in that it allows you to layout memory very precisely, allowing you to, for example, optimise cache lines in your CPU. - Bourgon started a project called Go Kit, which is designed for building microservices in Go. It takes inspiration from Tiwtter’s Scala-based Finagle which solved a lot of Micoservice concerns. - Go has a number of community-maintained package managers but no good solution; work in ongoing to try and resolve this. Notes and links can be found on: <a href="http://bit.ly/2kaHC9k" rel="nofollow" target="_blank">http://bit.ly/2kaHC9k</a> Work at Weaveworks Gossip vs. Paxos CRDTs at SoundCloud Go Go in large teams Go and Java package management Microservices in Go with Go Kit Logging and tracing in a distributed environment More on this: Quick scan our curated show notes on InfoQ. <a href="http://bit.ly/2kaHC9k" rel="nofollow" target="_blank">http://bit.ly/2kaHC9k</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a>

Peter Bourgon on Gossip, Paxos, Microservices in Go, and CRDTs at SoundCloud

Arun Gupta

Arun Gupta discusses with Wes Reisz some of the container-focused services that AWS offers, including differentiating ECS and EKS. Arun goes into some detail the role that Amazon Fargate plays and goals behinds EKS. Arun wraps ups discussing some of the open source work that AWS has recently been doing in the container space.Why liste to this podcast:- ECS &amp; EKS are both managed control planes; Amazon Fargate is a technology used to provision clusters. - ECR is the Amazon Container registry (similar to the Docker Registry). - EKS is an opinionated why of running a Kubernetes cluster on AWS. It is a highly available managed control plane available on US East 1 and US West 2 - EKS uses a split account. The control plane runs in an Amazon account and the workers run in customer’s account.- Upstream compatibility is a core tenant of EKS.You 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/infoqCheck the landing page on InfoQ: https://bit.ly/2tWT8t9

Arun Gupta discusses with Wes Reisz some of the container-focused services that AWS offers, including differentiating ECS and EKS. Arun goes into some detail the role that Amazon Fargate plays and goals behinds EKS. Arun wraps ups discussing some of the open source work that AWS has recently been doing in the container space. Why liste to this podcast: - ECS &amp; EKS are both managed control planes; Amazon Fargate is a technology used to provision clusters. - ECR is the Amazon Container registry (similar to the Docker Registry). - EKS is an opinionated why of running a Kubernetes cluster on AWS. It is a highly available managed control plane available on US East 1 and US West 2 - EKS uses a split account. The control plane runs in an Amazon account and the workers run in customer’s account. - Upstream compatibility is a core tenant of EKS. You can subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2tWT8t9" rel="nofollow" target="_blank">https://bit.ly/2tWT8t9</a>

Arun Gupta on Managed Container Control Planes on AWS

Oliver Gould

This week on The InfoQ Podcast Wes Reisz talks with the CTO of Bouyant Oliver Gould. Bouyant is the maker the LinkerD Service Mesh and the recently released Conduit. In the podcast, Oliver defines a service mesh, clarifies the meaning of the data and control plane, discusses what a Service Mesh can offer a Microservice application owners, and, finally, discusses some of the considerations they took into account developing Conduit.Why listen to this podcast:- Service mesh is dedicated infrastructure that handles interservice communication.- There are two components to a service mesh: the data plane handles communication and the control plane is about policy and config.- LinkerD and Conduit are two open service meshes made by Bouyant. Conduit has a small memory footprint and provides a convention over configuration approach to service mesh deployment.- Adopting Rust (language used for implementing the data plane in Conduit) requires thinking of memory differently, and the best way to adopt Rust is to read other people’s code.More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2skWF61You 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/infoqCheck the landing page on InfoQ: http://bit.ly/2skWF61

This week on The InfoQ Podcast Wes Reisz talks with the CTO of Bouyant Oliver Gould. Bouyant is the maker the LinkerD Service Mesh and the recently released Conduit. In the podcast, Oliver defines a service mesh, clarifies the meaning of the data and control plane, discusses what a Service Mesh can offer a Microservice application owners, and, finally, discusses some of the considerations they took into account developing Conduit. Why listen to this podcast: - Service mesh is dedicated infrastructure that handles interservice communication. - There are two components to a service mesh: the data plane handles communication and the control plane is about policy and config. - LinkerD and Conduit are two open service meshes made by Bouyant. Conduit has a small memory footprint and provides a convention over configuration approach to service mesh deployment. - Adopting Rust (language used for implementing the data plane in Conduit) requires thinking of memory differently, and the best way to adopt Rust is to read other people’s code. More on this: Quick scan our curated show notes on InfoQ <a href="http://bit.ly/2skWF61" rel="nofollow" target="_blank">http://bit.ly/2skWF61</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="http://bit.ly/2skWF61" rel="nofollow" target="_blank">http://bit.ly/2skWF61</a>

Oliver Gould on Service Mesh for Microservices, LinkerD, and the Recently Released Conduit

On this week’s podcast, Danny Yuan, Uber’s Real-time Streaming/Forecasting Lead, lays out a thorough recipe book for building a real-time streaming platform with a major focus on forecasting. In this podcast, Danny discusses everything from the scale Uber operates at to what the major steps for training/deploy models in an iterative (almost Darwinistic) fashion and wraps with his advice for software engineers who want to begin applying machine learning into their day-to-day job.  Why listen to this podcast:* Uber processes 850,000 - 1.3 million messages per second in their streaming platform with about 12 TB of growth per day. The system’s queries scan 100 million to 4 billion documents per second.* Uber’s frontend is mobile. The frontend talks to an API layer. All services generate events that are shuffled into Kafka. The real-time forecasting pipeline taps into Kafka to processes events and stores the data into Elasticsearch. * There is a federated query layer in front of Elasticsearch to provide OLAP query capabilities.* Apache Flink’s advanced windowing features, programming model, and checkpointing convinced Uber to move away from the simplicity of Apache Samza.* The forecasting system allows Uber to remove the notion of delay by using recent signals plus historical data to project what is happening now and what will happen into the future.* Uber’s pipeline for deploying ML models: HDFS, feature engineering, organizing into data structures (similar to data frames), deploy mostly offline training models, train models, &amp; store into a container-based model manager. * A model serving layer is used to pick which model to use, forecasting results are stored in an OLAP data store, a validation layer compares real results against forecast results to verify the model is working as desired, and a rollback feature enables poor performing models to be automatically replaced by previous one.* “Without output, you don’t have input.” If you want to start leveraging machine learning, developers just need to start doing. Start with intuition and practice. Over time ask questions and learn what you need, then apply a laser focus to gain that knowledge.You 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/infoqCheck the landing page on InfoQ: https://bit.ly/2GJQbUo

On this week’s podcast, Danny Yuan, Uber’s Real-time Streaming/Forecasting Lead, lays out a thorough recipe book for building a real-time streaming platform with a major focus on forecasting. In this podcast, Danny discusses everything from the scale Uber operates at to what the major steps for training/deploy models in an iterative (almost Darwinistic) fashion and wraps with his advice for software engineers who want to begin applying machine learning into their day-to-day job. Why listen to this podcast: * Uber processes 850,000 - 1.3 million messages per second in their streaming platform with about 12 TB of growth per day. The system’s queries scan 100 million to 4 billion documents per second. * Uber’s frontend is mobile. The frontend talks to an API layer. All services generate events that are shuffled into Kafka. The real-time forecasting pipeline taps into Kafka to processes events and stores the data into Elasticsearch. * There is a federated query layer in front of Elasticsearch to provide OLAP query capabilities. * Apache Flink’s advanced windowing features, programming model, and checkpointing convinced Uber to move away from the simplicity of Apache Samza. * The forecasting system allows Uber to remove the notion of delay by using recent signals plus historical data to project what is happening now and what will happen into the future. * Uber’s pipeline for deploying ML models: HDFS, feature engineering, organizing into data structures (similar to data frames), deploy mostly offline training models, train models, &amp; store into a container-based model manager. * A model serving layer is used to pick which model to use, forecasting results are stored in an OLAP data store, a validation layer compares real results against forecast results to verify the model is working as desired, and a rollback feature enables poor performing models to be automatically replaced by previous one. * “Without output, you don’t have input.” If you want to start leveraging machine learning, developers just need to start doing. Start with intuition and practice. Over time ask questions and learn what you need, then apply a laser focus to gain that knowledge. You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2GJQbUo" rel="nofollow" target="_blank">https://bit.ly/2GJQbUo</a>

Streaming: Danny Yuan on Real-Time, Time Series Forecasting @Uber

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 testingNotes and links can be found on: http://bit.ly/2ivoz9w4m:05s - Each domain has different failure and operating modes, and the layered approach to resiliency means that the layer handles this automatically4m:30s - Large systems may fail in unexpected ways4m:35s - Twitter originally had the “Fail Whale” but this has been phased out as the system has become more stable4m:50s - As Twitter grew, it needed to move quicker, with more engineers and less whale time5m:10s - Automation and social tools were needed to improve the situationMore on this - Quick scan our curated show notes on InfoQ: http://bit.ly/2ivoz9wYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

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: <a href="http://bit.ly/2ivoz9w" rel="nofollow" target="_blank">http://bit.ly/2ivoz9w</a> 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: <a href="http://bit.ly/2ivoz9w" rel="nofollow" target="_blank">http://bit.ly/2ivoz9w</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a>

Oliver Gould About Architecting to Avoid and Recover from Failure

Vaughn Vernon

Vaughn Vernon is thought-leader in the space of reactive software and Domain Driven Design (DDD). Vaughn has recently released a new open source project called vlingo. The platform is designed to support DDD at the framework and toolkit level. On today’s podcast, Vaughn discusses what the framework is all about, why he felt it was needed, and some of the design decisions made in developing the platform, including things like the architecture, actor model decisions, clustering algorithm, and how DDD is realized with the framework.Why listen to this podcast: - Vlingo is an open source system for building distributed, concurrent, event-driven, reactive microservices that supports (at the framework level) Domain Driven Design. - The platform is in the early stages. It runs on the JVM. There is a port to C#. All code is pushed up stream. - The platform uses the actor model and all messages are sent in a type-safe way. - Vlingo supports clustering and uses a bully algorithm to achieve consensus.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2MwEWxbYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/2MwEWxb

Vaughn Vernon is thought-leader in the space of reactive software and Domain Driven Design (DDD). Vaughn has recently released a new open source project called vlingo. The platform is designed to support DDD at the framework and toolkit level. On today’s podcast, Vaughn discusses what the framework is all about, why he felt it was needed, and some of the design decisions made in developing the platform, including things like the architecture, actor model decisions, clustering algorithm, and how DDD is realized with the framework. Why listen to this podcast: - Vlingo is an open source system for building distributed, concurrent, event-driven, reactive microservices that supports (at the framework level) Domain Driven Design. - The platform is in the early stages. It runs on the JVM. There is a port to C#. All code is pushed up stream. - The platform uses the actor model and all messages are sent in a type-safe way. - Vlingo supports clustering and uses a bully algorithm to achieve consensus. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/2MwEWxb" rel="nofollow" target="_blank">https://bit.ly/2MwEWxb</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2MwEWxb" rel="nofollow" target="_blank">https://bit.ly/2MwEWxb</a>

Vaughn Vernon on Developing a Domain Driven Design first Actor-Based Microservices Framework

In this special year-end wrap-up podcast Wes Reisz, Shane Hastie, Daniel Bryant, and Charles Humble discuss what we’ve seen in 2019 and speculate a little on what we hope to see in 2020. Topics include business agility and Teal, what it means to be an ethical engineer, bringing your whole self to work, highlights from QCon and InfoQ during 2019, the rise of Python, and progress in quantum computing.Why listen to this podcast:* Business agility is one of the major themes that the InfoQ team has seen emerge this year, with stronger emphasis on outcomes over outputs. We’ve also seen a growing interest in ethics and the ethical implications of the work we all do.* On the programming languages front the rise of Python continues, driven largely by its popularity in data science.* As Kubernetes cements its dominant position we’re hoping to see a simplification of the workflows associated with it, as well as in areas like observability.* There have been several big announcements in quantum computing in the past year, and this is an area we continue to watch with interest.* Another key trend for next year is edge computing. The edge of the cloud infrastructure has an amazing amount of available compute resource, as does the device edge.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2Z0Q9OIYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/2Z0Q9OI

In this special year-end wrap-up podcast Wes Reisz, Shane Hastie, Daniel Bryant, and Charles Humble discuss what we’ve seen in 2019 and speculate a little on what we hope to see in 2020. Topics include business agility and Teal, what it means to be an ethical engineer, bringing your whole self to work, highlights from QCon and InfoQ during 2019, the rise of Python, and progress in quantum computing. Why listen to this podcast: * Business agility is one of the major themes that the InfoQ team has seen emerge this year, with stronger emphasis on outcomes over outputs. We’ve also seen a growing interest in ethics and the ethical implications of the work we all do. * On the programming languages front the rise of Python continues, driven largely by its popularity in data science. * As Kubernetes cements its dominant position we’re hoping to see a simplification of the workflows associated with it, as well as in areas like observability. * There have been several big announcements in quantum computing in the past year, and this is an area we continue to watch with interest. * Another key trend for next year is edge computing. The edge of the cloud infrastructure has an amazing amount of available compute resource, as does the device edge. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/2Z0Q9OI" rel="nofollow" target="_blank">https://bit.ly/2Z0Q9OI</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2Z0Q9OI" rel="nofollow" target="_blank">https://bit.ly/2Z0Q9OI</a>

The InfoQ Podcast Hosts Take a Look Back at 2019, Discussing Teal, Edge, Quantum Computing, and more

Idit Levine

Today on The InfoQ Podcast, Wes Reisz speaks with CEO and founder of Solo Idit Levine. The two discuss the Three Pillars of Solo around Gloo, their API gateway, interoperability of service meshes (including the work on Service Mesh Interface), and on extending Envoy with Web Assembly (and the recently announced Web Assembly Hub).Why listen to this podcast: - Gloo is a Kubernetes-native ingress controller and API gateway. It’s built on top of Envoy and at its core is open source. - The Service Mesh Interface (SMI) is a specification for service meshes that runs on Kubernetes. It defines a common standard that can be implemented by a variety of providers. The idea of SMI is it’s an abstraction on top of service meshes, so that you can use one language to configure them all. - Autopilot is an open-source Kubernetes operator that allows developers to extend a service mesh control plane.  - Lua has been commonly used to extend the service mesh data plane. Led by Google and the Envoy community, web assembly is becoming the preferred way of extending the data plane. Web assembly allows you to write Envoy extensions in any language while still being sandboxed and performant. - WebAssembly Hub is a service for building, deploying, sharing, and discovering Wasm extensions for Envoy. - Wasme is a docker like an open-source commandline tool from Solo to simplify the building, pushing, pulling, and deploying Envoy Web Assembly Filters.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/37sYIoEYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/37sYIoE

Today on The InfoQ Podcast, Wes Reisz speaks with CEO and founder of Solo Idit Levine. The two discuss the Three Pillars of Solo around Gloo, their API gateway, interoperability of service meshes (including the work on Service Mesh Interface), and on extending Envoy with Web Assembly (and the recently announced Web Assembly Hub). Why listen to this podcast: - Gloo is a Kubernetes-native ingress controller and API gateway. It’s built on top of Envoy and at its core is open source. - The Service Mesh Interface (SMI) is a specification for service meshes that runs on Kubernetes. It defines a common standard that can be implemented by a variety of providers. The idea of SMI is it’s an abstraction on top of service meshes, so that you can use one language to configure them all. - Autopilot is an open-source Kubernetes operator that allows developers to extend a service mesh control plane. - Lua has been commonly used to extend the service mesh data plane. Led by Google and the Envoy community, web assembly is becoming the preferred way of extending the data plane. Web assembly allows you to write Envoy extensions in any language while still being sandboxed and performant. - WebAssembly Hub is a service for building, deploying, sharing, and discovering Wasm extensions for Envoy. - Wasme is a docker like an open-source commandline tool from Solo to simplify the building, pushing, pulling, and deploying Envoy Web Assembly Filters. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/37sYIoE" rel="nofollow" target="_blank">https://bit.ly/37sYIoE</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/37sYIoE" rel="nofollow" target="_blank">https://bit.ly/37sYIoE</a>

Idit Levine Discussing Gloo, Service Mesh Interface, and Web Assembly Hub

Randy Shoup

In this week's podcast QCon chair Wesley Reisz talks to Randy Shoup. Shoup is the vice president of engineering at Stitch Fix. Prior to Stitch Fix, he worked for Google as the director of engineering and cloud computing, CTO and co-founder of Shopilly, and chief engineer at Ebay.Why listen to this podcast: - Stitch Fix's business is a combination of art and science. Humans are much better with the machines, and the machines are much better with the humans. - Stitch Fix has 60 engineers, with 80 data scientists and algorithm developers. This ratio of data science to engineering is unique. - With Ruby-on-Rails on top of Postgres, the company maintains about 30 different applications on the same stack. - The practice of Test Driven Development makes Continuous Delivery work, and the practice of having the same people build the code as those who operate the code makes both of these things much more powerful. - Microservices gives feature velocity, the ability for individual teams to move quickly and independently of each other, and independent deployments. - Microservices solve a scaling problem. They solve an organisational scaling problem, and a technological scaling problem. These are not the problems that you have early on in the startup. - In the monolithic world, if you're not able to continue to vertically scale the application or the database or whatever your monolith is. And so for scaling reasons alone you might consider breaking it up into what we call microservices.  Notes and links can be found on http://bit.ly/randy-shoup-podcast  Data Science and Stitch Fix  1m:57s - Stitch Fix re-imagines retail, particularly for clothing. When you sign up, you fill out survey of the kinds of things that you like and you don't like, and we choose what we think you're going to enjoy based on the millions of customers that we have already. And we use a ton of data science in that process. 3m:00s - That goes into our algorithms and then our algorithms make personalised recommendations based on all the things we know about our other customers... there's a human element as well: we have 3,200 human stylists that are all around the United States and they choose the five items that go into the box [of clothing]. 3m:29s - What we like is that this is a combination of art and science. Modern companies combine what machines are really good at, such as chugging through the 60 to 70 questions times the millions of customers, and combining that with the human element of the stylists, figuring out what things go together, what things are trending, what things are appropriate... Humans are much better with the machines, and the machines are much better with the humans.[...]  More on this: Quick scan our curated show notes on InfoQ. http://bit.ly/randy-shoup-podcast You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

In this week's podcast QCon chair Wesley Reisz talks to Randy Shoup. Shoup is the vice president of engineering at Stitch Fix. Prior to Stitch Fix, he worked for Google as the director of engineering and cloud computing, CTO and co-founder of Shopilly, and chief engineer at Ebay. Why listen to this podcast: - Stitch Fix's business is a combination of art and science. Humans are much better with the machines, and the machines are much better with the humans. - Stitch Fix has 60 engineers, with 80 data scientists and algorithm developers. This ratio of data science to engineering is unique. - With Ruby-on-Rails on top of Postgres, the company maintains about 30 different applications on the same stack. - The practice of Test Driven Development makes Continuous Delivery work, and the practice of having the same people build the code as those who operate the code makes both of these things much more powerful. - Microservices gives feature velocity, the ability for individual teams to move quickly and independently of each other, and independent deployments. - Microservices solve a scaling problem. They solve an organisational scaling problem, and a technological scaling problem. These are not the problems that you have early on in the startup. - In the monolithic world, if you're not able to continue to vertically scale the application or the database or whatever your monolith is. And so for scaling reasons alone you might consider breaking it up into what we call microservices. Notes and links can be found on <a href="http://bit.ly/randy-shoup-podcast" rel="nofollow" target="_blank">http://bit.ly/randy-shoup-podcast</a> Data Science and Stitch Fix 1m:57s - Stitch Fix re-imagines retail, particularly for clothing. When you sign up, you fill out survey of the kinds of things that you like and you don't like, and we choose what we think you're going to enjoy based on the millions of customers that we have already. And we use a ton of data science in that process. 3m:00s - That goes into our algorithms and then our algorithms make personalised recommendations based on all the things we know about our other customers... there's a human element as well: we have 3,200 human stylists that are all around the United States and they choose the five items that go into the box [of clothing]. 3m:29s - What we like is that this is a combination of art and science. Modern companies combine what machines are really good at, such as chugging through the 60 to 70 questions times the millions of customers, and combining that with the human element of the stylists, figuring out what things go together, what things are trending, what things are appropriate... Humans are much better with the machines, and the machines are much better with the humans. [...] More on this: Quick scan our curated show notes on InfoQ. <a href="http://bit.ly/randy-shoup-podcast" rel="nofollow" target="_blank">http://bit.ly/randy-shoup-podcast</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a>

Randy Shoup on Stitch Fix's Technology Stack,  Data Science and Microservices

Caitie McCaffrey

In this week's podcast, QCon chair Wes Reisz and Werner Schuster talk to Caitie McCaffrey. McCaffrey works on distributed systems with the engineering effectiveness team at Twitter, and has experience building the large scale services and systems that power the entertainment industry at 343 Industries, Microsoft Game Studios, and HBO. McCaffrey's presentation at QCon New York was called The Verification of a Distributed System.Why listen to this podcast:- Twitter's engineering effectiveness team aims to help make dev tools better, and make developers happier and more efficient.- Asking someone to speak at your conference or join your team solely because of their gender does more harm than people think.- There is not one prescriptive way to make good, successful technology.- Even when we don't have time for testing, there are options to increase your confidence in your system.- The biggest problem when running a unit test is that it is only testing the input you hard code into the unit test.Notes and links can be found on http://bit.ly/2al6BRpEngineering Effectiveness1:24 - The purpose of the engineering effectiveness team is to help make dev tools better, and to make Twitter's developers happier and more efficient.2:44 - The team is trying to make infrastructure so that not every team has to solve the distributed problem on their own, and give developers some APIs and tools so that they can build systems easily.More on this:Quick scan our curated show notes on InfoQ. http://bit.ly/2al6BRpYou can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq

In this week's podcast, QCon chair Wes Reisz and Werner Schuster talk to Caitie McCaffrey. McCaffrey works on distributed systems with the engineering effectiveness team at Twitter, and has experience building the large scale services and systems that power the entertainment industry at 343 Industries, Microsoft Game Studios, and HBO. McCaffrey's presentation at QCon New York was called The Verification of a Distributed System. Why listen to this podcast: - Twitter's engineering effectiveness team aims to help make dev tools better, and make developers happier and more efficient. - Asking someone to speak at your conference or join your team solely because of their gender does more harm than people think. - There is not one prescriptive way to make good, successful technology. - Even when we don't have time for testing, there are options to increase your confidence in your system. - The biggest problem when running a unit test is that it is only testing the input you hard code into the unit test. Notes and links can be found on <a href="http://bit.ly/2al6BRp" rel="nofollow" target="_blank">http://bit.ly/2al6BRp</a> Engineering Effectiveness 1:24 - The purpose of the engineering effectiveness team is to help make dev tools better, and to make Twitter's developers happier and more efficient. 2:44 - The team is trying to make infrastructure so that not every team has to solve the distributed problem on their own, and give developers some APIs and tools so that they can build systems easily. More on this: Quick scan our curated show notes on InfoQ. <a href="http://bit.ly/2al6BRp" rel="nofollow" target="_blank">http://bit.ly/2al6BRp</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">http://bit.ly/24x3IVq</a>

Caitie McCaffrey on Engineering Effectiveness, Diversity, & Verification of Distributed Systems

Rod Johnson

Today on The InfoQ Podcast, Wes talks with Rod Johnson. Rod is famously responsible for the creation of the Spring Framework. The two talk about the early years of the framework and provides some of the history of its creation. After discussing Spring, Wes and Rod discuss languages he’s been involved with since Java (these include Scala and TypeScript). He talks a bit about what he liked (and didn’t like) about each. Finally, the two wrap by discussing Atomist and how they’re trying to change the idea of software delivery from a statically defined pipeline (located in individual repositories) to an event hub that drives a series of actions for software delivery. He describes this as creating an API for your software.Why listen to this podcast: - The initial origins of the Spring Framework really came about through a process of trying to write a really great book about J2EE in 2002. It was through that process that Rod Johnson found he felt there was a better way and ultimately lead to the creation of the Spring Framework. - What started as examples and references, became the Spring Framework. By 2005 there were about 2 million downloads of the Spring Framework.After leaving VMWare in 2013, Rod spent several years working with Scala. One of the elegant features that really attracted Rod to Scala was how everything is an expression. One of the things he didn’t like was an affinity to overly complex approaches to problem solving. - Today at Atomist, Rod does a lot of work in Node. He really enjoys the robust extra layer of typing over a dynamic language and the ability to escape to JavaScript if needed (similar to escaping types with reflection in Java found in the internals of the Spring Framework). - Atomist, the company he founded after leaving VMWare, is rethinking CI/CD from a static pipeline defined in every repository to an event-driven system that defines how to respond to specific events (such as a push from Git). For example, all pushes with Spring Boot can be configured to be scanned with SonarQube or because a push has kubespec it might get deployed to a K8 cluster. He describes this as creating an API for your software. - One of the reasons Atomist integrates so tightly with Slack (and other similar messaging platforms) is because it allows developers to shape their own relevant messages. By joining (or leaving channels), people are able to subscribe to only the information they actually want. Meeting developers inside Slack is an important interface for Atomist.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2FxK3xfYou 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/infoqCheck the landing page on InfoQ: https://bit.ly/2FxK3xf

Today on The InfoQ Podcast, Wes talks with Rod Johnson. Rod is famously responsible for the creation of the Spring Framework. The two talk about the early years of the framework and provides some of the history of its creation. After discussing Spring, Wes and Rod discuss languages he’s been involved with since Java (these include Scala and TypeScript). He talks a bit about what he liked (and didn’t like) about each. Finally, the two wrap by discussing Atomist and how they’re trying to change the idea of software delivery from a statically defined pipeline (located in individual repositories) to an event hub that drives a series of actions for software delivery. He describes this as creating an API for your software. Why listen to this podcast: - The initial origins of the Spring Framework really came about through a process of trying to write a really great book about J2EE in 2002. It was through that process that Rod Johnson found he felt there was a better way and ultimately lead to the creation of the Spring Framework. - What started as examples and references, became the Spring Framework. By 2005 there were about 2 million downloads of the Spring Framework. After leaving VMWare in 2013, Rod spent several years working with Scala. One of the elegant features that really attracted Rod to Scala was how everything is an expression. One of the things he didn’t like was an affinity to overly complex approaches to problem solving. - Today at Atomist, Rod does a lot of work in Node. He really enjoys the robust extra layer of typing over a dynamic language and the ability to escape to JavaScript if needed (similar to escaping types with reflection in Java found in the internals of the Spring Framework). - Atomist, the company he founded after leaving VMWare, is rethinking CI/CD from a static pipeline defined in every repository to an event-driven system that defines how to respond to specific events (such as a push from Git). For example, all pushes with Spring Boot can be configured to be scanned with SonarQube or because a push has kubespec it might get deployed to a K8 cluster. He describes this as creating an API for your software. - One of the reasons Atomist integrates so tightly with Slack (and other similar messaging platforms) is because it allows developers to shape their own relevant messages. By joining (or leaving channels), people are able to subscribe to only the information they actually want. Meeting developers inside Slack is an important interface for Atomist. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/2FxK3xf" rel="nofollow" target="_blank">https://bit.ly/2FxK3xf</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/2FxK3xf" rel="nofollow" target="_blank">https://bit.ly/2FxK3xf</a>

Rod Johnson Chats about the Spring Framework Early Days, Languages Post-Java, & Rethinking CI/CD

Joe Beda

Today on The InfoQ Podcast, Wes talks with Joe Beda. Joe is one of the co-creators of Kubernetes. What started in the fall of 2013 with Craig McLuckie, Joe Beda, and Brendan Burns working on cloud infrastructure has become the default orchestrator for cloud native architectures. Today on the show, the two discuss the recent purchase of Heptio by VMWare, the Kubernetes Privilege Escalation Flaw (and the response to it), Kubernetes Enhancement Proposals, the CNCF/organization of Kubernetes, and some of the future hopes for the platform.Why listen to this podcast: - Heptio, the company Joe and Craig McLuckie co-founded, viewed themselves as not a Kubernetes company, but more of a cloud native company. Joining VMWare allowed the company to continue a mission of helping people decouple “moving to cloud/taking advantage of cloud” patterns (regardless of where you’re running). - Re:Invent 2017 when EKS was announced was a watershed moment for Kubernetes. It marked a time where enough customers were asking for Kubernetes that the major cloud providers started to offer first-class support. - Kubernetes 1.13 included a patch for the Kubernetes Privilege Escalation Flaw Patch. While the flaw was a bad thing, it demonstrated product maturity in the way the community-based security response. - Kubernetes has an idea of committees, sigs, and working groups. Security is one of the committees. There were a small group of people who coordinated the security response. From there, trusted sets of vendors validated and test patches. Most of the response is based on how many other open source projects handle security response. - Over the last couple of releases, Kubernetes has introduced a Sig Architecture special interest group. It’s an overarching review for changes that sweep across Kubernetes. As part of Sig Architecture, the Kubernetes community has introduced Kubernetes Enhancement Proposal process (or KEPs). It’s a way for people to propose architectural changes to Kubernetes. - The goal of the CNCF is to curate and provide support to a set of projects (of which Kubernetes is one). The TOC (Technical Oversight Committee) decides which projects are going to be part of the CNCF and how those projects are supported. - Kubernetes was always viewed by the creators as something to be build on. It was never really viewed as the end goal.You 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/infoq

Today on The InfoQ Podcast, Wes talks with Joe Beda. Joe is one of the co-creators of Kubernetes. What started in the fall of 2013 with Craig McLuckie, Joe Beda, and Brendan Burns working on cloud infrastructure has become the default orchestrator for cloud native architectures. Today on the show, the two discuss the recent purchase of Heptio by VMWare, the Kubernetes Privilege Escalation Flaw (and the response to it), Kubernetes Enhancement Proposals, the CNCF/organization of Kubernetes, and some of the future hopes for the platform. Why listen to this podcast: - Heptio, the company Joe and Craig McLuckie co-founded, viewed themselves as not a Kubernetes company, but more of a cloud native company. Joining VMWare allowed the company to continue a mission of helping people decouple “moving to cloud/taking advantage of cloud” patterns (regardless of where you’re running). - Re:Invent 2017 when EKS was announced was a watershed moment for Kubernetes. It marked a time where enough customers were asking for Kubernetes that the major cloud providers started to offer first-class support. - Kubernetes 1.13 included a patch for the Kubernetes Privilege Escalation Flaw Patch. While the flaw was a bad thing, it demonstrated product maturity in the way the community-based security response. - Kubernetes has an idea of committees, sigs, and working groups. Security is one of the committees. There were a small group of people who coordinated the security response. From there, trusted sets of vendors validated and test patches. Most of the response is based on how many other open source projects handle security response. - Over the last couple of releases, Kubernetes has introduced a Sig Architecture special interest group. It’s an overarching review for changes that sweep across Kubernetes. As part of Sig Architecture, the Kubernetes community has introduced Kubernetes Enhancement Proposal process (or KEPs). It’s a way for people to propose architectural changes to Kubernetes. - The goal of the CNCF is to curate and provide support to a set of projects (of which Kubernetes is one). The TOC (Technical Oversight Committee) decides which projects are going to be part of the CNCF and how those projects are supported. - Kubernetes was always viewed by the creators as something to be build on. It was never really viewed as the end goal. You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a>

Joe Beda on Kubernetes & the CNCF

Greg Law

In this podcast, Daniel Bryant sat down with Greg Law, CTO at Undo. Topics discussed included: the challenges with debugging modern software systems, the need for “hyper-observability” and the benefit of being able to record and replay exact application execution; and the challenges with implementing the capture of nondeterministic system data in Undo’s LiveRecorder product for JVM-based languages that are Just-In-Time (JIT) compiled.Why listen to this podcast: - Understanding modern software systems can be very challenging, especially when the system is not doing what is expected. When debugging an issue, being able to observe a system and look at logging output is valuable, but it doesn’t always provide all of the information a developer needs. Instead we may need “hyper observability”; the ability to “zoom into” bugs and replay an exact execution. - Being able to record all nondeterministic stimuli to an application -- such as user input, network traffic, interprocess signals, and threading operations -- allows for the replay of an exact execution of an application for debugging purposes. Execution can be paused, rewound, and replayed, and additional logging data can be added ad hoc. - Undo’s LiveRecorder allows for the capture of this nondeterministic data, and this can be exported and shared among development teams. The UndoDB debugger, which is based on the GNU Project Debugger, supports the loading of this data and the execution and debugging in forwards and reverse execution of the application. There is also support for other debuggers, such as that included within IntelliJ IDEA. - Advanced techniques like multi-process correlation reveal the order in which processes and threads alter data structures in shared memory, and thread fuzzing randomizes thread execution to reveal race conditions and other multi-threading defects. - The challenges of using this type of technology when debugging (micro)service-based application lies within the user experience i.e. how should the multiple process debugging experience be presented to a developer?Live Recorder currently supports C/C++, Go, Rust, Ada applications on Linux x86 and x86_64, with Java support available in alpha. Supporting the capture and replay of data associated with JVM language execution, which contain extra abstractions and are often Just-In-Time (JIT) compiled, presented extra challenges.More on this: Quick scan our curated show notes on InfoQ https://bit.ly/37XLUa0You 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/infoqCheck the landing page on InfoQ: https://bit.ly/37XLUa0

In this podcast, Daniel Bryant sat down with Greg Law, CTO at Undo. Topics discussed included: the challenges with debugging modern software systems, the need for “hyper-observability” and the benefit of being able to record and replay exact application execution; and the challenges with implementing the capture of nondeterministic system data in Undo’s LiveRecorder product for JVM-based languages that are Just-In-Time (JIT) compiled. Why listen to this podcast: - Understanding modern software systems can be very challenging, especially when the system is not doing what is expected. When debugging an issue, being able to observe a system and look at logging output is valuable, but it doesn’t always provide all of the information a developer needs. Instead we may need “hyper observability”; the ability to “zoom into” bugs and replay an exact execution. - Being able to record all nondeterministic stimuli to an application -- such as user input, network traffic, interprocess signals, and threading operations -- allows for the replay of an exact execution of an application for debugging purposes. Execution can be paused, rewound, and replayed, and additional logging data can be added ad hoc. - Undo’s LiveRecorder allows for the capture of this nondeterministic data, and this can be exported and shared among development teams. The UndoDB debugger, which is based on the GNU Project Debugger, supports the loading of this data and the execution and debugging in forwards and reverse execution of the application. There is also support for other debuggers, such as that included within IntelliJ IDEA. - Advanced techniques like multi-process correlation reveal the order in which processes and threads alter data structures in shared memory, and thread fuzzing randomizes thread execution to reveal race conditions and other multi-threading defects. - The challenges of using this type of technology when debugging (micro)service-based application lies within the user experience i.e. how should the multiple process debugging experience be presented to a developer? Live Recorder currently supports C/C++, Go, Rust, Ada applications on Linux x86 and x86_64, with Java support available in alpha. Supporting the capture and replay of data associated with JVM language execution, which contain extra abstractions and are often Just-In-Time (JIT) compiled, presented extra challenges. More on this: Quick scan our curated show notes on InfoQ <a href="https://bit.ly/37XLUa0" rel="nofollow" target="_blank">https://bit.ly/37XLUa0</a> You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. <a href="http://bit.ly/24x3IVq" rel="nofollow" target="_blank">bit.ly/24x3IVq</a> Subscribe: <a href="http://www.youtube.com/infoq" rel="nofollow" target="_blank">www.youtube.com/infoq</a> Like InfoQ on Facebook: <a href="http://bit.ly/2jmlyG8" rel="nofollow" target="_blank">bit.ly/2jmlyG8</a> Follow on Twitter: <a href="http://twitter.com/InfoQ" rel="nofollow" target="_blank">twitter.com/InfoQ</a> Follow on LinkedIn: <a href="http://www.linkedin.com/company/infoq" rel="nofollow" target="_blank">www.linkedin.com/company/infoq</a> Check the landing page on InfoQ: <a href="https://bit.ly/37XLUa0" rel="nofollow" target="_blank">https://bit.ly/37XLUa0</a>

Greg Law on Debugging, Record & Replay of Data, and Hyper-Observability

The best episodes for anyone looking to learn more about topics such as happiness, fulfillment, depression and psychology/mental health in general. With interviews with industry experts, personal stories of individuals, this topic has lessons applicable to everyone. Add episodes you're interested into your queue below!

Best Episodes on Mental Health, Emotions & Thoughts

The best podcast episodes on physical health. Episodes talk about your diet, sleep, exercise and all the things that people do to improve their physical health and live a healthier life. This topic is for everyone, with applications in all of our everyday lives. Add episodes you're interested into your queue below!