Office2.0 applications become so ubiquitous, that I already use the term “standalone” for SaaS applications that run in a browser from a server, without any additional mashup or as a plugin within other applications…
A funny thing happened today when I quickly hammered an email to my colleagues about Wikis. Detecon is currently looking into options for a corporate-wide Wiki. There are several problems with this: we have some legacy software we have to use, we have existing SAP and Microsoft Sharepoint solutions we probably have to use by demand of our big mothership, and we have everything from process consulting with management dashboard requirements to software developers with coding, version control, and peer review requirements.
But that’s beside the point now: I wrote about my outstanding experience with TeamPage by Traction and the awesome plugins for Confluence by Atlassian. Here is what I wrote without really thinking about it:
[...] Within Confluence, I liked the gliffy plugin (there is standalone version available at www.gliffy.com), as well as the great spreadsheet plugin EditGrid (also standalone here: www.editgrid.com), [...]
Holy moly: SaaS as a “standalone” version?! No, not offline, standalone. This is quite funny. I am actually working with office2.0 / web2.0 applications on such a regular basis, that for me “standalone” now already means if it runs in a web browser from a server, without any additional mashup or as a plugin within another application.
I wonder when installing an .exe file or running a Windows Installer feels like patching a Linux kernel….
Berney Finucane is analyst of the Business Application Research Center (BARC). He is making a clear distinction between Software as a Service (SaaS) and web-based tools – which are not necessarily SaaS. He argues that with SaaS you could reduce server costs. But on the other hand this is an objective for general IT over
An excellent (German) article by BITKOM summarizes business challenges, decision points, and business models of cloud-based solutions. BITKOM segments the “Cloud” space into Software, Platforms, and Infrastructure. While this is all true and good for current business, the Cloud stack looks more like Information, Relationships, Services, Platforms, Infrastructure, and Networks.
Most amateur database programmers will answer you that any kind of application “basically only needs one big table”. Well, Twitter has proved them wrong. Just throwing more resources at a problem isn’t necessarily the best idea if your design is already flawed. That is also true for cloud-based testing, or even cloud-based testing of your
Content © Playout Intelligence
Proudly powered by WordPress
Theme designed by Artisan Themes