urko
/
ess-etl-go
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: update report

This commit is contained in:
Urko 2023-04-11 09:00:49 +02:00
parent e9141e0f11
commit 9fe42609bb
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
benchmark_report/Report.md
View File

@ -26,6 +26,7 @@ GraphQL api + ETL on Nestjs took me 3-4 days do some pairing with my team mates
Full restAPI + ETL process Go took me 4h to develop everything without any trouble. Full restAPI + ETL process Go took me 4h to develop everything without any trouble.
I found quite hard using graphQL as I find selected architecture quite hard to comprehend and navigate with decission. I know if you are building a multi-tenant library or service is ok to make do more unit test, to pass mocks and use more interfaces: which is one of the most used things in go. I found quite hard using graphQL as I find selected architecture quite hard to comprehend and navigate with decission. I know if you are building a multi-tenant library or service is ok to make do more unit test, to pass mocks and use more interfaces: which is one of the most used things in go.
I also would recommend to read **[this blog](https://betterprogramming.pub/graphql-from-excitement-to-deception-f81f7c95b7cf)** which I found really interesting point of view about graphQL and it's real use case.
### XML issues ### XML issues