Take care the serverless architecture and graphql

[mehmetaydogduu]

I've reviewed the source code and it's really spectacular. I found 3 problems in mastodon like other Rails apps.

1. API

• Serializers is slow.
• View not using same fields for all versions of a component. Sometimes unnecessary fields are returning from api and we are not using it on the view. We cannot develop a serializer for each variants of a component.
• Business Logic and Serializing Data intertwined in the code.

2. Domain Isolation

• Separating services by domain makes it easier to scale and maintenance. That's why micro service architecture is born. The follower system and like system must be separated. Also counting views of a post must be separated than sending post to client.

3. High scalability and high availability

• Some services are under heavy load, some services are not. So while image upload service having 2 instances, search service can need more than 2 instances.
• Also for an app that consuming traffic worldwide, we need copies of our services in both Asia, Europe and America. So a service discovery tool is needed.
• Also having only one PostgreSQL instance is a problem.

Final: I suggest you take a look at the following technologies.
https://serverless.com/
https://hasura.io/
https://traefik.io/