Resource Library

As far as modern architectures go, there are few more complicated than an IoT pipeline. You’ve got to consider an ingestion layer (typically streaming) that may undergo manic load. You’ve got to think of data tagging, storage (probably across multiple engines), archival and access—both internal and external. And all of it has to scale like crazy, be as cost effective as possible, and use automation wherever it can. Oh, and your boss needs the IoT pipeline built by tomorrow. Short timelines? Tight budget? Unrealistic expectations? Unfortunately, these asks are realities for many cloud professionals. AWS knows this and is here to help.  

Resource management is always an issue in any project, especially when the stakeholders from whom we need time have operational duties to perform.  If our requirements team was at our disposal 100 percent, always completed activities on target, and worked a full eight hour day without distraction or a loss of productivity, then estimating time would be simple. In this paper, we explore standard approaches to time estimation, the dangers of multi-tasking, and estimation alternatives, which consider work habits and productivity norms.

Like it or not, Internet of Things (IoT) is upon us. There are a number of factors that will impact its adoption rate, and the inevitable privacy (or lack of) discussions will likely happen sooner than later. This is going to change the world as we know it, in many cases for the better. But we will need to keep an eye on the extent to which it invades our personal lives if it is going to be the positive force it has the potential to be.