My GSoC’22 organisation was **CCExtractor** and the project I worked on was Beacon-Backend (Github repo). My mentors were Aadi Bajpai and Carlos Fernandez.

As soon I was accepted for GSoC, the community bonding period started. I started interacting with my mentor. We discussed and set various project milestones, pondered over how we were going to implement the required features. We decided that we’ll update the backend before the mid evaluation and complete all the cloud related deployment stuff before the final evaluation.

I setup the codebase and was pretty excited to get my hands dirty since this was my first GraphQL project and had not worked with AWS before.

0: Unifying the Master(express) and AWS branch…

…and fixing some small bugs.

Pull requests involved:

1. Unified the AWS and Express Branches
2. Merged Unified into Master!

Details of the work:

1. Subscriptions wont (automatically) be included in (resolvers.js) lambda versions, whereas they will (automatically) be included in express version.
2. Changed the scripts in package.json, a) start_aws to run index.js of aws version. b) start to run the express version.
3. Updated the resolvers to use mongoose 6.X and now both aws and express version share common files such as models, resolvers etc.
4. Serverless code lives inside /serverless .

This helped/will help us deploy the code later, because now any further change to codebase wont have to be duplicated for the two different branches.

1: N beacons 1 Group

<aside> 💡 Issue that tracked the progress.

</aside>

This task involved making new models, updating schema and resolvers. New Group model was added and the beacon model was made a sub-collection of this group model. Straightforward query and mutations to read and write to group model. New subscription “GroupJoined” was added to provide real-time updates about new joiners of the group.

1. N Beacons 1 Grp: PR1
   • Update existing models,
     1. Beacon model:
        1. New field, grpID = id of the group the beacon belongs to.
        2. leader is not same as the group’s leader. Here leader is the one who created it, which can later be changed using changeLeader() mutation.
     2. User Model:
        1. New field, groups = [ids of all the groups the user is a part of].
   • New mutations for creating, joining and fetching a group (changes to be done is resolvers and typedefs).
     1. createAGroup() , fairly straightforward, creating a new group with all the fields and saving it in the DB.
     2. joinAGroup(shortcode), Add the new member to all the beacons in the group, also use pubsub to publish this change.
   • Update the existing mutations, queries and subscriptions to incorporate group model.
     1. Update me query.
2. N beacons 1 Grp: PR2
   • Update the existing mutations, queries and subscriptions to incorporate group model:
     1. Update createBeacon() and joinBeacon() mutations.
     2. Fix Beacon query.
     3. Fix UserLocation subscription.
   • Add New Queries:
     1. Add Group Query.

This finished adding support for the new feature of groups, which was the target for the mid-evaluation. After some manual testing, we moved to deployment, so the frontend team can actually test it in the app itself.

2: Cloud Deployment Related

• Prepping the code for deployment.
  • Changes for deployment to work fine
  • Changes to enable deployment on AWS ec2 and lambda