When Scott Fulton looks the data center, HPC, infrastructure and next gen architecture, he focuses on the big picture.
Where we re-introduce ourselves to the two types of rules that are typically considered "business logic" in an organization, and gauge whether there's time to translate them both into modern data streams before another orchestrator comes charging in.
Where a component described simply enough as a "messaging queue" strikes at the nerve center of organizations' long-standing three-tier applications, and calls into question whether certain of their principal functions still matter.
Where the database market's equivalent of a commando raid brings a new actor to center stage, with the incentive and the opportunity to upset the balance of power and rewrite the rules of the data center.
Where an IBM engineer who helped steer her company away from locked-in, proprietary, vendor-driven data platforms, steers a new course for herself, not only building a new model for live, streaming data but possibly setting a new precedent for vendors.
Where data warehouses establish the patterns that business models follow for decades, and the need for scalability makes obvious the case for obsolescence.
Where we take stock of the long journey into the eye of the DevOps storm, and examine the truths that emerged during our travails.
Where the fellow who introduced DevOps to a generation of enterprises finds his services exclusively acquired by one of them, and the challenges to modernizing the business suddenly look very different.
Where one of the world's most recognized broadcasters makes a technological breakthrough that could save it from obsolescence, and the facilitators of that breakthrough discuss whether it did so the right way.
Where the ideal of automation itself seems capable of being automated, packaged, and marketed, and a debate ensues over whether such processed packages of processes can retain their innate humanity.
Where a post-war college researcher witnesses the birth of IT job silos two decades before the jobs themselves would be invented, and triggers a revolution whose objectives are literally all over the map.
We review the sweeping success of the orchestrator platform in 2017, and ponder what directions hyperscale data center development may take this year.
Where we look back at a month of intriguing questions and engaging answers, but where some of those answers may have been just responses rather than solutions.
If the addition of authentication and cross-checking policy enforcement creates too much of a negative impact on microservices behavior, then perhaps machine learning algorithms can be trained to spot that impact. But assuming they get that right, what do they do next?
If a cloud data center supports an orchestrator that's capable of spinning up dozens of the same microservice, and one goes wrong, how does it know which one? And how can an audit determine who's to blame? How far does identity go when identifying things that are things rather than people?
A months-old security firm has become the braintrust of engineers working to build the Software-Defined Perimeter -- a mechanism for enforcing firewall and access rules on a per-user level. How would SDP remake the ancient plan of the software fortress?
Data Centers
Micro-fortresses everywhere: The cloud security model and the software-defined perimeter
Data Centers
A data center with wings? The cloud isn't dead because the edge is portable
Data Centers
Have hyperscale, will travel: How the next data center revolution starts in a toolshed
Data Centers
It's a race to the edge, and the end of cloud computing as we know it
Data Centers
Searching for the perimeter in cloud security: From microservices to chaos