Asaf Zamir – Chief Technology Officer & AI/Cloud Consultant. Founder of CloudExpat, AZdev. Author of Coder to CTO.

npm install -g serverless
npm install -g terraform
npm install -g mocha

Installing a global NPM package locally

npm install serverless

./node_modules/.bin/serverless deploy -v

ln -s node_modules/.bin/serverless serverless

./serverless deploy -v

Hashgraph Performance

• Bitcoin 2.5 TPS
• Ethereum 15 TPS
• Visa 1700 TPS (avg) to 4000 TPS (peak)
• PayPal 115 TPS

• Hashgraph 50,000 TPS - 250,000 TPS

Hashgraph Security

Hashgraph Governance - the council of 39

Between Cloud and Crypto

Why Crypto Valley?

What's Next?

Business Partnerships

Technological Partnerships

Bridging the gap

Examples of integrating Serverless with your existing Web App

Reports

1. Go to Lambda on your AWS Dashboard:
2. Choose "Author from scratch":
3. In your Lambda function, add the following code:

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

   'use strict'; module.exports.runReport = (event, context, callback) => { const response = { statusCode: 200, body: { message: 'Result: ', input: event, }, }; const mysql = require('mysql'); const connection = mysql.createConnection({ host: 'localhost', user: 'user', password: 'password', database: 'database', port: 'port' //if you remove this line port defaults to 3306 }); connection.connect(); connection.query('SELECT * FROM users', function(err, results) { if (err) throw err; response.body.message += JSON.stringify(results); response.body = JSON.stringify(response.body); callback(null, response); }) connection.end(); };

4. As an easier alternative, get the entire Serverless Boilerplate here

Admin Panel

• Restrict Admin functions permissions - Since Lambda functions have their own IAM roles, you can have very fine-grained permission settings. A great example of this is with DynamoDB.
  You can literally give your function access to specific tables with a custom IAM policy:

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

  { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1509470869566", "Action": [ "dynamodb:BatchGetItem", "dynamodb:DescribeTable", "dynamodb:GetItem", "dynamodb:GetRecords", "dynamodb:ListTables", "dynamodb:Query", "dynamodb:Scan" ], "Effect": "Allow", "Resource": "arn:aws:dynamodb:YOUR-REGION:YOUR-AWS-ID:table/TABLE-NAME" } ] }

  Or another great example where a function can only write items to the table without reading any:

  1 2 3 4 5 6 7 8 9 10 11 12 13

  { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1509470869566", "Action": [ "dynamodb:PutItem" ], "Effect": "Allow", "Resource": "arn:aws:dynamodb:YOUR-REGION:YOUR-AWS-ID:table/TABLE-NAME" } ] }

  
  
  
• Combine API Gateway with Cognito User Pools for authentication - This is quite complex, but this guide has a pretty good walkthrough. In the following days (probably weeks) I'll try to add this to the boilerplates repository.
  
  
  
• Write the entire Admin Panel on Serverless - If your app doesn't have a fully fledged Admin Panel yet (and you understood the last 2 items on the list), This could offer both a high level of security as well as a great way to integrate Serverless into an important but not-yet-customer-ready parts of your system.

Cron Jobs

1
2
3
4

api.addFiles([
    'client/page-login.html',
    'client/page-login.js',
], 'client');

1
2
3
4
5
6
7

<template name="PageLogin">
  <form id="login-form">
    <input name="username" type="text" />
    <input name="password" type="password" />
    <input id="submit-login" type="submit" />
  </form>
</template>

1
2
3
4
5
6

Template.PageNewDomain.events({
  'submit #login-form': function (event, template) {
    event.preventDefault();
    //handle form submission..
  }
});

How it should work

• Each View in the views/ folder has a name, let's create a corresponding JS file with the same name
• On Sails.js, JavaScript files are stored separately in the js/ folder, let's store all view-specific JS files under js/views/
• JS filenames should be the same as view filenames. views/dashboard/login.ejs will have a JS file named js/views/dashboard/login.js
  

How to implement

• add this to config/views.js:
  

  1 2 3 4

  locals: { existsSync: require('fs').existsSync, jsPath: __dirname + '/../assets/js/views/' }

  This is so that we're able to check if a JS file exists.
• on the bottom of views/layout.ejs, under blocks.localScripts

  1 2 3

  <% if (existsSync(jsPath + req.options.controller + '/' + req.options.action + '.js')) { %> <script src="/js/views/<%= req.options.controller + '/' + req.options.action %>.js"></script> <% } %>

• In tasks/pipeline.js in the jsFilesToInject array, we need to remove

  js/**/*.js

  This is Critical. Otherwise, all JS files under js/views will be automatically included in ALL views.
  Instead, to automatically inject other views we can have the following line:

  js/dependencies/**/*.js