You are viewing content from a past/completed QCon -

Presentation: Rethinking Applications for the NVM Era

Track: Hardware Frontiers: Changes Affecting Software Developers Today

Location: Pacific LMNO

Day of week: Tuesday

Slides: Download Slides

Level: Advanced

Persona: Developer

What You’ll Learn

  • Approaches to handling persistent objects in DRAM
  • How to handle failure in memory as if you were using a file system.

Abstract

Storage looks and feels like a block device hidden behind layers of abstractions - system calls, pagecaches, block device drivers and things we don't want to think about. This might change in the near future with the introduction of CPU accessible, byte addressable, persistent memory. How would your logging service, database or filesystem look in this world? Actually, would you need any of those or could a persistent C++ STL container be your storage service of choice?

Question: 

What is your motivation for this talk?

Answer: 

So the focus of this talk is about how do you re-architect your software to take advantage of the advances of software today. Many developers treats the serialization of objects as sort of a separate process something that hangs off the side where the object is out of flat file or disk. But now if your object lives in persistent memory how do you manage that? How do you update that in a consistent way so it's you know it's just constant even through power failures and so on. So most of the focus is on talking about how we write our software in the future when our DRAM is persistent.

Question: 

Who should come to your talk?

Answer: 

Somebody who writes C++ could but might be curious about what non-volatile memory might mean for them. So for instance maybe somebody who is developing a boost library and wants to use non-volatile memory and also wants to know what NVM is doing under the hood.

Question: 

What can people come take away from this talk?

Answer: 

So I'm going to sort of start by talking about general principles. C had sort of an object layout in memory and if the the memory was persistent, how would you manipulate that in a failure atomically? What does it means if I'm inserting a node of a red/black tree and now pull power in between, how do I ensure I haven’t destroyed the black tree. So this has been tackled in the file system and database world. But I'm talking about a general principle that we're tackling this with non-volatile memory and I'm sort of going to move on to saying in a practical sense if you’re writing code today, what are the libraries available to let you do this in a more high level maybe having to take up all those details yourself.

Question: 

What keeps you up at night?

Answer: 

Well as I look a lot of the hardware software interface so a lot of the tech issues I deal with is really coming from two angles. One is because Moore's Law is slowing down so CPUs basically you can not take the same code and speed up by a factor of two every 18 months. At the same time software developers cannot expect code to be sped up until they start taking advantage of new features in the CPU; because that's the only way you can get things to go faster. So really a lot of the stuff that keeps me awake at night is bridging this.

Speaker: Amitabha Roy

Software Engineer @Google

Amitabha is a software engineer at Google. He likes to rethink system architecures in a world of changing hardware interfaces and properties. Some of the interesting things he has done are building graph processing systems that tackle trillions of edges, developed a completely transparent software transactional memory implementation for x86 machine code and developed a parallel algorithm for verifying the x86 memory consistency model that is used by Intel to verify their multicore products before they are shipped to customers.

Find Amitabha Roy at

Last Year's Tracks

  • Monday, 16 November

  • Inclusion & Diversity in Tech

    The road map to an inclusive and diverse tech organization. *Diversity & Inclusion defined as the inclusion of all individuals in an within tech, regardless of gender, religion, ethnicity, race, age, sexual orientation, and physical or mental fitness.

  • Architectures You've Always Wondered About

    How do they do it? In QCon's marquee Architectures track, we learn what it takes to operate at large scale from well-known names in our industry. You will take away hard-earned architectural lessons on scalability, reliability, throughput, and performance.

  • Architecting for Confidence: Building Resilient Systems

    Your system will fail. Build systems with the confidence to know when they do and you won’t.

  • Remotely Productive: Remote Teams & Software

    More and more companies are moving to remote work. How do you build, work on, and lead teams remotely?

  • Operating Microservices

    Building and operating distributed systems is hard, and microservices are no different. Learn strategies for not just building a service but operating them at scale.

  • Distributed Systems for Developers

    Computer science in practice. An applied track that fuses together the human side of computer science with the technical choices that are made along the way

  • Tuesday, 17 November

  • The Future of APIs

    Web-based API continue to evolve. The track provides the what, how, and why of future APIs, including GraphQL, Backend for Frontend, gRPC, & ReST

  • Resurgence of Functional Programming

    What was once a paradigm shift in how we thought of programming languages is now main stream in nearly all modern languages. Hear how software shops are infusing concepts like pure functions and immutablity into their architectures and design choices.

  • Social Responsibility: Implications of Building Modern Software

    Software has an ever increasing impact on individuals and society. Understanding these implications helps build software that works for all users

  • Non-Technical Skills for Technical Folks

    To be an effective engineer, requires more than great coding skills. Learn the subtle arts of the tech lead, including empathy, communication, and organization.

  • Clientside: From WASM to Browser Applications

    Dive into some of the technologies that can be leveraged to ultimately deliver a more impactful interaction between the user and client.

  • Languages of Infra

    More than just Infrastructure as a Service, today we have libraries, languages, and platforms that help us define our infra. Languages of Infra explore languages and libraries being used today to build modern cloud native architectures.

  • Wednesday, 18 November

  • Mechanical Sympathy: The Software/Hardware Divide

    Understanding the Hardware Makes You a Better Developer

  • Paths to Production: Deployment Pipelines as a Competitive Advantage

    Deployment pipelines allow us to push to production at ever increasing volume. Paths to production looks at how some of software's most well known shops continuous deliver code.

  • Java, The Platform

    Mobile, Micro, Modular: The platform continues to evolve and change. Discover how the platform continues to drive us forward.

  • Security for Engineers

    How to build secure, yet usable, systems from the engineer's perspective.

  • Modern Data Engineering

    The innovations necessary to build towards a fully automated decentralized data warehouse.

  • Machine Learning for the Software Engineer

    AI and machine learning are more approachable than ever. Discover how ML, deep learning, and other modern approaches are being used in practice by Software Engineers.