Slide 1

Slide 1 text

August 2019 @

Slide 2

Slide 2 text

Thank you!

Slide 3

Slide 3 text

The Company Mike McNeil @mikermcneil open-source MVC framework for Node.js creator of

Slide 4

Slide 4 text

❌ error ling @mikermcneil

Slide 5

Slide 5 text

Everyone has this problem.

Slide 6

Slide 6 text

Overly complex async logic Usually, you don't need this. Even at high scale, there are other, much more immediately-relevant performance and scalability bottlenecks.

Slide 7

Slide 7 text

Swallowing

Slide 8

Slide 8 text

Dealing w/ upstream services 3rd party APIs, servers maintained by other other internal teams ☁

Slide 9

Slide 9 text

the code

Slide 10

Slide 10 text

What's wrong with try/catch?

Slide 11

Slide 11 text

What's better than try/catch?

Slide 12

Slide 12 text

…in a Sails app

Slide 13

Slide 13 text

…in vanilla JavaScript Not using Sails? You can actually use the same approach, even in vanilla JavaScript.

Slide 14

Slide 14 text

npm install parley

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

.intercept()

Slide 17

Slide 17 text

.tolerate()

Slide 18

Slide 18 text

.retry() 㾾

Slide 19

Slide 19 text

.timeout() ⏳

Slide 20

Slide 20 text

sails.helpers.flow ⚗ (if time allows)

Slide 21

Slide 21 text

npm install flaverr (if time allows)

Slide 22

Slide 22 text

questions?

Slide 23

Slide 23 text

Thank you! @mikermcneil @sailsjs sailsjs.com