...

...

The very first task (<1 week) will be to run the upstream examples and attempt to break the internal state of EMCO by modifying them, making API calls out of order, or proving providing incorrect parameters.

The intern student is expected to deliver multiple contributions, as a series of patches, throughout the internship, to resolve or improve the current referential integrity issues observed between microservices, or under certain edge cases (such as when dependent services respond unpredictably).

Depending on the difficulty of improving basic data integrity (reproduceable by the API examples), additional integrity-related tasks may be pursued:

• implementing or enhancing rollback/update operations

...

• clarifying intent vs. deployment-level states

...

• in code and in documentation
• if these tasks still prove to not be sufficient, the next step would be working on implementing support for an open-source NoSQL database backend for EMCO, which also

...

• relates to data integrity.

Since EMCO is still in its early days, the expected deliverables may also change throughout the internship, but the general umbrella of work items will remain with the intent of addressing data integrity and consistency issues. 

...

Working hours are flexible but the intern student should try to be reachable and responsive throughout 9am-4pm (pacific time) since that's when the team is most active.

Mentor(s) Names and Contact Info

Click here to apply

Please read all instructions before applying.  Include Resume, proof of school enrollment, and participation permission from school/employer

Igor DC | contact me | Intel Corporation

...