The O'Reilly Media Podcast spreads the knowledge of innovators. At O’Reilly, a big part of our business is paying attention to what’s new and interesting in the world of technology. The O'Reilly Media Podcast features interviews with the people working on the forefront of technology.

O'Reilly Media Podcast

Programming podcasts

podcast techno

technology

oreily

"Incremental change may be good theory, but in practice you have to have a big enough stick to hit everybody with to make everything move at once". So shares Adrian Cockcroft, who helped lead Netflix's migration from datacenter to the cloud -- and from monolithic to microservices architecture -- when their streaming business (the "stick"!) was exploding.

So how did they -- and how can other companies -- make such big, bet-the-company kind of moves, without getting mired in fanatical internal debates? Does organizational structure need to change, especially if moving from a more product-, than project-based, approach? What happens to security? And finally, what happens to the role of CIOs; what can/should they do?

Most interestingly: How will the entire industry be affected as companies not only adopt, but essentially offer, microservices or narrow cloud APIs? How do the trends of microservices, containers, devops, cloud, as-a-service/ on-demand, serverless -- all moves towards more and more ephemerality -- change the future of computing and even work? Cockcroft (who is now a technology fellow at Battery Ventures) joins this episode of the a16z Podcast, in conversation with Frank Chen and Martin Casado (and Sonal Chokshi) to discuss these shifts and more.

---

The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the enduring accuracy of the information or its appropriateness for a given situation.
 
This content is provided for informational purposes only, and should not be relied upon as legal, business, investment, or tax advice. You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments and certain publicly traded cryptocurrencies/ digital assets for which the issuer has not provided permission for a16z to disclose publicly) is available at https://a16z.com/investments/.

Charts and graphs provided within are for informational purposes solely and should not be relied upon when making any investment decision. Past performance is not indicative of future results. The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures for additional important information.

a16z Podcast: All About Microservices

Docker Distributed Systems Summit Opening Words by Solomon Hykes

Web service is a method of communication between two electronic devices over the internet. It follows the client server architecture. SOAP and REST are the two major classes of web services. SOAP stands for Simple Object Access Protocol and REST is the acronym for Representational State Transfer.

The key takeaways from this podcast are:

•	Understanding SOAP and REST Basics
•	Advantages and disadvantages of SOAP and REST web services
•	Difference between SOAP and REST web services
•	Choosing the best web service

About the speaker:
Mr. Vidhut Singh is a Technical Architect at MSys Technologies. He has over 10 years of experience in designing and developing Storage Host Integration products. He also has a sturdy expertise in storage integration with other enterprise products.

SOAP vs REST: Which is better and why? Expert speak..

In this episode of the O’Reilly podcast, Jon Bruner sat down with Rahul Kamdar, director of product management and strategy at TIBCO Software. They discussed the shift from the centralized enterprise service bus (ESB) to a distributed data architecture based on microservices, APIs, and cloud-native applications.

From Enterprise Service Bus to Microservices

In this episode of the Data Show, I spoke with Karthik Ramasamy, adjunct faculty member at UC Berkeley, former engineering manager at Twitter, and co-founder of Streamlio. Ramasamy managed the team that built Heron, an open source, distributed stream processing engine, compatible with Apache Storm.  While Ramasamy has seen firsthand what it takes to build and deploy large-scale distributed systems (within Twitter, he worked closely with the team that built DistributedLog), he is first and foremost interested in designing and building end-to-end applications. As someone who organizes many conferences, I’m all too familiar with the vast array of popular big data frameworks available. But, I also know that engineers and architects are most interested in content and material that helps them cut through the options and decisions.

Architecting and Building End-to-End Streaming Applications

In this podcast episode, O’Reilly’s Jeff Bleiel talks with Jan Machacek, CTO at Cake Solutions, a global consulting firm that specializes in building reactive systems. They discuss Machacek’s experiences in building reactive microservice-based systems and how these systems can help companies keep up with changing business demands.

Jan Machacek on Reactive Systems and Shifting Business Demands

In this episode of the Data Show, I spoke with Lukas Biewald, co-founder and chief data scientist at CrowdFlower. In a previous episode we covered how the rise of deep learning is fueling the need for large labeled data sets and high-performance computing systems. CrowdFlower has a service that many leading companies have come to rely on to provide them with labeled data sets to train machine learning models. As deep learning models get larger and more complex, they require training data sets that are bigger than those required by other machine learning techniques.

