Podcast: Play in new window | Download
http://traffic.libsyn.com/sedaily/2018_02_14_ProductionMLSystems.mp3Podcast: Play in new window | Download Pinterest is a visual feed of ideas, products, clothing, and recipes. Millions of users browse Pinterest to find images and text that are tailored to their interests. Like most companies, Pinterest started with a large monolithic application that served all requests. As Pinterest’s engineering resources expanded, some of the architecture was broken up into microservices and Dockerized, which make the system easier to
http://traffic.libsyn.com/sedaily/2018_02_01_MicroservicesZhamakDehgani.mp3Podcast: Play in new window | Download On this show, we spend a lot of time talking about CI/CD, data engineering, and microservices. These technologies have only been widely talked about for the last 5-10 years. That means that they are easy to adopt for startups that get founded in the last 5-10 years, but not necessarily for older enterprises. Within a large enterprise, it can be challenging to make
http://traffic.libsyn.com/sedaily/CassandraShum.mp3Podcast: Play in new window | Download Many companies are transitioning from a monolith to microservices architecture. Tools for cloud computing, containerization, and continuous delivery are making this easier. But there are still technological and organizational challenges that a company will encounter while making this transition. Cassandra Shum is an engineer with ThoughtWorks. She has worked with major financial institutions and other large companies to architect their migrations from monolith
http://traffic.libsyn.com/sedaily/microservicesmacro_edited.mp3Podcast: Play in new window | Download The word “microservices” started getting used after a series of events–companies were moving to cloud virtual machines. Those VMs got broken up into containers, and the containers can fit to the size of the service. Services that are more narrowly defined take up smaller containers, and can be packed more densely into the virtual machines–hence the term “microservices.” As this change to software
http://traffic.libsyn.com/sedaily/developing_reactive_microservices_edited.mp3Podcast: Play in new window | Download The goals of microservices are the same as what we have pursued in software engineering for decades: isolation, decoupling, maintainability, scalability. The reason that we use the term microservices is not because we have a completely different idea of what a service is than we used to. We use the term microservices because we are signaling that we need to achieve these architectural
http://traffic.libsyn.com/sedaily/reactivemicroservices_edited.mp3Podcast: Play in new window | Download For many years, software companies have been breaking up their applications into individual services for the purpose of isolation and maintainability. In the early 2000s, we called this pattern “service-oriented architecture”. Today we call it “microservices”. Why did we change that terminology? Did the services get smaller? Not exactly. Jonas Boner suggests that the movement towards cloud and the increased prevalence of mobile
http://traffic.libsyn.com/sedaily/microservices_tools_edited.mp3Podcast: Play in new window | Download Microservices are a widely adopted pattern for breaking an application up into pieces that can be well-understood by the individual teams within the company. Microservices also allow these individual pieces to be scaled independently and updated in isolation. Past Software Engineering Daily episodes have covered the microservice architectures of Twitter, Netflix, Google, Uber and other companies. In today’s episode, I sit down with
http://traffic.libsyn.com/sedaily/distributed_tracing_edited_fixed.mp3Podcast: Play in new window | Download In a microservices architecture, a user request will often make its way through several different services before it returns a result to the end user. If a user experiences a failed request, the root cause could be in any of the services along that request path. Even more problematic is the challenge of debugging latency in this kind of request chain. Reshmi
http://traffic.libsyn.com/sedaily/github_edited_fixed.mp3Podcast: Play in new window | Download github has grown to have 10 million users and 30 million repositories. Getting to this scale has required innovation in many places–github has significantly altered the code for git itself, and has built unique infrastructure and written low level code to architect for git repository management at scale. Despite the need for cutting-edge technologies to support github, the development culture at github
http://traffic.libsyn.com/sedaily/Bouyant_Edited.mp3Podcast: Play in new window | Download Six years ago, Twitter was experiencing outages due to high traffic. Back in 2010 Twitter was built as a monolithic Ruby on Rails application. Twitter migrated to a microservices architecture to fix these problems. During this migration, the engineers at Twitter learned how to build and scale highly distributed microservice architectures. William Morgan was an engineer at Twitter during that time, and he
http://traffic.libsyn.com/sedaily/Cimpress_Edited_2.mp3Podcast: Play in new window | DownloadMass customization is the process of making customized, personalized products that are accessible to individuals and small businesses. The process involves manufacturing, assembly lines, supply chains, and software at every step along the way. Today’s guests are Jim Sokoloff and Maarten Wensveen, who work on infrastructure and technology at Cimpress, a mass customization platform. Cimpress has t shirt printers, warehousing machines, supply chain management
http://traffic.libsyn.com/sedaily/Algorithmia_Edited.mp3Podcast: Play in new window | Download Algorithmia is marketplace for algorithms. A software engineer who writes an algorithm for image processing or spam detection or TF-IDF can turn that algorithm into a RESTful API to be consumed by other developers. Different algorithms can be composed together to build even higher level applications. Diego Oppenheimer is the CEO of Algorithmia, and he joins the show today to explain how Algorithmia
http://traffic.libsyn.com/sedaily/Ride_Edited.mp3Podcast: Play in new window | Download “With any system, whether it’s an organization or a biological system, or an information system, communication is always going to be a challenge. And how pieces of the system communicate will have a direct impact on how effective impact on how effective or efficient that organism or organization is.” In today’s episode, Ben Halpern interviews Juan Buritica, VP of Engineering at Ride. They
http://traffic.libsyn.com/sedaily/Segment_Edited.mp3Podcast: Play in new window | Download “Its sort of like the old joke in computer science – what do you do when you have a problem? Well, add a layer of abstraction.” Today’s guest is Calvin French-Owen, the CTO of Segment, a tool that companies use to aggregate their analytics into once place. As Segment has scaled, the company has had to restructure its etire technical architecture. Microservices, containers,
“You can have a monolith, and it can be a perfectly good thing.”
“By the time I joined, people were already starting to have this microservice fatigue.”
Distributed systems programming will always be a world of tradeoffs — there is no silver bullet in the future. But life can be made easier with tactics such as the actor pattern and the use of conflict-free replicated data types (CRDTs).
Caitie McCaffrey is a distributed systems engineer who currently works at Twitter. She previously worked on Halo 4 at Microsoft and 343 Industries. At QCon San Francisco, she will be hosting the track Taming Distributed Architecture.
What is DevOps? DevOps was an unclear term at the beginning of the week. Depending on who you ask, DevOps is: the agile manifesto applied to sysadmin the applied version of The Lean Enterprise the people who manage tools like Jenkins and containers Does the DevOps role actually exist? DevOps is a loose cultural thing, like agile. “DevOps” engineers are often software engineers or operations people that have been rebranded with minor change
http://traffic.libsyn.com/sedaily/docker_turnbull.mp3Podcast: Play in new window | Download Microservices on container architecture lead to effective workflows associated with DevOps. Docker containers wrap up a piece of software in a complete filesystem that contains everything it needs to run. This allows for quick flexibility and scaleability in business applications, a key driver of the DevOps methodology. James Turnbull is VP of engineering at Kickstarter, an advisor at Docker and author of The Docker Book.
http://traffic.libsyn.com/sedaily/joyent_bcantrill_fixed.mp3Podcast: Play in new window | Download Container infrastructure has benefits of security, scalability and efficiency. Containers are a central component of the DevOps movement. Joyent provides simple, secure deployment of containers with bare metal speed on container-native infrastructure Bryan Cantrill is the CTO of Joyent, the father of DTrace and an OS kernel developer for 20 years. Questions: Why are containers relevant to DevOps? Why are containers advantageous to