Critical Service
Large nodes have more dependents
Node been dragged

Hootsuite Microservice Challenge

Problem: build a system using Graph DB to represent microservice dependency graph. Imagine 100s of microservices calling each other on different API endpoints using REST, how would you know which service depends on another? how often API calls are being made from one service to another? Does one service always call all endpoints of another service, or usually just one or two etc…?

Components

The proposed solution consists of three repositories. One for the API server, one for data visualization and another one as a library to allow easy integration with WSGI applications.

Inside each one them there is a readme explaining its functionality in details.

The tasks were splitted between the members in the following way:

Fernando Marcio fernandomarcio13@gmail.com: Python WSGI library and API server.
João Gustavo gagu2030@gmail.com: Graph visualization frontend and Graphics design.
Marcus Vinicius mbodock@gmail.com: API server.
Tiago Ilieve tiago.myhro@gmial.com: API server and infrastructure.

The full project description is on Github repositories.

Built With

Submitted to

VanHackathon

Created by

Backend Development with the API. Integration tests, Q&A.

Marcus Martins
I've worked on the Python WSGI library and API server.

Fernando Matos
I worked in Graph visualization front-end and Graphics design from project.

João Gustavo Vieira e Silva
I've worked on the API server, dealing with the Redis backend and together with Fernando and Marcus on Neo4j. Some infrastructure details, like running services on Docker and adapting the application to run on Heroku were also done by me.

Tiago Ilieve