Please enable JavaScript.
Coggle requires JavaScript to display documents.
microservices project / thesis - Coggle Diagram
microservices project / thesis
architecture
deployment
on-premise
kubernetes
cloud
serverless framework
communication
event bus
nats
kafka
gRPC
application technologies
database
sql
yugabyte
nosql
cassandra
mongodb
arangodb
rethinkdb
couchbase
couchdb
search
elastic search
neo4j
caching
redis
backend
nodejs
golang
frontend
web
react
mobile
flutter
react native
testing
jest
cypress
auth
keycloak
auth0
color code
nice to have / nice to do
making a decision on
decided
maybe later for another project
not suitable
use case
octopus
services
users
you have to research what kind of tags are needed from users to make the matching with the surveys like they are doing right now. is it just age, gender, education, income, marital status? or something more?
matching
how are you going to handle the problem with a user being given a survey and then it not being completed in time? how is re-matching going to be done?
rewards
surveys
how much freedom or rather options are you going to give to the clients when creating their surveys? just standard fields or custom fields depending on their feedback after using the app?
answers/analytics
offer 3 tiers of services to clients.
(cheapest) the client agrees that the data he receives from the users will be shared with octopus. BUT octopus will have to bear paying the difference in price with the hope that it will pay off when it will launch the dream-tier
(mid-tier) only the client will hold the answers but he will be paying the full cost of the user getting his reward, paying octopus for the running costs and the profit
(dream-tier) not needing to create a survey, but having the ability to query on historical responses
joana's project