AWS patterns for humans

Юрий Дадычин

FE DM, Levi9

Yes, I'm a FE architect at Levi9.

And yes, I'm going to speak about AWS

WHY???

I've took AWS Certification training 

There was a lot of marketing

• EC, DB's, S3 and so on
• Licenses
• Availability 

I have spotted a some kind of pattern

• Pattern of hi-load and hi-availability app setup 
• Access control principles
• Applications which can be hybrid-ised

Let's introduce ourselves

• Who are using AWS among you?
• What are you using?

Cool, nice to know many of you know a lot about AWS

But for those who are far from AWS I'll run threw AWS

I'll start from idea

• IaaS

• PaaS

• SaaS

• I mean cloud computing 

Lambda

exports.myHandler = function(event, context, 
    callback) {

   console.log("value1 = " + event.key1);
   console.log("value2 = " + event.key2);  
   callback(null, "some success message");
   // or 
   // callback("some error type"); 
}

So what do we see?

• Application must be easy to scale
• Try to decouple app for scalable micro-services to have control on bottle-neck parts
• You can use hybrid server-DB set but consider lower latency 
• Use queues and notification based ISC(inter-service communication)
• Consider FE SPA as stand-alone application deployed aside of any of your application 

Well designed application

What is best for micro-services?

• Docker
• REST ISC in RAML or http://swagger.io/ or old fags WSDL
• http://microservices.io/

Couple words about FE and micro-services?

Yep, it's some kind of stand alone application

• https://github.com/stylesuxx/generator-react-webpack-redux
• https://github.com/angular/angular-cli#generating-and-serving-an-angular2-project-via-a-development-server -> Proxy To Backend(s)

{
  "/api": {
    "target": "http://localhost:3000",
    "secure": false
  }
}

Thanks