FalcorJS and React - Speaker Deck

Slide 1

Slide 1 text

FA L C O R S I M P L I F Y I N G Y O U R D ATA @ H O LT B T BoJack Horseman

Slide 2

Slide 2 text

W H AT I S FA L C O R ?

Slide 3

Slide 3 text

Thug Life

Slide 4

Slide 4 text

FA L C O R I S A W E S O M E • Let’s you treat your local and remote data the same way • Takes care of fetching, caching, and cache invalidating for you • Framework / library agnostic (doesn’t have to be React)

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

PAT H S • Look just like normal object accessors • Ranges • "shows[0..2]['plot']" • Multiple properties • "shows[2]['title','plot']"

Slide 9

Slide 9 text

FA L C O R A N D R E A C T • Allows your components to declare their own data dependencies • Alleviates the data tunneling problem

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

MovieList Movie Title Year Plot

Slide 12

Slide 12 text

MovieList • Needs list of movies to map over • Needs ID for key

Slide 13

Slide 13 text

Movie • Needs nothing of its own

Slide 14

Slide 14 text

Title Year Plot • Title, Year, and Plot components need the title, year, and plot pieces of data respectively • Nothing else

Slide 15

Slide 15 text

S P E N D L E S S T I M E W I R I N G U P T H E A P P

Slide 16

Slide 16 text

S P E N D M O R E T I M E O N T H E A P P

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

• No black magic • No mixins or helpers (other than lodash) • You already understand how it works • You can still use the components even without the queries • Don’t like the way I did it? Hack your own solution. You have all the tools.

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

FA L C O R S E R V E R • Aims to be very RESTful in its implementation • Best used to retrieve small amounts of data you can paginate over • Not terrible to implement

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

L O L M I C R O S E R V I C E S

Slide 29

Slide 29 text

FA L C O R D O E S A L O T O F O T H E R C O O L S T U F F • Create, update, and delete are no problem too. Easy even to batch multiple actions at once. • Smart caching so if you request the same info twice, it will pull from the cache. • Easy also to send cache invalidating logic from the server

Slide 30

Slide 30 text

Brian Holt @holtbt