Skip to content
This repository has been archived by the owner on Nov 7, 2020. It is now read-only.

feat: moving api services to microservices pattern #201

Merged
merged 32 commits into from
Sep 8, 2019

Conversation

mentos1386
Copy link
Member

@mentos1386 mentos1386 commented Jul 3, 2019

Closes #126
Closes #96

TODO:

  • Move to own packages
  • Decide on grpc or events for connection between services; Will use GRPC
  • Fix code to reflect types from grpc/events
  • Implement HTTP or GraphQL gateway; Will go with HTTP for now
  • Implement health checks for all services
  • Implement k8s services/deployments/ingress and setup up istio for all services
  • Fix circleci to build all the services
  • ⚠️ Reevaluate JWT authentication changes. Make sure that only tokens obtained through our authentication flow can be used to access api. ⚠️

@mentos1386 mentos1386 self-assigned this Jul 3, 2019
@mentos1386
Copy link
Member Author

mentos1386 commented Aug 18, 2019

Next thing to do:

  • Look in to events, specifically, how should we handle notification creation and delivery of them to websocket services.
  • remove all cqrs things
  • Modify all services to be Hybrid services, so that they can be on grpc and redis at once. + we will need http for health check
  • Create AuthenticationService
  • Create events on notification creations
  • Make sure everything builds using docker (.dockerignore issue...)
  • API Gateway

@mentos1386 mentos1386 merged commit f61451e into master Sep 8, 2019
@mentos1386 mentos1386 deleted the microservices-126 branch September 8, 2019 21:05
@mentos1386
Copy link
Member Author

Merged as preparing to work on infra and ci. Will need to build and push images to registry.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Microservices? API Gateway? Security issues with using EVE SSO tokens for authentication
1 participant