Engine for Zebra (Jul 17 Discussion and Jul 19 Follow-up)

[evaachim]

No description provided.

[evaachim]

1. Scraping the DB to enable search on the tool's resources with increased productivity
2. Assigning IPs in an async manner
3. Manage requests

[evaachim]

Potential solution: appengine

[evaachim]

The goal is to have two layers:

1. Async.
2. DB layer

[evaachim]

Thus, the following can be done:

1. requests, IPs, ...
2. searching the db

[evaachim]

• The tool can have a DB where all the data from the current spreadsheet model is ported, as well as on the server, and a syncing between the DB and server can be done.

• Instead of scraping the entire DB to search for a resource, employ matching as a search solution on the tool itself.

• Use the back-end engine to power several tasks via go-routines to improve performance.

• The goal is to have a bigger method that triggers different go routines which act to start various tasks as needed.

[evaachim]

May potentially use the engine for label assignment (such as, have a go routine that deals with labels).