1CS514: Intermediate Course in Computer SystemsLecture 1: Course Overview and ThemesProfessor: Paul FrancisTA: Saikat Guhahttp://www.cs.cornell.edu/courses/cs514/2003fa/CS514Perspectives on Computing Systems and Networks| CS314: Hardware and architecture| CS414: Operating Systems with a focus on single-processor and multi-processor systems| CS513: Security for operating systems and networks| CS514: Emphasis on “middleware”: Web services, distributed computing, reliability, major platforms| CS519: Network structure and widely used protocols, mobile networking, emerging issues and topics| CS614: A survey of current research frontiers in the operating systems and middleware space{{{PrerequisitesComplementary aspects of the same broad areaAimed a PhD students2CS514Picking between 514 and 614| CS514 is practical in emphasis:z We study tools used in real products and real systems. “Technology you can buy or build”z But looks hard at what goes on beneath the surfacez Projects build on popular technologies| CS614 emphasizes research opportunitiesz Mix of “classics” and state of the art papersz Tremendous amount of readingz Projects are often original research and many have resulted in publishable papersz For systems students in PhD program, often seen as a way to find a good research topicCS514About myself| This is my first semester as CS facultyz At Cornell or anywhere elsez I co-taught CS514 with Ken Birman last semester as an instructor| My background is primarily networkingz 15 years industrial research (Bellcore, NTT Software Labs, others)z Plus a few years spent in startups3CS514About myself| Primary “interest” is in large scale, self configuring networks of various sortsz But have done work in IP routing and addressingz Most notably I invented NATz But also some IPv6 work, multicast (IP and overlay), distributed search, etc.CS514Textbook| We are using Ken Birman’s textbookz Highly Assured Distributed Computing: Overcoming The Web Services and Distributed Systems Reliability Barrier| Originally written in 1995, substantially revised for your reading pleasurez And it is actually fun to read…| Most of the lectures are also Ken’s4CS514Course Overview| Combination of project and lectures| Some (not all) of the lectures relate to the project, but they don’t really tell you how to build the project| At 500 level, we expect you to be able to implement a project on your ownz With help from your team members, classmates, the TA, and me• In that order!CS514Student Evaluation(see www.cs.cornell.edu/courses/cs514/2003fa/)Intangibles: Class participation, mailing list participation, etc.5%-10%Homework (much of it will be project-lets) 15%Prelims (typically essay questions) 35%-40% (split evenly)Final Project (there will be a demo day) 40%5CS514Student Evaluation| Mention about how homework is graded| Regrading procedurez Regrade requests must be in writingz Must be within one week of original gradeCS514Course Project| Implement a web service using either J2EE or .NET| Give the service high availability in some wayz Replicate data, reliable transaction, etc.z This will require mechanisms not available in J2EE or .NET6CS514Course Project| You may work in teams of up to threez Each person may implement a different part, but you must all understand all of it| Project may be done for MEng credit (COM S 790)z You must get approval from me| Project is evaluated on demo dayz Based on quality of demo and discussionCS514Lecture outline| Part 1: Introductions to the course, to web services, and to the networks they run on| Part 2: Performance and Scaling Issues| Part 3: Security Issues| Part 4: Reliability and Fault Tolerance (and Performance) Issues| Part 5: Advanced Topics15%25%5%30%25%7CS514Lecture outline| Part 1: Introductions to the course, to web services, and to the networks they run onz .NET, J2EE, Web Services (SOAP-RPC, WDSL, XML, …), and the network (HTTP, TCP, …)z Message bus (publish/subscribe), transactions| Part 2: Performance and Scaling Issues| Part 3: Security Issues| Part 4: Reliability and Fault Tolerance (and Performance) Issues| Part 5: Advanced TopicsCS514Lecture outline| Part 1: Introductions to the course, to web services, and to the networks they run on| Part 2: Performance and Scaling Issuesz Replication in server cluster/farm, caches, consistency, hard/soft state, load balancing, and transactions, impact of network on performance| Part 3: Security Issues| Part 4: Reliability and Fault Tolerance (and Performance) Issues| Part 5: Advanced Topics8CS514Lecture outline| Part 1: Introductions to the course, to web services, and to the networks they run on| Part 2: Performance and Scaling Issues| Part 3: Security Issuesz HTTPS/SSL, Certs and PKI, Network security and network attacks, Web Services security| Part 4: Reliability and Fault Tolerance (and Performance) Issues| Part 5: Advanced TopicsCS514Lecture outline| Part 1: Introductions to the course, to web services, and to the networks they run on| Part 2: Performance and Scaling Issues| Part 3: Security Issues| Part 4: Reliability and Fault Tolerance (and Performance) Issuesz Most detailed drill downz RPC issues, virtual synchrony, transaction concepts like 2/3 phase commit and serializability, and multicast| Part 5: Advanced Topics9CS514Lecture outline| Part 1: Introductions to the course, to web services, and to the networks they run on| Part 2: Performance and Scaling Issues| Part 3: Security Issues| Part 4: Reliability and Fault Tolerance (and Performance) Issues| Part 5: Advanced Topicsz Various topics: discovery issues in the web and in peer-to-peer (P2P) systems (DNS, DHTs, Google), P2P networks for file and data replication (Napster, Gnutella, Freenet, CFS, PAST), mobility challenges (Coda, Rover), more multicast, Resilient Overlay Networks, Grid computing, and Autonomic computingCS514Recent Trends| A network rollout of unprecedented scale continuesz Larger and larger numbers of small devices, web-compatible cell phonesz Everything is “on the web” – “Web Services”| Object orientation and components have become a prevailing structural optionz Promotes productivity, software reusez Widespread use of transactions for reliability and atomicity| Platform standards are a battlegroundz Java/J2EE vs C#/.NET| Client-server model is fading… what will replace it?10CS514How can we learn about these?| Basically two optionsz Study the fundamentalsz Then
View Full Document
Unlocking...