L'open source m'a tuer*

L'opensourcem'atuer*?
HTGrenoble Février 2019 - @sabativi

VictorSabatier
Freelance Web and mobile
developper.
Build stuﬀ using Meteor,
GraphQL, React and React native.
Love learning and sharing
victor@reactivic.com

Disclaimer:Iloveopen
sourceYou should contribute, use and have fun with it.

A story of open sourcing a project that
went wrong.

Two technologies involved :
· React Native.
· GraphQL.

IloveGraphQL
· Promise is amazing.
· Tooling is amazing.
· Community is amazing
Iwanttouseiteverywhere

November2017:newproject

Customer : I want a mobile app and I have
already a REST API.
· Me : I want to use GraphQL, can you put an API
for me ? It will be easier and cheaper.
· Customer : Euh...
· Customer: Nop.
· Me : Ok no problem. I will use more standard
technologies.

But wait, what if we can specify in our
GraphQL queries to fetch data from
REST.

GraphQlquery
{
users {
id
name {
first
last
}
emails {
address
}
}
}

{ {
users { users @restAPI(type: "User", endPoint: "/users") {
id id
name { name {
first ---> first
last last
} }
emails { emails {
address address
} }
} }
} }

POC

!
POC was working well, in both React and React
Native environments.
!

My real vision for this project was to enable
people to start using GraphQL on the client
without having to change anything on the
backend.

Advanced example

Celebration

· Hey, this is peggy from Apollo, we will love
make it available within our own github org.
· We started having a huge traction, starting to
have many contributors...
· Many new issues, PRs

Sowhatwentwrong?

RESTisnotastandard.
By accepting contributions, we have tried to fit every use cases of
a REST API into our lib.

It requires some computation power
to transform all possibles ways of
writing a REST APIs into something
standard for the graphQL client
cache.

WhyitisaproblemintheReact
Nativeenvironment?
On the web, it is working well.

Meetthebridge

Principle

Whathappens
· I make a query -> results arrived.
· It is transformed to fit into graphQL client cache
· JS thread ( can be ) blocked while doing so.
· No new UI rendering possible, UI is
unresponsive.
· CPU spike -> battery melt away.

Conclusion
· Open Source is not the problem
· I am
· I did not manage to keep the project as simple
as I first wanted.
· API was also a badly designed.

Thanks

L'open source m'a tuer*

More Related Content

What's hot (16)

Similar to L'open source m'a tuer* (20)

Recently uploaded (20)

L'open source m'a tuer*