└── README.md


/README.md:
--------------------------------------------------------------------------------
 1 | # ChirpBird
 2 | 
 3 | This challenge has been replaced with [OwlDetect](https://github.com/riandyrn/owldetect) challenge. 😁
 4 | 
 5 | <!--
 6 | Welcome to Haraj take home challenge!
 7 | 
 8 | In this challenge you will be assigned to help fictional startup called `ChirpBird` to create their instant messaging platform. Basically they want to create platform similar like [Facebook Messenger](https://www.messenger.com/), [WhatsApp](https://www.whatsapp.com/), or [Telegram](https://telegram.org/).
 9 | 
10 | `ChirpBird` have vision to make it easy for people around the world to stay connected. It is your job to make that happen through your system. 😁
11 | 
12 | ## Requirements
13 | 
14 | You need to create system with client-server architecture. For the server you need to develop it using [Go](https://golang.org/). As for the client, you just need to create a web app (you could use whatever tools or framework to create it).
15 | 
16 | The system needs to be:
17 | 
18 | 1. Capable of delivering message to client instantly through Websocket
19 | 2. Capable of delivering text message
20 | 3. Capable of hosting P2P & Group chat
21 | 4. Horizontally scalable
22 | 5. Resilient from failure (since the system will be distributed, there should be tons of potential failures)
23 | 
24 | ## Deployment
25 | 
26 | It is not mandatory to deploy your system on public. However if you decided to do so, it would be very great. 
27 | 
28 | At the very least you need to deploy your system using docker-compose locally.
29 | 
30 | ## Evaluation
31 | 
32 | 1. System design
33 | 2. Project documentation (any docs that help people understand your project better)
34 |     - API documentation
35 |     - Architecture diagram
36 |     - DB schema
37 |     - Class diagram
38 |     - Failure handling documentation
39 |     - etc...
40 | 3. System fail safe strategies
41 | 4. Code readibility, cleanliness, & testability
42 | 5. UI comfortability (good UX)
43 | 6. Deployment strategy (bonus)
44 | 
45 | ## Submission
46 | 
47 | 1. Fork this repo.
48 | 2. After you finish creating your changes, submit the link of your fork along with your CV & cover letter to [this page](https://stackoverflow.com/jobs/558729?so_medium=Talent&so_source=Talent).
49 | 3. In your cover letter, share with us what changes you have made and what further changes you would prioritize if you had more time.
50 | 
51 | ## Deadline
52 | 
53 | There is no exact deadline date for this project. The only deadline is when the vacancy has been closed. We plan to open the vacancy for the next 3 months (it was first published on November 15, 2021).
54 | 
55 | So feel free to take your time.
56 | 
57 | ## Questions
58 | 
59 | Got any questions? Feel free to open [issues](https://github.com/riandyrn/chirpbird/issues).
60 | -->


--------------------------------------------------------------------------------