Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Michael Stal on May 15, 2011
SAP has recently introduced StreamWork as a cloud-based solution for collaborative decision-making. According to the German ERP company its product
brings together the people, information, and proven business approaches to drive fast, meaningful results.
The main purpose of the social networking application that reveals some similarities with Facebook is the cooperation within teams. Team members may share information, discuss upcoming business discussions in a brainstorming process, and then decide.
A concrete show case may look like the following one: a software engineer creates a new activity for deciding on a proposed design convention, adds some context information, and invites others to participate. He then assigns actions to the participants such as applying a SWOT analysis (Strength-Weaknesses-Opportunities-Threats), and deciding on whether to accept or reject the proposal.
According to Rita Sallam from Gartner Research,
Social and collaboration capabilities have the potential to improve the quality and transparency of decisions and drive positive outcomes if they can be married to a user's existing applications, information and business processes. Collaborative decision-making applications that are linking with existing business processes like performance management, CRM, forecasting, and procurement, bring the right people together and provide the tools they need to make better decisions. For example, BI users, such as sales managers evaluating sales performance across regions or products, or product managers deciding which new product ideas to fund, or finance managers allocating capital expenditures across strategic projects now have an efficient way to bring the right people together to analyze and discuss results and agree on a course of action - and capture the entire process - rather than the disconnected manual efforts of the past.
StreamWork is being provided as SaaS (Software as a Service) offering, with a free “Basic Edition” and a “Professional Edition” for 96 Euro per year. In addition, SAP offers an “Enterprise Edition” which may be integrated in existing SAP installations. SAP partners can also integrate their own applications into StreamWork. Examples currently include Box.net, Evernote, and Scribd.
An advertisement video on YouTube is supposed to introduce the basic motivation behind using StreamWork. Other videos such as a slide presentation are also available.
More details are available on SAP’s StreamWork web site.
Continuous Delivery: Anatomy of a Deployment Pipeline
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
How ALM Supports Business Processes
Branching & Merging Efficiently: A Guide to Using Process-Based Promotional Patterns
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply