Tugas Analisis Perancangan Sistem Informasi

 Tugas 2 - System Request


Apa itu system request?

merupakan sebuah dokumen yang mendeskripsikan alasan bisnis diperlukannya membangun sebuah sistem, serta nilai yang diprediksi akan diberikanoleh sistem. Dokumen ini dibuat oleh Project Sponsor.

System Request memiliki 5 elemen :

  • Project Sponsor -> CP dari sebuah proyek
  • Kebutuhan bisnis -> merepresentasikan alasan yang mendasari proyek
  • Keperluan bisnis -> mengacu pada kemampuan bisnis yang harus dimiliki oleh sistem
  • Nilai bisnis -> mendeskripsikan manfaat yang akan didapatkan orgaisasi dari sistem
  • Special issues -> merupakan kumpulan dokumen yang berisi semua informasi yang mungkin diperlukan untuk penilaian proyek.

System request kemudian diajukan kepada komite untuk dimintai pertimbangannya. 

Contoh Penerapan system request pada platform Netflix.

What is Netflix?

Netflix is a subscription-based streaming service that allows its members to watch TV shows and movies on an internet-connected device. It is available on platforms such as the Web, iOS, Android, TV, etc.

Requirements

Our system should meet the following requirements:

Functional requirements

  • Users should be able to stream and share videos.
  • The content team (or users in YouTube's case) should be able to upload new videos (movies, tv shows episodes, and other content).
  • Users should be able to search for videos using titles or tags.
  • Users should be able to comment on a video similar to YouTube.

Non-Functional requirements

  • High availability with minimal latency.
  • High reliability, no uploads should be lost.
  • The system should be scalable and efficient.

Extended requirements

  • Certain content should be geo-blocked.
  • Resume video playback from the point user left off.
  • Record metrics and analytics of videos.

Estimation and Constraints

Let's start with the estimation and constraints.

Note: Make sure to check any scale or traffic-related assumptions with your interviewer.

Traffic

This will be a read-heavy system, let us assume we have 1 billion total users with 200 million daily active users (DAU), and on average each user watches 5 videos a day. This gives us 1 billion videos watched per day.

200 million×5 videos=1 billion/day
Assuming, a 200:1 read/write ratio, about 50 million videos will be uploaded every day.
1200×1 billion=50 million/day
What would be Requests Per Second (RPS) for our system?

1 billion requests per day translate into 12K requests per second.

1 billion(24 hrs×3600 seconds)=12K requests/second
### Storage

If we assume each video is 100 MB on average, we will require about 5 PB of storage every day.

50 million×100 MB=5 PB/day
And for 10 years, we will require an astounding 18,250 PB of storage.
5 PB×365 days×10 years=18,250 PB
### Bandwidth

As our system is handling 5 PB of ingress every day, we will a require minimum bandwidth of around 58 GB per second.

5 PB(24 hrs×3600 seconds)=58 GB/second
### High-level estimate

Here is our high-level estimate:

Type Estimate
Daily active users (DAU) 200 million
Requests per second (RPS) 12K/s
Storage (per day) ~5 PB
Storage (10 years) ~18,250 PB
Bandwidth ~58 GB/s                                        

 

Referensi: 

  • https://docplayer.info/122303903-Analisa-perancangan-si-ii-titien-s-sukamto.html
  • https://dev.to/karanpratapsingh/system-design-netflix-3d9g


Komentar

Postingan populer dari blog ini

EAS - Analisa Perancangan Sistem Informasi

Tugas Analisis Perancangan Sistem Informasi