ROOST Cloud Native Hackathon

Theme based FAQ's:

1. Can you provide some more details on the themes of the event?

• Collaborative Development of Microservices

When two or more developers work on a feature which includes multiple services which are dependent on each other, they would need specs/request/response schema of dependent microservices.

To develop in parallel, the options for them to use specs or create mock services. Mock services may have to be changed a lot during development as requirements keep on changing.

With Roost's Collaboration feature, during development, you can share and run your services in each other's environment, there is no need for mock services.

You can build any use case consisting of dependent microservices built across ROOST instances and ensure both backward and forward integration of services.

• Service to Service Observability

Collect service to service interaction data (east-west). You can use tracing, custom proxy based on sidecar pattern, or a light-weight servicemesh/proxy to achieve that.

Learn from the collected data to understand a normal service to service behavior. Compare it with live interaction/traffic data to detect deviations.

You can deploy it to multiple Roost instances for higher accuracy.

• Operationalize Machine Learning Pipeline

As we know, Model deployment is traditionally handled by an engineering team. Data scientists pass these models to engineers for code refactoring and deployment.

You can pick any existing data sets and models, and deploy those models in your roost environment and consume them for actions.

You can also make use of MLFlow/Kubeflow.

Platform and Hackathon related FAQ's:

For additional info specific to ROOST, please visit https://docs.ROOST.io

1. Do I need to pay any money to register for the Hackathon? No. You do not have to pay anything to anyone to register yourself for any Hackathon on HackerEarth.

2. Do I need to have any specific qualifications to be a participant for the Hackathon? If you love to code, you should participate.

3. How do I submit what I have made for the Hackathon? You must develop the your submission using ROOST and submit it on HackerEarth as a GitHub or any public repository URL along with a short PPT and/or a video presentation (<5 mins) explaining what you have built.

4. I am registered. How do I get started?" First, participants must create a Username at https://roost.io. For individuals running 2 or more ROOST instances, you will need an additional Username at https://roost.io in order to demonstrate the ROOST Collaboration feature.

5. Where do I download ROOST Desktop? Please download ROOST here: MacOS | Windows | Linux

6. Do we need to have the entire idea fully working? The entire idea need not be fully implemented however, the submission should be functional so that it can be reviewed by the judges.

7. How is the environment? Will your environment support any language? Will you provide any IDE and DB for us to work on ideas? You must develop the platform on your local systems using ROOST Desktop and submit it via HackerEarth as a GitHub or any public repository URL.

8. Does one have to be online and available for the entire duration of the Hackathon? No, one does not need to be logged in on HackerEarth or be online for the entire duration. You can develop the application on your local system based on the given themes and then submit it on HackerEarth, on the specific challenge page.

9. Is there any specific technology I need to use to build my project? You have to develop your solution using ROOST. You can visit the Resource Center for additional details.

10. Do I need to give a demo for the product that I have built? If you want you can submit a small presentation or video that demos your submission; however it's not mandatory. If you are selected as a Winner, you may be invited to demo your hack at a Cloud Native event, details of which will be shared with sufficient advance notice.

11. A fully developed application need to have a solid backend for data storage like SQL, SharePoint etc. since its online, is it accepted to show only the prototype of it? Yes it's absolutely fine to submit just the prototype. If you use any database like MySQL or PostgresSQL you can also submit a database dump along with your submission. However, you are permitted to submit only a prototype.

12. If it is a team submission, does that mean all team members will have access to work at the same time? Yes, all team members can login from their account on HackerEarth at any time.

13. Who will own the IP(Intellectual Property) Rights to the product that I have built? The developer/developers of the project will have all rights and own the IP of the submission. However, all code needs to be in public domain (open source) so that it can be evaluated by the judges.