Software Engineering Daily

Software Engineering Daily

By Software Engineering DailyNewsTechnologyTech News
Download on the App Store

Software Engineering Daily episodes

  • Distributed Systems with Leslie Lamport
    This episode is a republication from my interview with Leslie Lamport on Software Engineering Radio. Leslie Lamport won a Turing Award in 2013 for his work in distributed and concurrent systems. He also designed the document preparation tool LaTex. Leslie is employed by Microsoft Research, and has recently been working with TLA+, a language that is useful for specifying concurrent systems from a high level. The interview begins with a definition:Continue reading...
    51 min
  • Engineering Cloud Services with Sam Kottler

    “A lot of our customers are kind of AWS refugees who really don’t want all the stuff amazon has, and they just want a really easy to use system that is reliable.”

    Operating a data center has been turned into a service. For most new companies, managing real-world servers is no longer an issue. But one exception is if your startup is a company offering the data center as a service. In this episode, Jeff and Sam talk about the engineering that goes on at DigitalOcean, and how the company differentiates itself from its competitors.

    Sam Kottler is an engineering manager at DigitalOcean, and previously worked at Red Hat.

    Questions
    • What were my options before DigitalOcean was created?
    • If I choose to go with DigitalOcean over AWS, what are the tradeoffs I am making?
    • What happens on DigitalOcean’s end when I spin up a droplet on the online portal?
    • What economies of scale could you get if you moved all droplets from VMs to containers?
    • What happens when the server my droplet is on dies?
    • Can you talk about a distributed systems problem that you’ve dealt with that seemed unbelievable?
    • What’s in the future for DigitalOcean?
      • Links
      • DigitalOcean
      • Google File System paper
      • Twilio
      • How to Debug Anything
      • MySQL
      • Sam on Twitter

        • The post Engineering Cloud Services with Sam Kottler appeared first on Software Engineering Daily.

        48 min
      • Moving to Microservices at SoundCloud with Lukasz Plotnicki

        “You can have a monolith, and it can be a perfectly good thing.”

        Monoliths versus microservices – the architectural debate continues across the internet. SoundCloud is a popular music company that experienced the rapid development benefits of a monolith, as well as the long-term technical debt. That technical debt has since been relieved by a move towards microservices. In this episode of Software Engineering Daily, Lukasz joins Jeff to talk about the realities of moving from a monolith to a microservices architecture, and walks through the lessons learned at SoundCloud.

        Lukasz Plotnicki is a consultant and software engineer at ThoughtWorks, which helps clients address their software development challenges and needs.

        Questions
        • What are the application requirements of SoundCloud?
        • Is there something about Rails that lends towards apps becoming monolithic?
        • How did SoundCloud gradually ease into using microservice architecture?
        • How did the variety of front-end interfaces affect SoundCloud’s monolithic architecture?
        • What is the difference between a BFF and a microservice?
        • What are the downsides of a BFF implementation?
        • What are the lessons the SoundCloud case study has taught you about software architecture?
          • Links
          • SoundCloud
          • BFF @ SoundCloud
          • Thoughtworks
          • Monolithic application
          • How we ended up with microservices
          • The Strangler Pattern
          • Bounded Context
          • Domain-driven design
          • Lukasz on Twitter

            • The post Moving to Microservices at SoundCloud with Lukasz Plotnicki appeared first on Software Engineering Daily.

            47 min
          • Engineering at Quora with Shreyes Seshasai

            “If an engineer is doing something repeatedly over and over again, their mind is immediately going to jump to that place where it’s like ‘Okay how can I make this faster?’ or ‘How can I save myself time?’”

            Quora is a Q&A website where questions are asked, answered, edited and organized by its community of users.

            Shreyes Seshasai is the Director of Engineering at Quora.

            Questions
            • Is there a false dichotomy between development velocity and code quality?
            • What does it mean to “move fast at average”?
            • How do you incentivize people to automate?
            • Why does Quora engineering not have pre-commit code reviews?
            • How do you handle testing for desktop, iOS and Android?
            • What are Webnode and Livenode?
            • What is the relationship between engineering and design teams at Quora?
              • Links
              • Moving Fast With High Code Quality
              • Quora’s Approach To Moving Fast Sustainably
              • Tech Talk – webnode2 and LiveNode
              • Amazon Redshift
              • Shreyes on Twitter
                • Sponsors

                Hired.com is the job marketplace for software engineers. Go to hired.com/softwareengineeringdaily to get a $600 bonus upon landing a job through Hired.

                Digital Ocean is the simplest cloud hosting provider. Use promo code SEDAILY for $10 in free credit.

                The post Engineering at Quora with Shreyes Seshasai appeared first on Software Engineering Daily.

                52 min
              • Engineering at Quora with Shreyes Seshasai
                “If an engineer is doing something repeatedly over and over again, their mind is immediately going to jump to that place where it’s like ‘Okay how can I make this faster?’ or ‘How can I save myself time?’” Quora is a Q&A website where questions are asked, answered, edited and organized by its community of users. Shreyes Seshasai is the Director of Engineering at Quora. Questions Is there a falseContinue reading...
                54 min
              • Scaling Uber with Matt Ranney

                “If you can make a system that can survive this random failure testing, then you will more or likely survive whatever other chaotic conditions exist.”

                Uber is a transportation and logistics company that manages many aspects of its ride-sharing services through mobile apps and distributed technology. Uber faces unique challenges in rapidly scaling its services internationally, and at one point increased its developer headcount from 200 to over 1000 in less than a year.

                Matt Ranney is the Chief Systems Architect at Uber and was previously a founder and CTO of Voxer. At QCon San Francisco, he gave a talk called Scaling Uber.

                Questions
                • How did technical debt accumulate at Uber in the first five years?
                • Why do microservices offer a strategy to help alleviate technical debt?
                • Could you discuss immutable infrastructure?
                • What is Ringpop, and how does it help maintain state?
                • What are the service discovery problems you’ve had while scaling?
                • How have you “embraced the chaos” recently?
                  • Links
                  • Adopting Microservices at Netflix: Lessons for Architectural Design
                  • Ringpop
                  • SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol
                  • Jeff Dean: “Achieving Rapid Response Times in Large Online Services” Keynote
                  • The Netflix Simian Army
                    • Sponsors

                    Hired.com is the job marketplace for software engineers. Go to hired.com/softwareengineeringdaily to get a $600 bonus upon landing a job through Hired.

                    Digital Ocean is the simplest cloud hosting provider. Use promo code SEDAILY for $10 in free credit.

                    The post Scaling Uber with Matt Ranney appeared first on Software Engineering Daily.

                    45 min
                  • Netflix Genie with Tom Gianos

                    “Sometimes there’s a misconception that Genie is a job scheduling platform… Genie really represents our extraction layer, from what our computational resources are, to our end user jobs.”

                    Genie is an open-source tool that provides job and resource management for the Hadoop ecosystem in the cloud.

                    Tom Gianos is a Senior Software Engineer at Netflix focusing on its big data platform. He is one of the core contributors in charge of maintaining and improving Genie.

                    Questions
                    • How fast is the pace of Netflix data collection increasing?
                    • What are the differences between running Hadoop in the cloud and running it in a data center?
                    • Why is job and resource management so important for a Hadoop ecosystem?
                    • What does Netflix do with spare computational resources?
                    • What is a bonus cluster?
                    • Does Netflix collect more data than it can practically make use of?
                      • Links
                      • Genie
                      • Yarn – Resource Scheduling Layer
                      • Hadoop Platform as a Service in the Cloud
                      • SE Daily Episode on Presto
                      • Spring Boot

                        • The post Netflix Genie with Tom Gianos appeared first on Software Engineering Daily.

                        57 min

                      About Software Engineering Daily

                      From the publisher's feed

                      Technical interviews about software topics.