The document discusses high availability (HA) and load balancing (LB), emphasizing their distinct purposes: HA ensures consistent service despite failures while LB focuses on distributing workloads for scalability. It outlines various approaches, including OS-level hardware redundancy and software solutions, and highlights the importance of application design for database availability. The document concludes with a summary of upcoming webinars and includes quiz questions related to the concepts discussed.

1. Does HA Can Help You
Balance Your Load?
Equnix Webinar TechTalk 2021 - June 2021
MYTHBUSTERS

2. Copyright © 2007-2021 PT Equnix Business Solutions. Copyright is protected by law.
This document is owned by PT Equnix Business Solutions. This document contains confidential information, which
is protected by law. No part of this publication could be photocopied, reproduced or translated into another language
without permitted or the express written consent of PT Equnix Business Solutions.
Data and information regarding the proposal and its offer is for limited use and are not disclosed. The information
contained in this document is subject to change at any time without prior notice.
Copyright Statement

3. Our Client and Partners

4. High Availability
“Availability of resources in a computer system, in the
wake of component failures in the system.”
Source: IEEE Task Force on Cluster Computing.
In short, It is a capability of the System to failover and avoiding
Single Point of Failure (SPOF)

5. What is High Availability (HA)?
● HA is a “concept”
● A percentage of time that a given system is providing service since it has
been deployed (production)
● For example: A system is 99% available if the downtime is 4 days in a year
● Everyone craves for the five 9s (downtime of less than 5 minutes in a year
– 99.999%)
● HA is NOT designed for high performance
● HA is NOT designed for high throughput (aka load balancing)
● OS Level

6. A. Hardware Redundancy
More expensive, provide higher degree of availability
(close to fault tolerant system).
B. Software Solutions
From OS level up to application level. Application should
be support by design. Database level availability is a must
for today requirement.
C. Mix both approaches.
Approaches

7. HA is not LB
&
LB is not HA
HA for Availability, while LB for Scalability

9. Scale Up vs Scale Out
Scale Up
❖ Add more CPU Clock
❖ Add more Memory
❖ Add more Storage & IOPS
❖ Tune Logical Database
Structure
❖ Tune Application Logic
❖ Optimize business processes
❖ Open more concurrency
Scale Out
❖ Add more servers
❖ Deploy applications and
database instances on more
than one server
❖ Implement Load balancing

10. Connection Pool
❖ When database resources is not really
powerful enough
❖ When application load is really heavy
❖ Not for HA
❖ LB on DB is not that simple

11. Clustering/load balancing – Master/Replica
Master-Replica Load Balancing
Master-Replica Cluster with capability of load balancing.
All update query goes to master, while read-only query goes to replica.
Async

12. So how to get
both??

13. Thank You
Equnix Business Solutions, Pte Ltd.
8 Eu Tong Sen Street, #14-94
THE CENTRAL - Singapore 059818
Equnix Business Solutions, PT.
Sampoerna Strategic Square 25th Floor
Jl. Jend Sudirman - Jakarta 12930
Ep Date Topic Speaker
4 30 June
2021
Myth-buster: Build Enterprise Level Data Center is more
expensive than Cloud
Lucky Haryadi
5 7 Juli 2021 Equnix’s Birthday All Equnix Team
6 14 Juli 2021 Friend or Foe: Hiring DBAs or Use Vendors? Chris Travers
7 21 Juli 2021 Friend or Foe: Is Open Source is the right choice for your
system?
Agatha & Yudha
8 28 Juli 2021 Are you sure that your Application is Enterprise Level? Julyanto & Hani
Don’t miss our next episodes...

14. Our Sponsor

15. Komunikasi apa yang menjadi pembangun
terbentuknya High Availability pada 2 server?
A. Heart beat
B. Heart pulse
C. Heart wave
D. Streaming replication

16. Apa yang dimaksud dengan SPOF?
A. Single Point of Faint
B. Separate Point of Failure
C. Single Point of Failure
D. Separate Point of Faint

17. Apa yang menjadi tujuan dikonfigurasikannya HA?
A. Automatic Takeover
B. Automatic Swing over
C. Automatic Failover
D. Automatic Pullover