Spike: Review legacy DSNP gateway and social web demo to map out services

[p5150j]

Objective: Review legacy DSNP gateway and social web demo to map out services.

This spike is to take the existing social web demo and dsnp-gateway prototype and see what services we have now that could feed the social web demo, what services need to be built (eg: account service) and of the services we already have built define any additional enhancement we would want to make.

Repos for social web demo and dsnp-gateway prototype:

• Gateway Template App Backend: https://github.com/AmplicaLabs/dsnp-gateway-prototype
• Gateway Template App Frontend: https://github.com/AmplicaLabs/social-web-demo

Services repos we already have built:

• https://github.com/AmplicaLabs/graph-service
• https://github.com/AmplicaLabs/content-watcher-service
• https://github.com/AmplicaLabs/content-publishing-service
• https://github.com/AmplicaLabs/reconnection-service

Spike output: (timeboxed 3 days)

Based on: https://github.com/AmplicaLabs/dsnp-gateway-prototype/pull/4

• [x] #4
• [x] #3

[wilwade]

Questions from 2024-03-12

• Is the backend template going to use Nestjs or straight Node/Express?
  • Answer: Node/Express
• How we want to do sessions?
  • Phase 1: Simple Session inside of the Gateway Template App Backend or account service
  • Phase 2: Investigate OpenId inside of the Account Service (or other Gateway production service)
• Do we want to build a frequency package for the Gateway Services to consume?
  • Could
• Do we want to build a frequency blockchain package for the Gateway App Template to consume?
  • Not for Phase 1
• Do we want libraries for the Gateway services?
  • Instead of libraries we have OpenAPI specs
  • Perhaps each of those publishes the json spec (Future: Publish to npm & make sure they are part of the releases etc...)