15 Results Found
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.
Unlike ITIL, DevOps is more of a philosophy than a formal framework. DevOps, which is short for Collaboration between Development and Operations, arose as a movement within IT best practices when IT managers began to realize that something needed to be done to close the communications and collaboration gap between development groups and support operations staff. After some time and examination, it became clear that there was no inherent conflict between the DevOps movement and ITIL—the two, in fact, are quite complementary.
This article addresses non-technical skills you need to do to be a success in IT.
General character attributes every IT pro should have and on the things that every IT pro should know or do.
Let's look at 10 ways the cloud will change (and to a large degree already has changed) the world.
It’s inevitable. At some point in your career, you’ll find yourself working alongside individuals who fall into the general category of “Difficult People.” The effects these people can have on an organization vary greatly but usually involve many problems for the team. This white paper describes some of the more common types of difficult people and provides you with tips on how to handle them.
Get an insider’s take on 2017 cloud computing, DevOps, and Internet of Things (IoT) trends from an industry expert.
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.