Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Your Guide to Writing A Technical Abstract

96fd3cfb5c5fa348143916fde090599a?s=47 Francesca Krihely
December 28, 2016
58

Your Guide to Writing A Technical Abstract

96fd3cfb5c5fa348143916fde090599a?s=128

Francesca Krihely

December 28, 2016
Tweet

Transcript

  1. Your guide to writing abstracts

  2. What’s the point of an abstract? • Why they should

    come • What to expect • How to plan for it
  3. Abstract = Invitation

  4. Abstract Formula • What is the problem you are trying

    to solve? • What are our learning objectives for the audience? • How are you going to teach this to the audience? “This is what I will do to teach you how to can learn this thing” • What are you going to know how to do when you leave? • What should someone know before they come into your session?
  5. Test it out Many organizations are moving to microservices, running

    smaller systems to help increase release frequency, or application portability. In this session you will learn how to set up MongoDB to run on containers, and how to orchestrate them with Kubernetes through configuration examples. We’ll then discuss managing high availability and resiliency in a containerized environment by walking through demos of failure scenarios. At the end of the session, you’ll know how to configure MongoDB for Docker containers, orchestrate them with Kubernetes, and understand best practices for managing high availability in a containerized environment. We recommend you attend “Microservices 100” before you attend this session to get an introductory overview of containers and Kubernetes. Attendees should also understand the basics of MongoDB architecture and the concepts of replication and sharding.
  6. What is the problem you are trying to solve? Many

    organizations are moving to microservices, running smaller systems to help increase release frequency, application portability. We know you need to learn how to do this!
  7. What are our learning objectives for the audience? 1. How

    to successfully define your infrastructure with MongoDB running on containers 2. How to orchestrate them with Kubernetes 3. Managing high availability and resiliency in a containerized environment
  8. How are you going to teach this to the audience?

    1. Show recommended configurations for running MongoDB on containers 2. Demoing failure scenarios
  9. What are you going to know how to do when

    you leave? You’re going to know how to configure MongoDB for Docker containers and then orchestrate them with Kubernetes and understand best practices for managing high availability in a containerized environment.
  10. What should someone know before they come into your session?

    We recommend you attend “Microservices 100” before you attend this session to get an introductory overview of containers and Kubernetes. Attendees should also understand the basics of MongoDB architecture and the concepts of replication and sharding.
  11. Go forth, and write your own abstract!