App Deployment, Debugging, and Performance

Start Date: 10/18/2020

Course Type: Common Course

Course Link:

Explore 1600+ online courses from top universities. Join Coursera today to learn data science, programming, business strategy, and more.

About Course

In this course, application developers learn how to design and develop cloud-native applications that seamlessly integrate managed services from the Google Cloud Platform. Through a combination of presentations, demos, and hands-on labs, participants learn how to create repeatable deployments by treating infrastructure as code, choose the appropriate application execution environment for an application, and monitor application performance. Learners can choose to complete labs in their favorite language: Node.js, Java, or Python. Prerequisites and prework: • Completed Google Cloud Platform Fundamentals or have equivalent experience • Working knowledge of Node.js, Java, or Python • Basic proficiency with command-line tools and Linux operating system environments • Previous course(s) in the specialization

Deep Learning Specialization on Coursera

Course Introduction

App Deployment, Debugging, and Performance In this course, we'll explore how to develop more efficient applications by using a set of common, simple techniques, using AppDelegate and sharing resources between different classes. We will explore how to make these simpler by adopting a uniform approach for all classes and using a common approach to build common functionality across different classes. This course assumes some prior experience with Java programming, as we will cover many of the key concepts and techniques through which you can build complex, functional Java programs. If you are new to Java programming or if you want to skip the boilerplate and get straight to tips and tricks, feel free to skip down to the next course in this specialization. This course is the third and last course in the Java specialization. Completion of the first course will give you access to all the major features and functionality of the Java programming language. The second and third courses are focused on making your Java code more efficient and modular, while the final course focuses on the use of common practices to make your Java code more robust and maintainable. Course 4: Debugging and Performance In this course, we'll dive deeply into the topic of application performance and debugging. We'll cover topics such as memory usage, disk usage, networking, and the like. We'll also discuss methods of investigating application performance and how to use common debugging techniques such as profiling, system analysis, and simple rule-driven debugging. We'll use the common frameworks used in Java programs, such as

Course Tag

Google Container Engine Debugging Google Cloud Platform Cloud Computing

Related Wiki Topic

Article Example
Debugging Anti-debugging is "the implementation of one or more techniques within computer code that hinders attempts at reverse engineering or debugging a target process". It is actively used by recognized publishers in copy-protection schemas, but is also used by malware to complicate its detection and elimination. Techniques used in anti-debugging include:
Debugging Debugging ranges in complexity from fixing simple errors to performing lengthy and tiresome tasks of data collection, analysis, and scheduling updates. The debugging skill of the programmer can be a major factor in the ability to debug a problem, but the difficulty of software debugging varies greatly with the complexity of the system, and also depends, to some extent, on the programming language(s) used and the available tools, such as "debuggers". Debuggers are software tools which enable the programmer to monitor the execution of a program, stop it, restart it, set breakpoints, and change values in memory. The term "debugger" can also refer to the person who is doing the debugging.
Microsoft App-V Aside from the operations associated with the deployment operations, App-V Application Virtualization mainly comprises two components – the "App-V Sequencer" and the "App-V Client".
Debugging Debugging is the process of finding and resolving of defects that prevent correct operation of computer software or a system.
Debugging Numerous books have been written about debugging (see below: Further reading), as it involves numerous aspects, including interactive debugging, control flow, integration testing, log files, monitoring (application, system), memory dumps, profiling, Statistical Process Control, and special design tactics to improve detection while simplifying changes.
Debugging The terms "bug" and "debugging" are popularly attributed to Admiral Grace Hopper in the 1940s. While she was working on a Mark II Computer at Harvard University, her associates discovered a moth stuck in a relay and thereby impeding operation, whereupon she remarked that they were "debugging" the system. However the term "bug" in the meaning of technical error dates back at least to 1878 and Thomas Edison (see software bug for a full discussion), and "debugging" seems to have been used as a term in aeronautics before entering the world of computers. Indeed, in an interview Grace Hopper remarked that she was not coining the term. The moth fit the already existing terminology, so it was saved. A letter from J. Robert Oppenheimer (director of the WWII atomic bomb "Manhattan" project at Los Alamos, NM) used the term in a letter to Dr. Ernest Lawrence at UC Berkeley, dated October 27, 1944, regarding the recruitment of additional technical staff.
Debugging In contrast to the general purpose computer software design environment, a primary characteristic of embedded environments is the sheer number of different platforms available to the developers (CPU architectures, vendors, operating systems and their variants). Embedded systems are, by definition, not general-purpose designs: they are typically developed for a single task (or small range of tasks), and the platform is chosen specifically to optimize that application. Not only does this fact make life tough for embedded system developers, it also makes debugging and testing of these systems harder as well, since different debugging tools are needed in different platforms.
Microsoft App-V App-V 5 requires the use of System Center Configuration Manager 2012, and above, for full support of App-V features. Deployment by older versions, or other electronic delivery systems, are also possible by using the virtual msi method of deployment.
Debugging data format Some object file formats include debugging information, but others can use generic debugging data formats such as stabs and DWARF.
Debugging The seminal article by Gill in 1951 is the earliest in-depth discussion of programming errors, but it does not use the term "bug" or "debugging".
Debugging By 1963 "debugging" was a common enough term to be mentioned in passing without explanation on page 1 of the CTSS manual.
Debugging The Oxford English Dictionary entry for "debug" quotes the term "debugging" used in reference to airplane engine testing in a 1945 article in the Journal of the Royal Aeronautical Society. An article in "Airforce" (June 1945 p. 50) also refers to debugging, this time of aircraft cameras. Hopper's bug was found on September 9, 1947. The term was not adopted by computer programmers until the early 1950s.
Debugging For debugging electronic hardware (e.g., computer hardware) as well as low-level software (e.g., BIOSes, device drivers) and firmware, instruments such as oscilloscopes, logic analyzers or in-circuit emulators (ICEs) are often used, alone or in combination. An ICE may perform many of the typical software debugger's tasks on low-level software and firmware.
Debugging In the ACM's digital library, the term "debugging" is first used in three papers from 1952 ACM National Meetings. Two of the three use the term in quotation marks.
Algorithmic program debugging The research and development in the field of Algorithmic debugging has made major improvements over the original algorithms for debugging Prolog and other and extended the ideas to other language paradigms such as functional languages and object oriented languages.
Debugging Normally the first step in debugging is to attempt to reproduce the problem. This can be a non-trivial task, for example as with parallel processes or some unusual software bugs. Also, specific user environment and usage history can make it difficult to reproduce the problem.
Algorithmic program debugging Algorithmic debugging (also called declarative debugging) is a debugging technique that compares the results of sub-computations with what the programmer intended. The technique constructs an internal representation of all computations and sub-computations performed during the execution of a buggy program and then asks the programmer about the correctness of such computations. By asking the programmer questions or using a formal specification, the system can identify precisely where in a program a bug is located. Debugging techniques can dramatically reduce the time and effort spent on debugging.
Delta Debugging Delta Debugging is a methodology to automate the debugging of programs using a scientific approach of hypothesis-trial-result loop. This methodology was first developed by Andreas Zeller of the Saarland University in 1999.
RR (debugging) In computing, rr (usually spelled in lowercase) is a debugging tool, designed to record and reproduce execution state of a program. RR also supports reverse execution.
Debugging data format A debugging data format is a means of storing information about a compiled computer program for use by high-level debuggers. Modern debugging data formats store enough information to allow source-level debugging.