Author Archive for edward

18
May
10

ebizQ Forum: What Are the Biggest Downsides to Cloud Computing?

Delivered Innovation CTO Michael Topalovich recently provided his take on the ebizQ Forum question: What Are the Biggest Downsides to Cloud Computing?  From the Forum:

I’ll substitute “downsides” with “risks” because some of these may be viewed as half empty / half full arguments, but I see the biggest current risks as:

  1. Market confusion. As Peter mentioned, it is a mad dash to the cloud right now. And since nobody wants to feel left out, just about every company in the B2B tech space has re-branded itself as a cloud computing company. I’ve heard this referred to as “cloudwashing,” and the result is that companies will find it more difficult to find services specific to their needs, because of the tendency of providers to water down messaging into cloud buzzwords and ignore basic positioning and value statements.
  2. Cloud sprawl. With the rapid proliferation of cloud services, IT is struggling to adapt corporate service delivery strategies. The results that we have seen have included duplication and overlap of processes and functions due to services being provisioned directly by business units; loss of control of the billing for services because no single entity within the company is responsible for the procurement and management of them; and the equivalent of “shelfware,” a situation where cloud services are orphaned after the champion leaves the company or the business shifts focus.
  3. Lack of cohesive integration strategy. There is no doubt in my mind that the cloud model of service delivery is the one that we will adopt for at least the next 10-15 years of technology cycles, but until the integration of all of the pieces is thought through, the sum of the parts will never add up. My company has standardized our core service offerings around the Force.com platform from salesforce.com to provide the “glue” that holds all of the pieces together, and we “mash up” other cloud services into composite enterprise business systems through API integration, business process orchestration, and data integration using services such as Boomi. But if companies just provision cloud services for siloed requirements up and down the cloud stack (from infrastructure to SaaS), the disaggregation of these services will prove to be a value destroyer.
09
Apr
10

Book Preview: The Design of Design by Frederick P Brooks Jr.

Delivered Innovation has been given the opportunity to read a chapter excerpt and do an early review of Frederick P. Brooks, Jr.’s new book  The Design of Design: Essays From a Computer Scientist. Brooks is most renowned for his book The Mythical Man-Month. In The Design of Design, Brooks explores of the process of design, focusing equally on the creative and technical aspects of design as well as the bureaucratic, hierarchical, and political interactive. In other words, how can a design process best incorporate (and nurture) the artfulness of design while not compromising the real time needs of the project?
Chapter 6 is entitled “Collaboration in Design.” He begins with the observation:

Most great works have been made by one mind. The exceptions have been made by two minds. And two is indeed a magic number for collaborations; marriage was a brilliant invention and has a lot to be said for it, but notes that, while single or double-minded design works best as a result of the single-minded purpose of design, the practice of team design is absolutely necessary because of, the increasing sophistication of every aspect of engineering… I am impressed that there are no naive technologies left in modern practice.

Brooks explores the drawbacks of collaboration and the ways to take advantage of and manage collaboration, but the section that grabbed our attention most was his key to successful collaborative design – the System Architect.

[The Sytem Architect] must have a clear vision of and for the system and must really care about its conceptual integrity… Only the architect represents the users. And, for complex systems as well as for simple residences, it is the architect who must bring professional technology mastery to bear for the users’ overall, long-run interest. The role is
challenging.

Being in the business of cloud Architecture, we couldn’t agree more. We oversee different design teams and steer their output towards an outcome that MUST please the user, i.e. our client. The challenge is the mixture of expertise with the skills of management while meeting the needs of the client (and sometimes defining the vague or moving needs for the client). Brooks nails it on the head and his incorporation of dry humor into a clear layout of a complex subject appeals to us. We’re looking forward to the rest of the book.

Check out an excerpt from The Design of Design here: The Design of Design Chapter Excerpt (81)

05
Mar
10

PivotLink CEO Quentin Gallivan on SaaS Business Analytics and Cloud Computing

PivotLink

Edward Schlicksup of Delivered Innovation recently caught up with Quentin Gallivan, CEO of PivotLink, the leading provider of SaaS business intelligence solutions. PivotLink’s approach to business intelligence is a paradigm-shifting model within the BI industry. By combining advanced technologies like in-memory analytics, columnar data storage, cloud computing, a SaaS delivery model and unique methodologies, PivotLink helps organizations gain greater insight into the massive volumes of data increasingly at their disposal – in a highly secure manner.

Continue reading ‘PivotLink CEO Quentin Gallivan on SaaS Business Analytics and Cloud Computing’




Cloud computing application & service design by Delivered Innovation

Subscribe to Delivered Innovation with RSS  Follow Delivered Innovation on Twitter  Find Delivered Innovation on Facebook