Data Preparation in the Age of Deep Learning

The growth of the consumer Internet has left many companies awash in analytics data. In this O’Reilly Podcast episode, I talk with William Plummer, chief strategy officer at TalkingData, about how to make sense of it.

Plummer’s key message is that companies need to embrace what he calls “smart data.” Smart data is an evolution of the “big data” idea that enterprises have been pursuing for about a decade now. Plummer links smart data to the two developments that have transformed the practice of data science over the last couple of decades: the arrival of nearly universal connectivity and the advent of the consumer internet.

Moving Beyond Big Data to Smart Data

In this episode of the O’Reilly Programming Podcast, I talk with Ben Evans, co-founder and technology fellow at JClarity, and co-author of the forthcoming O’Reilly book "Optimizing Java: Practical Techniques for Improved Performance Tuning." We discuss the upcoming release of Java 9, Java performance issues, and Evans’ experience as an organizer for the London Java Community.

Ben Evans on Java 9

In a recent episode of the O’Reilly Media Podcast, we spoke with George Miranda about the importance of service mesh technology in creating reliable distributed systems. As discussed in the new report The Service Mesh: Resilient Service-to-Service Communication for Cloud Applications, service mesh technology has emerged as a popular tool for companies looking to build cloud-native applications that are reliable and secure.

During the podcast, we discussed the problems a service mesh infrastructure solves and the service mesh features you’ll find most valuable. We also talked about how to choose the right service mesh for your organization, the challenges involved in getting it deployed to production, and the best ways for getting started with a service mesh.

How to Choose and Deploy a Service Mesh

In this episode of the O’Reilly Media Podcast, Rachel Roumeliotis, VP of content strategy at O’Reilly, sat down with Daniel Krook, IBM developer advocate. They discussed how developers across industries can participate in the Call for Code initiative, the benefits of the program, support from its charitable partners—United Nations Human Rights and the American Red Cross—and the positive impacts IBM hopes to achieve by investing in Call for Code.

Developers Worldwide Will Collaborate on Solutions to Save Lives in Call For Code

This episode of the O’Reilly Podcast, features a conversation on serverless and Kubernetes, with Kelsey Hightower, developer advocate for Google Cloud Platform at Google (and co-author of "Kubernetes: Up and Running"), and Chris Gaun, Kubernetes product marketing manager at Mesosphere.

Kelsey Hightower and Chris Gaun on Serverless and Kubernetes

At Google’s 2019 Cloud Next conference, I sat down with Stephen Thorne, site reliability engineer on Google’s customer reliability engineering team and co-author of "The Site Reliability Workbook," to talk about how organizations, both large and small, can use SRE to reduce operational costs, improve reliability, and create productive cross-functional teams.

How to Get Started With Site Reliability Engineering (SRE)

In this interview, Tim Craig and fellow Googler Gustavo Franco, a site reliability engineer (SRE), discuss the wide range of events that qualify as “incidents;” the need for a conscious, robust, and well-defined process for understanding them; the role of training; and how to get buy-in from management so you can spread incident response training throughout an organization.

Taming Chaos: Preparing for Your Next Incident

O'Reilly Media spreads the knowledge of innovators. At O’Reilly, a big part of our business is paying attention to what’s new and interesting in the world of technology. We have a pretty good record at having anticipated some of the big technology developments in recent history. For instance, we launched the first commercial Web site, GNN, in 1993; we organized the meeting at which the term “open source” was first adopted; we were early investors in Blogger, which helped launch the blogging revolution; and more recently, our Web 2.0 conference launched a world-wide meme. We call this predictive sense the “O’Reilly Radar.” And while we’re certainly not always right, we are, at least, good at making interesting guesses.

Our methodology is simple: we draw from the wisdom of the alpha geeks in our midst, paying attention to what’s interesting to them, amplifying these weak signals, and seeing where they fit into the innovation ecology. Add to that the original research conducted by our Research team, and you start to get a good picture of what the technology world is thinking about.

From Enterprise Service Bus to Microservices

O'Reilly Radar