| const urls = { | |
| "":"", | |
| "sec-job0": "https://www.youtube.com/watch?v=T7MnJOfOVcY", | |
| "sec-overview": "https://d0.awsstatic.com/whitepapers/aws-security-whitepaper.pdf", | |
| "aws-tue": "https://www.youtube.com/watch?v=AyOAjFNPAbA", | |
| "gist":"https://gist.github.com/jfaerman/546902c79d21e53c3a724d00a30566f2" | |
| } | |
| function lookup(path) { | |
| var url = urls[path] |
Event info: https://www.meetup.com/Barcelona-Amazon-Web-Services-Meetup/events/241356452/
This gist: https://gist.github.com/jfaerman/5ef93929bca38f2eaacc8d255fb504b6
Me: Julio Faerman - https://twitter.com/jmfaerman
Live Stream: https://www.twitch.tv/jmfaerman
Today goals:
Today´s episode notes:
The decision between SQL and NoSQL databases can be challenging in new projects with great expectations. Choosing the comfort of SQL, one risks not reaching the proper abstraction or scale. Daring a new NoSQL database, developers usually face the learning curve of new abstractions, APIs, query languages and system operations. In this broadcast we will add and scale an SQL database, consider their usage tradeoffs and related services.
http://blog.julien.org/2017/03/exploring-gdelt-data-set-with-amazon.html
https://github.com/juliensimon/aws/tree/master/athena/gdelt
| In this broadcast we continue to develop the “cornerstone” of our serverless application. We already addressed content delivery, API invocation and authentication. The next step is storing structured data with DynamoDB and complete our template of a typical application transaction. After this episode, we will have all the components required to build our first features and improve our application towards more complex scenarios. | |
| # Introducing DynamoDB | |
| http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ProvisionedThroughput.html | |
| # Creating tables and indexes | |
| # Storing and deleting items | |
| # Querying and Scanning tables |
Este documento: http://bit.ly/awsnosqlba
Julio Faerman - http://twitter.com/jmfaerman
Crie uma conta no qwiklabs https://amazon.qwiklabs.com
Registre-se para acesso aos labs com o mesmo email do qwiklabs https://goo.gl/forms/T6D436ZEqGimPDSn2
In the previous episodes we implemented the fundamental components of a tyical web application: "static" content and "dynamic" APIs. For each component, we´ve been using the most out of AWS services, such as S3, CloudFront, Lambda and API gateway. But so far we have only been working with public resources. Let us now learn more about user authentication and authorization in two very important services: AWS Identity and Access Management and Amazon Cognito. Even more importantly, let us integrate that within our React application ;)
After creating and publishing a static website in the last broadcast, today we'll develop a web application API to compute and access dynamic data. Starting by the basics of interface design and serverless compute, we´ll explore the most relevant aspects of application integration with AWS backends.
Today's broadcast starts 4pm GMT ( check your local time http://bit.ly/2mLj30j ) and will include:
https://aws.amazon.com/about-aws/whats-new/2017/03/aws-lambda-supports-node-js-6-10/