Skip to content

kyomel/system-design-challenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 

Repository files navigation

Note

Welcome!

This is system design use case problem for Software Engineering Growth Indonesia - Computer Science subgroup.

Link Working Exalidraw: Link


7 October 2025

Live Discussion:

Link

Question:

Design a typeahead suggestion system.

Requirements:

Functional Requirements: The system should suggest top N (let’s say top ten) frequent and relevant terms to the user based on the text a user types in the search box.

Non-Functional Requirements:

  • Low latency
  • Fault tolerance
  • Scalability

25 August 2025

Live Discussion:

Link

Question:

Design a app calendar.

Requirements:

Functional Requirements:

  • Event Management
  • Calendar Views
  • Reminder & Notifications
  • Recurring Events
  • Multi-Device Synce

Non-Functional Requirements:

  • Perfomance
  • Reliability
  • Scalability
  • Usability

13 August 2025

Live Discussion:

Link

Question:

Design a service sequencer(random unique ID).

Requirements:

Functional Requirements:

  • Uniqueness
  • 64-bit numeric ID

Non-Functional Requirements:

  • Scalability
  • Availability

24 July 2025

Live Discussion:

Link

Question:

Design a service similar to Quora.

Requirements:

Functional Requirements:

  • Questions and answers
  • Upvote/downvote and comment
  • Search
  • Recommendation system
  • Ranking answers

Non-Functional Requirements:

  • Scalability
  • Consistency
  • Availability
  • Performance

24 June 2025

Live Discussion:

Link

Question:

Design a service similar to TinyURL for shortening the uniform resource locator(URL).

Requirements:

Functional Requirements:

  • Short URL generation
  • Redirection
  • Custom short links
  • Deletion
  • Update
  • Expiry time

Non-Functional Requirements:

  • Scalability
  • Latency
  • Availability
  • Readability
  • Unpredictability

15 June 2025

Live Discussion:

Link

Question:

Design a Like Counter System similar to Twitter's post likes or YouTube's video likes. Users should be able to like and unlike posts/content, with real-time counter updates and proper state management.

Requirements:

Functional Requirements:

  • Like/Unlike Operations
  • Counter Display
  • Data Consistency

Non-Functional Requirements:

  • Scalability
  • Performance
  • Availability
  • Consistency

23 May 2025

Live Discussion:

Link

Question:

Design an API rate limiter that caps the number of API calls the service can receive in a given period to avoid an overload. Requirements:

Functional Requirements:

  • Limit requests.
  • Configurable.
  • Error or notification if the limit is reached.

Non-Functional Requirements:

  • Availability.
  • Scalability.
  • Low latency.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •