This document discusses distributed systems, providing examples and discussing their key characteristics and design issues. It defines distributed systems as those where components located at networked computers communicate only by passing messages. Common characteristics include heterogeneity, security, scalability, and failure handling. Basic design issues addressed are naming, communication, software structure, and system architectures like client-server and peer-to-peer.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
2. 1. What is a Distributed System
2. Examples of Distributed Systems
3. Common Characteristics
4. Basic Design Issues
5. Summary
2
3. 1. DISTRIBUTED SYSTEM TYPES
Fully
Distributed
Processors
Control
Fully replicated
Not fully replicated
master directory
Local data,
local directory
Master-slave
Autonomous
transaction based
Autonomous
fully cooperative
Homog.
special
purpose
Heterog.
special
purpose
Homog.
general
purpose
Heterog.
general
purpose
3
4. 1. WHAT IS A DISTRIBUTED SYSTEM?
Definition: A distributed system is one in which components
located at networked computers communicate and coordinate
their actions only by passing messages. This definition leads
to the following characteristics of distributed systems:
Concurrency of components
Lack of a global ‘clock’
Independent failures of components
4
5. 1.1 CENTRALIZED SYSTEM CHARACTERISTICS
One component with non-autonomous parts
Component shared by users all the time
All resources accessible
Software runs in a single process
Single point of control
Single point of failure
5
6. 1.2 DISTRIBUTED SYSTEM CHARACTERISTICS
Multiple autonomous components
Components are not shared by all users
Resources may not be accessible
Software runs in concurrent processes on different
processors
Multiple points of control
Multiple points of failure
6
7. 2. EXAMPLES OF DISTRIBUTED SYSTEMS
Local Area Network and Intranet
Database Management System
Automatic Teller Machine Network
Internet/World-Wide Web
Mobile and Ubiquitous Computing
7
8. 2.1 LOCAL AREA NETWORK
the rest of
email server
Web server
Desktop
computers
File server
router/firew all
print and other servers
other servers
print
Local area
netw ork
email server
the Internet
8
13. 2.4.2 WEB SERVERS AND WEB BROWSERS
Internet
Browsers
Web servers
www.google.com
www.uu.se
www.w3c.org
Protocols
Activity.html
http://www.w3c.org/Protocols/Activity.html
http://www.google.comlsearch?q=lyu
http://www.uu.se/
File system of
www.w3c.org
13
14. 2.5 MOBILE AND UBIQUITOUS COMPUTING
Laptop
Mobile
Printer
Camera
Internet
Host intranet Home intranet
GSM/GPRS
Wireless LAN
phone
gateway
Host site
14
15. 3. COMMON CHARACTERISTICS
What are we trying to achieve when we construct a distributed
system?
Certain common characteristics can be used to assess
distributed systems
Heterogeneity
Openness
Security
Scalability
Failure Handling
Concurrency
Transparency
15
16. 3.1 HETEROGENEITY
Variety and differences in
Networks
Computer hardware
Operating systems
Programming languages
Implementations by different developers
Middleware as software layers to provide a programming abstraction
as well as masking the heterogeneity of the underlying networks,
hardware, OS, and programming languages (e.g., CORBA).
Mobile Code to refer to code that can be sent from one computer to
another and run at the destination (e.g., Java applets and Java
virtual machine).
16
17. 3.2 OPENNESS
Openness is concerned with extensions and
improvements of distributed systems.
Detailed interfaces of components need to be published.
New components have to be integrated with existing
components.
Differences in data representation of interface types on
different processors (of different vendors) have to be
resolved.
17
18. 3.3 SECURITY
In a distributed system, clients send requests to access
data managed by servers, resources in the networks:
Doctors requesting records from hospitals
Users purchase products through electronic commerce
Security is required for:
Concealing the contents of messages: security and privacy
Identifying a remote user or other agent correctly (authentication)
New challenges:
Denial of service attack
Security of mobile code
18
19. 3.4 SCALABILITY
Adaptation of distributed systems to
accommodate more users
respond faster (this is the hard one)
Usually done by adding more and/or faster processors.
Components should not need to be changed when scale
of a system increases.
Design components to be scalable!
19
20. 3.5 FAILURE HANDLING (FAULT TOLERANCE)
Hardware, software and networks fail!
Distributed systems must maintain availability even at
low levels of hardware/software/network reliability.
Fault tolerance is achieved by
recovery
redundancy
20
21. 3.6 CONCURRENCY
Components in distributed systems are executed in
concurrent processes.
Components access and update shared resources (e.g.
variables, databases, device drivers).
Integrity of the system may be violated if concurrent
updates are not coordinated.
Lost updates
Inconsistent analysis
21
22. 3.7 TRANSPARENCY
Distributed systems should be perceived by users and
application programmers as a whole rather than as a
collection of cooperating components.
Transparency has different aspects.
These represent various properties that distributed
systems should have.
22
23. 4. BASIC DESIGN ISSUES
General software engineering principles include
rigor and formality, separation of concerns,
modularity, abstraction, anticipation of change, …
Specific issues for distributed systems:
Naming
Communication
Software structure
System architecture
Workload allocation
Consistency maintenance
31
24. 4.1 NAMING
A name is resolved when translated into an interpretable form
for resource/object reference.
Communication identifier (IP address + port number)
Name resolution involves several translation steps
Design considerations
Choice of name space for each resource type
Name service to resolve resource names to comm. id.
Name services include naming context resolution, hierarchical
structure, resource protection
32
25. 4.2 COMMUNICATION
Separated components communicate with sending processes
and receiving processes for data transfer and synchronization.
Message passing: send and receive primitives
synchronous or blocking
asynchronous or non-blocking
Abstractions defined: channels, sockets, ports.
Communication patterns: client-server communication (e.g.,
RPC, function shipping) and group multicast
33
26. 4.3 SOFTWARE STRUCTURE
Layers in centralized computer systems:
Applications
Middleware
Operating system
Computer and Network Hardware
34
27. 4.3 SOFTWARE STRUCTURE
Layers and dependencies in distributed systems:
Applications
Distributed programming
support
Open
services
Open system kernel services
Computer and network hardware
35
28. 4.4 SYSTEM ARCHITECTURES
Client-Server
Peer-to-Peer
Services provided by multiple servers
Proxy servers and caches
Mobile code and mobile agents
Network computers
Thin clients and mobile devices
36
29. 4.4.1 CLIENTS INVOKE INDIVIDUAL SERVERS
Server
Client
Client
invocation
result
Server
invocation
result
Process:
Key:
Computer:
37
31. 4.4.3 A SERVICE BY MULTIPLE SERVERS
Server
Server
Server
Service
Client
Client
39
32. 4.4.4 WEB PROXY SERVER
Client
Proxy
Web
server
Web
server
server
Client
40
33. 4.4.5 WEB APPLETS
a) client request results in the dow nloading of applet code
Web
server
Client
Web
server
Applet
Applet code
Client
b) client interacts w ith the applet
41
34. 4.4.6 THIN CLIENTS AND COMPUTE SERVERS
Thin
Client
Application
Process
Network computer or PC
Compute server
network
42
35. 5. SUMMARY
Definitions of distributed systems and comparisons to
centralized systems.
The characteristics of distributed systems.
The eight forms of transparency.
The basic design issues.
Read Chapter 1 and Chapter 2 of the textbook.
43