OAuth 2, Objectstore Backing in Apache Brooklyn, a Beacon App Infographic and more from the Sponsored Feed
Here is the latest from the New Stack sponsored feed, which appears at the bottom of every post. The items in the sponsored feed link back to the sponsor’s blog. The more the sponsor posts, the more their posts appear at the top of the feed.
New Relic: Democratizing Government Data: A FutureTalk with Chris Rieth [Video]
Chris Rieth spoke as part of New Relic’s Future Talk series in Portland about open data and the work he did for the Maryland governor’s office, where he drove open data programs aimed at reducing violence in the city of Baltimore. “Under its ComStat program, the city saw the largest reduction in violent crime of any city in America, and those trends held even through the Great Recession. Chris currently works to replicate Maryland’s success as a product manager for Socrata’s GovStat program, which helps governments build their own open data portals.”
Cloudsoft: Objectstore-Backed Rebinding in Apache Brooklyn
Apache Brooklyn has recently been updated to include ObjectStore-backed rebinding. It’s a high-availability feature that “allows multiple Brooklyn management nodes to be run in a master-slave(s) configuration.”
A new ebook by Apigee’s Ed Anuff explores how a business and its interactions have transformed with the advent of data and how it is accessed—through a mobile app, a kiosk, and an ever-expanding network of “things” that are increasingly available. “This transformation has significant implications for enterprise architecture, which must move from delivering web apps as the primary interaction channel to powering interactions across multiple interactive touch points, of which the web is just one.”
Tidemark: Planning for Nightmare Scenarios—But without the Nightmares
Caroline Japic, Tidemark’s chief marketing officer, writes about avoiding disasters by doing scenario planning. Her post summarizes the perspective of CEB’s Peter Young, who offers a 10-step guide for scenario planning. “Young’s idea is that, with the right methodology in place, it’s possible for companies to anticipate and blunt the damage caused by future calamities—and possibly even turn some disasters into revenue opportunities. To achieve this with some reliability, they need to combine some core best practices, a good dose of procedural structure, cross-disciplinary talent and data-driven models, and then apply all these to the process of predicting likely scenarios.”
Here’s Japic’s summary of the guide:
- Formulate the most important problems you’re likely to face and the most crucial decisions you’ll need to make.
- Create a team representing the key disciplines across your company.
- Generate a list of major future drivers or the events and influences likely to impact your business.
- Refine and rank these major driving forces.
- Establish the nature of the “alternate worlds” your company may face, including the logic and framework needed to test scenarios.
- Create a quantifiable model based on the scenario’s major forces.
- Gather data and quantify your assumptions, including historical data, internal structured data, and external unstructured data—everything you need to make assumptions that mean something.
- Run the model you built based on the what-if scenario framework you designed.
- Create data-driven narrative scenarios and outline your opportunities.
- Present your results to senior management.
The question becomes how to manage this scenario planning and how to avoid the manually intensive work that comes with managing information through static controls such as spreadsheets.
Digital Ocean: Integrate Your Apps with Our API Using OAuth
OAuth 2 is now supported by Digital Ocean. According to the company, the new OAuth flow, available in APIv2, is much better suited for web applications, as users can safely and easily provide access to their accounts through a DigitalOcean authorization request page:
Prior to OAuth support, applications that used the API required users to supply their personal access token, a manual and inconvenient process. The new OAuth flow, available in APIv2, is much better suited for web applications, as users can safely and easily provide access to their accounts through a DigitalOcean authorization request page.
Digital Ocean is providing an open-source OAuth strategy, available on Github and published to RubyGems. “Based on OmniAuth, the widely used Rack-based library for multi-provider authentication, the gem is an easy way to integrate ‘sign in with DigitalOcean’ into Rails and Rack frameworks. We are excited to join the growing list of providers with OmniAuth strategies.”
A post about the different forms of beacon technology as told by an infographic. For reference, 400 million devices are now beacon enabled, and that’s from Apple alone.
Adallom also has a post from earlier this month about its perspectives on shared responsibility.
New Relic, Cloudoft, Tidemark, Apigee, Digital Ocean and Kinvey are sponsors of The New Stack.
Feature image via Flickr Creative Commons