https://www.figma.com/file/qyHj71vccIZsiRckxq1Zxs/Supershare-Backend-Architecture?node-id=0%3A1

SuperShare tech serves three main content stakeholders - Sharers, Creators, and Consumers - through its various platforms - Android/iOS, Web, Backend, Browser extensions, Chat bots.

Some of the problems we are solving on the tech side:

• Scaleable gamification engine for content sharing.
• Dynamic scaling to handle burst traffic from creator campaigns.
• Cracking content syndication across top content platforms.
• Social graph to map out creator-sharer-consumer relationships.
• Internationalization of services.
• Modularization of ad-hoc engagement zones around content.
• Complete remote configurability of user journeys based on cohorts.

Backend

Application Server: Spring Boot (Kotlin) | NodeJS | GoLang

Databases: Mongo DB | ElasticSearch | Redis | Aerospike | Maxmind DB

Messaging Queue: Kafka

Monitoring and Alerting: Prometheus | Grafana | FluentD | Kibana | Sentry

Data: Hadoop | Scala | HDFS | Hive | Spark | Tableau

Infra: Docker | Terraform | Drone | Varnish

Our backend is hosted on AWS (EC2, S3, ECS, Route53, ALB, Cloudwatch, Lambda, MSK, Athena)

Main parts of the backend:

1. User Management: verified sharers + anonymous consumers, social graph.
2. Content Sharing: link conversion + customization, opens tracking, first order analytics.
3. Content Metadata: OpenGraph data.
4. Game Engine: Point system, reward management, badges, bonus cards, slot machine, raffle machine, leaderboards, fraud prevention.
5. Communities: Qualifying top fans, access gating, quickshare.
6. Remote Config: Audience based journey mapping.