This slidedeck from Giragadurai covers the following topics: • Cloud Native (Scalability, Fault Tolerance, Load Balancing, Security and Monitoring Data) • Micro Services (Concept, Containers & Inter-Communication Patterns) • Big Data (Concept, Lambda Architecture) • IoT Applications (Concept, Device, Data Acquisition, Edge & Deep Processing/Analytics)

1. Modern Software Architectures
Giragadurai Vallirajan
@girag
✉ grahaindia@gmail.com

2. Agenda
● Evolution
● Cloud Native Application
● Microservices
● Case Study - 1
● Big-data Analytics
● IOT Application
● Case Study - 2

3. Evolution of Architecture
1970’s
Monolithic
Data
BL
UX
1980’s
2-Tier
Data
BL
UX
1990’s
3-Tier
Data
BL
UX
2000’s
SOA
Data
BL
UX
Service API
svc
2010’s
Web Scale
SOA
Data
UX
…...
svc

4. Cloud
“Cloud computing enables companies to consume compute
resources as a utility (like electricity) rather than having to
build and maintain computing infrastructures in-house.”
Three of the main benefits of cloud computing include:
○ Self-service provisioning: End users can spin
up computing resources for almost any type of
workload on-demand.
○ Elasticity: Companies can scale up as
computing needs increase and then scale down
again as demands decrease.
○ Pay per use: Computing resources are
measured at a granular level, allowing users to
pay only for the resources and workloads they
use.

5. Anything
as Service

6. Factors to
consider...
multitenancy

7. Factors to
consider...
load balance

8. Factors to
consider...
scaling
ComputePower
Timeline

9. Factors to
consider...
X - Axi
Sca
Y - Axi
Sca
Reference : http://microservices.io/articles/scalecube.html

10. Factors to
consider...
Z - Axi
Sca
Mix X
an Y
Reference : http://microservices.io/articles/scalecube.html

11. Microservices
● the microservice architectural style is an approach to developing a single
application as a suite of small services, each running in its own process and
communicating with lightweight mechanisms, often an HTTP resource API.
● These services are built around business capabilities and independently
deployable by fully automated deployment machinery.
● There is a bare minimum of centralized management of these services, which
may be written in different programming languages and use different data
storage technologies.

12. Microservices

13. Microservices
1970’s
Monolithic
Data
BL
UX
1980’s
2-Tier
Data
BL
UX
1990’s
3-Tier
Data
BL
UX
2000’s
SOA
Data
BL
UX
Service API
svc
2010’s
Web Scale
SOA
Data
UX svc

14. Virtualization

15. Containerizing

16. Container Ecosystem
Refer following link for latest up-to-date Ecosystem https://www.mindmeister.com/389671722/open-container-ecosystem-formerly-docker-ecosystem

17. Factors to
consider...
Monitoring
and
Metering
Monitoring and Metering Cloud
application metrics for health tracking
and also pricing.
● CPU Utilization
● Network (Inbound / Outbound)
● DiskOps, Bytes (Read/Write)
● Server Throughput (In/Out)
● Service API Usage Count
● Delays

18. Factors to
consider...
Pricing
● Focusing solely on registering accounts with free trials
increases dependency and ultimately, conversions.
● Presenting 5 plans clearly enforces the level of
seriousness, capability, and value increase by price plan,
without doubting higher price points.
● Focusing on team size directly validates price
differences.
● Pairing a free trial with necessary quotes allows potential
customers to experience the service first-hand and
validate higher-priced plan propositions.
● Transparency and customisation in pricing information
allow potential customers to determine an appropriate
plan and increase comfort level.

19. Let r ...

20. Assignment
Questionnaire App We have to design an SAAS based application for helping customer who like to post a
survey, poll, census to study their customer expectation, business reachability or quiz competitions.
Functionality,
1. An Account can have many survey and track them
2. Participant can be Anonymous (survey) or known (quiz)
3. Statistical analytics of individual survey
4. Every campaign stay active for duration
5. API Service for custom integration
6. Charges
Factors to be noted,
1. Scale, end user must get seamless feeling even the load high
2. Multi-Tenancy
3. Security

