REST is simple, but it...

• Focuses on use cases
• Can bloat quickly
• Couples consumers & providers

A REST endpoint

teams/1

{
    name: 'FC Barcelona',
    city: 'Barcelona',
    country: 'Spain,
    stadium: 'Camp Nou',
    manager: 'Luis Enrique'
}

A REST endpoint (cont.)

teams/1

{
    name: 'FC Barcelona',
    city: 'Barcelona',
    country: 'Spain,
    stadium: 'Camp Nou',
    manager: 'Luis Enrique',
    president: 'Josep Maria Bartomeu',
    website: 'http://www.fcbarcelona.com/',
    leagues: [
        {
            name: 'La Liga',
            ...
        },
        ...
    ],
    players: [
        {
            name: 'Lionel Messi',
            nationality: 'Argentina',
            position: 'forward'
        },
        {
        },
        ...
    ],
    trophies: [
    ],
    ...
}

Example of GraphQL

{
    team(id: 1) {
        name
        stadium
        manager
    }
}

{
    team: {
        name: 'FC Barcelona',
        stadium: 'Camp Nou',
        manager: 'Luis Enrique'
    }
}

Example of GraphQL (cont.)

{
  team(id: 1) {
    name
    manager
    website
    leagues(country: 'Spain') {
        name
    }
    players(first: 5) {
        name
        position
    }
  }
}

{
  team: {
    name: 'FC Barcelona',
    manager: 'Luis Enrique',
    website: 'http://www.fcbarcelona.com/',
    leagues: [
      {
        name: 'La Liga'
      }
    ],
    players: [
      {
        name: 'Lionel Messi',
        position: 'forward'
      },
      {
      },
      ...
    ]
  }
}

Comparison

source: https://medium.com/apollo-stack/why-graphql-is-the-future-3bec28193807#.3qw13ibx4

Advantages

• Clean API
• Efficient communication
• Easier documentation

Challenges

• Complexity
• Security
• Caching

see also: https://edgecoders.com/graphql-deep-dive-the-cost-of-flexibility-ee50f131a83d#.hhitxfcwb

More logic in Frontend?

Ideas to the extreme

• Code review -> Pair programming
• Unit Test -> Test driven development
• Frequent delivery -> Continuous delivery

Serverless app

• FaaS (Amazon Lambda)
• Write functions, pay per execution*
• Forget about managing servers

see also: http://blog.serverless.com/defining-serverless/

* Java, JavaScript and Python are currently supported in Amazon Lambda

Advantages

• Focus on business logic
• Reduce cost
• Auto scale

Challenges

• Organize code effectively
• Vendor lock-in
• Different security and identity models
• Loss of control

There's an app for everything, but...

I don't want to install 1000 apps on my phone

There might be a website for it, but how do I find it?

• Search engine
• Displayed URL
• QR Code

Beacons

• Broadcast content (URL)
• Long battery life (Bluetooth LE)
• Small

see also: https://google.github.io/physical-web/examples

Enables interaction when native is not practical

Any physical web devices nearby?

Advantages

• Opens like a web
• Just a web page
• On-demand
• Scales

Challenges

• Spam?
• Phishing?
• Thousands of beacons?

Challenges with HTTP

• Inefficient and expensive
• Humanity's history is deleted daily
• The web's centralization limits opportunity
• Our apps are addicted to the backbone

InterPlanetary File System

...IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository

source: https://en.wikipedia.org/wiki/InterPlanetary_File_System

Usages

• Preserve knowledge
• Spread knowledage
• Deliver content