Outline ● What is plugin architecture? ● Why use plugin architecture? ● Designing a simplified plugin architecture ● Library used in robotics to implement plugin based system ○ Pluginlib ● Case study study for plugin architecture - MoveIt ● Limitations ● Summary 2Introduction •Abi Sivaraman •Robotics Engineer at PickNik Robotics •I work with robotic arms •MoveIt Maintainer 3What is plugin plugin architecture? Software Design Pattern that allows for developers to add functionality to a larger system without having to alter the source code of the system itself. Plug-ins are self-contained

API server-side architecture for Beginners GopherCon ���� ����.��.�� - @hgsgtk © ����-���� BASE, Inc. � Talk abstract • A practical approach to build server-side architecture in a Go project � Problem of building architecture for beginners � Approach to build architecture � Summary � Talk structure © ����-���� BASE, Inc. � Problem of building architecture for beginners � Approach Approach to build architecture � Summary � Talk structure © ����-���� BASE, Inc. � Why I need server-side architecture �.Keep a design easy to change • -> Separate external input/output and business

uptake in many different computing sectors. The book also contains many insights about computer architecture in general, as well as explaining the particular de- sign choices we made in creating RISC-V. the point, and complete. The book’s commentaries provide a gratuitous history, motivation, and architecture critique. —C. Gordon Bell, Microsoft and designer of the Digital PDP-11 and VAX-11 instruction handy little book effortlessly summarizes all the essential elements of the RISC-V Instruction Set Architecture, a perfect reference guide for students and practitioners alike. —Professor Randy Katz, University

embedded software • Started using C++ in 1995 • First cross-platform project in 1994Cross-Platform Architecture Goals • Take advantage of all platforms • Focus on the compiler • Minimize boilerplate and unnecessary requiring implementations that differ depending upon the target machine architecture. • Features may be hardware: CPU architecture, SIMD instruction set, DMA controller, GPIO module, etc. • Features

. . . . . . . . . . . . . . . . . . . . . . . . . 05 Push vs . Pull-Based Architecture . . . . . . . . . . . . . . . . . . . . . . include continuous integration / continuous delivery (CI/CD), choosing between pull- or push-based architecture, and observability. Getting Started with GitOps Looking for an In-Depth Introduction to GitOps are property of their respective companies. Push vs. Pull-Based Architecture Push vs . Pull-Based Architecture Adopting a cloud-native architecture is not without its challenges. While the benefits are

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Architecture/Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 2. Pull-based metrics system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3 Architecture/Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 2. Pull-based metrics system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Architecture/Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 2. Pull-based metrics system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction Background Operations & observability Outro Working assumptions & concepts Prometheus is a pull-based system Black-box monitoring: Looking at a service from the outside (Does the server answer to

arbitrary append-only Update rates relatively low high, bursty Processing Model query-driven / pull-based data-driven / push-based Queries ad-hoc continuous Latency relatively high low 5 Vasiliki Kalavri