Table of Contents

Administrators and Mentors

We will list the potential mentors in this place. For now, if you have any questions, please contact the GSoC administrators:

George Zaronikas (gzaronikas) Ali Ok (@aliok_tr) and Anuj Garg (@KeenWarrior).

Communication channels

Gitter    : JBossOutreach/GSoC - Gitter 

Please take note - These channels are about generic doubts. For project specific doubts you will need to contact project mentors and channels specified in the project description.

Notes for students

Points to consider while choosing any project

1. You meet at least 50 percent of prerequirements. Remaining skills can be honed on the go, so don't worry if you lack some.

2. You can relate with the project idea and you have used something related to the project as user.

3. You are willing more toward learning the skills and less toward boasting about the skills you have already.

Suggested steps after choosing favourite project

1. Start to use product/tool/api as user or hello world client application.

2. Setup the development environment for project and start to use your own build.

3. Look for new comer bugs and try to get your head around them.

4. Let us know if you feel stuck at any stage.

Idea template (for mentors)

Project title

Summary of idea:

-Idea

-Feature A

-Feature B

Knowledge prerequisite: Languages/Technologies goes here

Github repo:

Skill level: Beginner/Intermediate/Advanced

Contact(s) / potential mentors(s): Mentor(s) name and contact details

Associated JBoss community project(s):

Idea Proposals

AeroGear - NodeJS based Data Synchronization engine on top of Apache Kafka, Debezium and GraphQL Subscriptions 

Summary of the idea:

GraphQL Subscriptions allow developers to build reactive data-driven applications where each client actively subscribes to new data and receive it immediately after is available.
However in traditional messaging systems when a client subscribes for the first time it is not 

going to get any previous messages. Purpose of this  will be to provide offline enabled data synchronization platform on top of GraphQL, Debezium and Apache Kafka 

Project references

Candidates are going to work closely with the JBoss community by contributing to the following projects:

• Graphback: https://github.com/aerogear/graphback
• Debezium: https://github.com/debezium/debezium
• Offix: https://github.com/aerogear/offix

Required knowledge

• Node.js (Understanding performance implications of event loop etc.),
• TypeScript 
• Basics of GraphQL, React
• Apache Kafka (Basic concepts, Consuming messages, Partitioning) 
• Knowledge of one of the relational and NoSQL databases (Postgress, MongoDB)
• Familiarity with the event streaming principles
• Engagement with AeroGear and Debezium communities is essential!

Definition of the problem

When building microservices architecture various parts of the system can interact with the source database. Using publishing events from the server application is not always possible and it might require modifications in various servers that are often legacy.

When utilizing Debezium and Kafka we can connect directly to the database to get notified about any change that happened in the database instantly.

Debezium will be only involved in collecting and publishing the data to Kafka. The purpose of this work is to build an opinionated Node.js layer that will consume Kafka messages to apply some specific filtering and publish messages back to clients using GraphQL subscriptions.

Possible goals:

• Introduce a stateful live query layer for Graphback based on Kafka stream (https://www.youtube.com/watch?v=g-asVW9JFPw)
• Check the performance of the solution and identify bottlenecks for scalability. (https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md#implementing-graphql-live-queries)
• Build a suite of the integration tests for various Graphback use cases
• Provide example app for Debezium
• Build a Node.js OpenShift template application for Graphback that can connect with Kafka
• Build out of the box subscription connector for Offix that will update underlying cache/db
  
  

Diagram: https://media.discordapp.net/attachments/632235423300714507/669530559701319691/Screenshot_2020-01-22_at_13.15.08.png

Technologies: Nodejs, GraphQL, AeroGear DataSync, React, Apache Kafka

Github Repo: 

Skill level: Intermediate 

Contacts / potential mentors: wtrocki@redhat.com 

Associated JBoss community project(s): AeroGear

EAT  - Testing Infinite Software Project Versions

Summary of idea:

The innovative part of EAT is creating the test once and testing with any version of the tested software. It may be firstly applied for the JBoss Servers, but, in general, a similar structure, can be used for creating tests about any software with multiple versions or for multiple software programs that have a part of the testsuite in common. EAT is a project under the ΙΔΕΑ statement.

Possible tasks for this project :

Go through the EAT workshop, extending the existing AT testsuites, creating a new testsuite using the AT Structures, improving the dependency AT analyzer (dynamic testing), etc

Github repo: https://github.com/jboss-set/eap-additional-testsuite

Contact / potential mentors: Panagiotis Sotiropoulos (psotirop@redhat.com)

Associated JBoss community project: EAT

Knative - A GraphQL subscription Knative source

Summary of idea:

Implement a Knative eventing source for GraphQL subscriptions.

• Create a subscription
• Receive subscription events
• Create CloudEvents from them
• Send those cloudEvents to other Knative resources, using the standard Knative mechanisms

Possible tasks for this project :

• Implement the source
• Implement unit tests, e2e test
• Implement performance tests
• Write documentation
• Prepare demos

Required knowledge

• Kubernetes
• Knative
• Containers and tooling (e.g. Docker)
• GraphQL
• Golang

NOTE: all the skills listed above are big things. We don't expect students to be experts in any of these. However, we expect students to have experimented with these technologies and have experience in majority of them.

Github repo: https://github.com/knative/eventing

Contact / potential mentors: Ali Ok (aliok@redhat.com)

Associated JBoss community project: Knative upstream

Knative - Scaling GraphQL Subscriptions on Serverless environments using Knative

Summary of idea:

GraphQL subscriptions work with websockets or some other persistent connection. When a mutation happens in the GraphQL engine, a subscribed client receives the event of that mutation over that persistent connection.
In the current case, the piece of software that sends the subscription events runs all the time.
How about scaling to zero if there are no subscribed clients?

This project will need some level of research in these areas, before the implementation:

• How to use Websockets with Knative
• How to scale resources with regards to Websocket connections
• See if KEDA could be used to scale the subscription manager

Possible tasks for this project :

• Implement the endpoint
• Implement unit tests, e2e test
• Implement performance tests
• Write documentation
• Prepare demos
• Investigate how KEDA could help

Required knowledge

• Kubernetes
• Knative
• Containers and tooling (e.g. Docker)
• GraphQL
• Websockets
• Golang (must)

NOTE: all the skills listed above are big things. We don't expect students to be experts in any of these. However, we expect students to have experimented with these technologies and have experience in majority of them.

Github repo: https://github.com/knative/eventing

Contact / potential mentors: Ali Ok (aliok@redhat.com)

Associated JBoss community project: Knative upstream