IoT Challenge: Building APIs That Last in Node.js

[inadarei]

For decades now, we, computer programmers, have borrowed, copied and imitated the terminology and mannerisms of civil engineers. We even call ourselves "engineers".

But truth be told, “software engineering” was never really like the architecture of buildings or bridges. In the "real" architecture the cost of a mistake is sky-high: if you make a mistake — buildings will collapse, bridges will sink. In software engineering the cost of a "mistake" was always significantly lower: the predominant philosophy taught us to "just ship it” — we can fix mistakes, later, relatively cheaply.

With the rise of the Internet of Things, potentially millions of apps and devices will use APIs that we build. Any breaking change in our API can have severe effects on millions of consumers. The cost of making an early design mistake, the cost of a sloppy architecture is rising rapidly.

Let's talk about how to build long-lasting APIs in Node.js and be ready for the IoT challenges.

[dscape]

@inadarei very curious about your IoT experience. Build quite a bit on the IoT space. Maybe skype sometime?

[oroce]

Hey, our cfp is closed now, but it would be great to have this talk. We are doing a preevent meetup on Wednesday before the OneShot. We can offer you a free ticket to the conference (no accommodation).

[inadarei]

Thank you Róbert, unfortunately I will be in London for an API summit at that time, but I appreciate your offer. We'll do it next time. Best of luck with the event and thanks for the consideration.

[oroce]

thanks for letting me know. Have a great time in London.