noBackendCreating JavaScript applications without a server

nathangloynnathans.dropbox@gmail.com@NathanGloyn

Design Code Release

Agenda• What is a noBackend application• Why would you create a noBackend app• Options• Cost• Things to be aware of• Building an application• Summary• Questions

definition: noBackendnoun1. Computing: system created without a server component

adjective2. Computing: denotes type of computer system where the developer creating an application only creates the UI using services to provide the server component functionality

Services on offer

Phantom Ranch Canteen Menu Board - Grand Canyon by Al_HikesAZ used under CC BY

noBackendor

Unhostedor

Static appsor

Backend as a Serviceor

Front end driven applicationsDerivative of Confused? by Joe Benjamin used under CC BY

What’s in a name…

What’s the difference?

Derivative of Meditating by Staffan Scherz used under CC BY

Philosophy

What’s the difference?Personal

Derivative of Hotel Swimming Pool by Steve Hall used under CC BY

Options

Options by David Goehring used under CC BY

Providers

Why?

It Looks Insoluble by David Goehring used under CC BY

Why?

Simple Hosting

shoebox by How can I recycle this used under CC BY

Why?

Leverage your skills

Head Skill by Aikawa Ke used under CC BY

Speed to market

Why?

Derivative of Piggy Bank by TaxCredits.netused under CC BY

Cost

Derivative of Cash Register by Taber Andrew Bain used under CC BY

Cost

Kicked In the nuts by Superbk12

Gotcha’s

Things to be aware of

Worried Eggs I - Oh! My! God! by Domiriel used under CC BY

Things to be aware of

Security

Things to be aware ofReliability

Grandfather's pocketwatch inner workings by Kevin Trotman used under CC BY

Things to be aware of

Shared resources

By Michael Yamashita used under CC BY

Things to be aware of

cockpit controls - over the pilot's shoulder - _MG_5187 by Sean Dreilinger used under CC BY

Control

Building an application

Segal Self Build Course by Rob Annable used under CC BY

How?• Focus on client related technology• Provider library/SDK may use specific patterns• Think about how application may evolve

Anatomy of a noBackend app

• Static files• HTML 5• Javascript• Utilise online services• Offline first

• Native app• Device specific• Language of your choice• Utilise online services

Web Mobile

Basic• Static files only• Using local storage• Good for• Testing idea• Soliciting feedback

Code

Remote Storage• Personal storage• Infrastructure for storage & working with your data• Currently draft to be accepted as standard protocol

Code

Firebase• Authentication• Data storage• Basic User Management• Hosting• Analytics

Code

Web Task• No code on the server• Code hosted elsewhere• Client passes web task to server for execution

Summary• Application where you don’t create a server• Many providers with differing functionality• Reliant on provider• Initial costs low but can increase• Focus on client related technology

Questions?

.: Any question??? :. by Marcello Maria Perongini used under CC BY

Resources• To-Doge implementations• Basic: http://bit.ly/to-doge• Remote Storage: https://to-doge.azurewebsites.net• Firebase: https://to-doge.firebaseapp.com/

• Code Repo: https://github.com/NathanGloyn/to-doge• Remote Storage: https://remotestorage.io/• Firebase: https://www.firebase.com/

nathangloynnathans.dropbox@gmail.com@NathanGloyn

Design Code Release