LinkedIn Twitter Facebook
Lean, Kanban, Agile Pairing, TDD (sometimes test after) software architect and programmer. Worked with distributed (called cloud sometimes) computing services since 2007 using phat data (8 billion rows of data on an AVERAGE day, sometimes called big data) and everything from business intelligence to the nitty gritty of array structures inside file based data stores to create caching tiers for custom software needs. Currently pushing for distributed technologies & improving software architecture, better data centers, the best software development practices and keeping everything secure in the financial industry again. To see what I'm up to today, check out my blog at Composite Code.

11 responses to “The Confusions of IaaS, PaaS, and SaaS”

  1. Xappworks

    The introduction of virtualization showed us that infrastructure abstraction provided significant benefit. This mirrors the evolution of highly evolved programming methods, which abstract from machine code to provide value. When coupled together, the benefits can be extreme – consider rapid software development with flexible and scalable deployment.

    This is what we are achieving at xappworks. Of course, the limit is market fragmentation. We have selected Java/Groovy as our niche. This is a calculated move – Java is mature language and Groovy adds additional abstractions and benefits. Other players focus on .NET for example. We believe that the benefits of bringing Java into the cloud is the ease at which client/server paradigm can be implemented – and the user experiences a desktop application which is completely familiar to them.

    The three basic descriptors of cloud are this: elasticity, self-service and service-based billing. We have decided not only to provide all three, but also a risk-free method of adoption – providing free access, in order to share the benefits of success. Perhaps this is a model for the future?