21. Application - Data Intensive

22. Data Landscape
Reference : Tiecon data landscape

23. Data Landscape
Reference : IBM Infographic

24. Data
Infrastructure

25. Lambda
Architecture

26. IOT
Now
Microservice
Data
UX svc
The Internet of Things (IoT) is the network of physical devices,
vehicles, home appliances and other items embedded with
electronics, software, sensors, actuators, and connectivity which
enables these things to connect and exchange data, creating
opportunities for more direct integration of the physical world into
computer-based systems, resulting in efficiency improvements,
economic benefits and reduced human intervention.
Applications
● Consumer Application
○ Smart Home
○ Wearables
● Enterprise Application
● Industrial Application
○ Manufacturing
○ Assembly
○ Energy Management
● Agriculture
● Medical Healthcare
● etc...

27. Reference : https://techbeacon.com/4-stages-iot-architecture
IOT Solution

28. Sensor / Actuator
A “Sensor” is a transducer that converts a physical stimulus from one form into a more useful
form to measure the stimulus. There are two basic categories:
● Analog
● Discrete
○ Binary
○ Digital (e.g., Pulse Counter)
Examples: Sound (db), Touch, Light with lumin, Distance with ultrasonic, Temperature, RFID
Barcode, Proximity, Vision, Gyroscope, Compass, Tilt/Acceleration Etc.
An “Actuator” is a component of a machine that is responsible for moving and controlling a
mechanism or system, for example by opening a valve. In simple terms, it is a "mover".
Types of Actuators
● Electrical actuators
○ Electric motors
■ DC servomotors
■ AC motors Stepper motors
○ Solenoids
● Hydraulic actuators ~ Use hydraulic fluid to amplify the controller command signal
● Pneumatic actuators ~ Use compressed air as the driving force
Reference http://www.sensorwiki.org/

29. Data Acquisition
Data acquisition systems (DAS) perform these data aggregation and conversion functions.
The DAS connects to the sensor network, aggregates outputs, and performs the
analog-to-digital conversion. The Internet gateway receives the aggregated and digitized data
and routes for further processing. DA systems often sit in close proximity to the sensors and
actuators.
For example, a pump might contain a half-dozen sensors and actuators that feed data into a
data aggregation device that also digitizes the data. This device might be physically attached
to the pump.
Purpose :
Preprocessing - The analog data streams that come from sensors create large volumes of
data quickly. The measurable qualities of the physical world in which your business may be
interested—motion, voltage, vibration, and so on—can create voluminous amounts of
constantly changing data. Think how much sensor data a complex machine like an aircraft
engine might generate in one day, and there’s no theoretical limit to the number of sensors
that could be feeding data into an IoT system.
Mapping - not to pass the data on to the data center in this form is that analog data has
specific timing and structural characteristics that require specialized software to process. It's
best to convert the data into digital form first

30. Edge Computing
Edge IT systems, which perform more analysis,
contextualizing and filtering. Edge IT processing
systems may be located in remote offices or other
edge locations, but generally these sit in the facility or
location where the sensors reside closer to the
sensors, such as in a wiring closet.
● It's a stream processor
● Regulate data to avoid flooding network
bandwidth
● Basic analytics run on edge, reduces operation on
core
● Machine learning used to pick data smartly
● High priority decision making logic packed with
this.

31. Factors to
consider...
Protocol
Choosing protocol is the key for the communication,
● Advanced Message Queuing Protocol (AMQP)
● Constrained Application Protocol (CoAP)
● Extensible Messaging and Presence Protocol (XMPP)
● OASIS Message Queuing Telemetry Transport (MQTT)
● Very Simple Control Protocol (VSCP)
Reference https://techbeacon.com/67-open-source-tools-resources-iot

32. Factors to
consider...
Operating
Systems
Choosing operating system is the another,
● ARM mbed
● Canonical Ubuntu and Snappy Ubuntu Core
● Contiki
● Raspbian
● RIOT

33. Factors to
consider...
Framework
Choosing flow editor / platform, ease up your development,
● Eclipse Kura
● Node RED
● FloGo
● ThingBox
● KinomaJS

34. Let r ...

35. Assignment