This talk will cover the high-level design of Kinesis, how it scales, how clients can retrieve records that have been stored in it, and the use of Kinesis Analytics to to transform data and extract outliers.
Data has different purposes over time: when fresh, it can be used for real-time decision-making; as it ages, it becomes useful for analytics; eventually, it becomes a record, useful or perhaps not. Each of these stages requires a different approach to storage and management, and this talk looks at appropriate ways to work with your data at the different stages of its life.
This talk will review two common use cases for the use of captured metric data: 1) Real-time analysis, visualization, and quality assurance, and 2) Ad-hoc analysis.
In this session we will walk through the steps required to securely communicate with your device using the Device Shadow service. This will include an overview of user authentication and authorization, connecting to AWS IoT, and using MQTT to communicate with the device’s “Device Shadow” to read and update its state. All this, using the AWS Amplify CLI and SDK.
This presentation will take you through the biggest areas where you need to focus your efforts in order to keep your data safe in AWS, and will show some real-life examples of what could go wrong if you make compromises or allow bad practices.
Amazon uses a “pay as you go” pricing model: you pay for the resources that you use, and in most cases don’t need to pre-allocate resources. While this allows your business to scale, it means that each component of your data pipeline will incur a separate charge, which can obscure the overall cost of running the pipeline. This talk will examine those changes, along with strategies for partitioning those costs between your clients or organizational units.
Ken Rimple’s talk on GraphQL for BarCamp Philly 2019 covered the query language, clients and servers, and some thoughts about application of the API.
What is the Internet of Things? Does adding the internet to a device (or thing) make it better or does it just create more problems?
GraphQL is a client/server API specification for submitting queries, updates and subscribing to data, and it’s been an interesting replacement technology for JSON in single page applications.
In 2009, Amazon Web Services was simple: EC2 for compute, S3 for storage. In 2019, it’s far more complex: well over 100 services, covering the entire software life-cycle. This talk is intended for the person who is looking at AWS as an alternative to running in a data center, and focuses on the important topics and strategies for a successful migration.