https://github.com/censys/mini-scan-takehome

https://github.com/censys/mini-scan-takehome

Last synced: 24 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/censys/mini-scan-takehome
• Owner: censys
• Created: 2023-10-24T12:39:10.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-03-13T22:44:32.000Z (9 months ago)
• Last Synced: 2024-03-26T04:50:34.393Z (9 months ago)
• Language: Go
• Size: 52.7 KB
• Stars: 0
• Watchers: 4
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Mini-Scan

Hello!

As you've heard by now, Censys scans the internet at an incredible scale. Processing the results necessitates scaling horizontally across thousands of machines. One key aspect of our architecture is the use of distributed queues to pass data between machines.

---

The `docker-compose.yml` file sets up a toy example of a scanner. It spins up a Google Pub/Sub emulator, creates a topic and subscription, and publishes scan results to the topic. It can be run via `docker compose up`.

Your job is to build the data processing side. It should:

1. Pull scan results from the subscription `scan-sub`.

2. Maintain an up-to-date record of each unique `(ip, port, service)`. This should contain when the service was last scanned and a string containing the service's response.

> **_NOTE_**

The scanner can publish data in two formats, shown below. In both of the following examples, the service response should be stored as: `"hello world"`.

> ```javascript

> {

>   // ...

>   "data_version": 1,

>   "data": {

>     "response_bytes_utf8": "aGVsbG8gd29ybGQ="

>   }

> }

>

> {

>   // ...

>   "data_version": 2,

>   "data": {

>     "response_str": "hello world"

>   }

> }

> ```

Your processing application should be able to be scaled horizontally, but this isn't something you need to actually do. The processing application should use `at-least-once` semantics where ever applicable.

You may write this in any languages you choose, but Go, Scala, or Rust would be preferred. You may use any data store of your choosing, with `sqlite` being one example.

--- 

Please upload the code to a publicly accessible GitHub, GitLab or other public code repository account.  This README file should be updated, briefly documenting your solution. Like our own code, we expect testing instructions: whether it’s an automated test framework, or simple manual steps.

To help set expectations, we believe you should aim to take no more than 4 hours on this task.

We understand that you have other responsibilities, so if you think you’ll need more than 5 business days, just let us know when you expect to send a reply.

Please don’t hesitate to ask any follow-up questions for clarification.