Data is a necessary piece of nearly every software solution (I'm sure we can all think of exceptions, but there is data there too). Web 2.0 via mashups makes data integration from various sources relatively easy. Applying the MVC pattern to Web 2.0 we have view and control provided by Flex, AJAX / JavaScript / wikis / feed readers / browser, etc. and the model JSON or just raw data in syndication format. The formal nuances of data, its structure and relations, etc. are not the focus of mashups but rather pulling out relevant information fragments from various sources into a new whole (aggregation, composition, integration, etc.) creates a new information model, that requires new controllers and new views (unless you can reuse those from elsewhere too, but by and large you are pulling in data, aggregating and defining a new format, contollers and views. That's it. So why do IT departments seem to make it soooooo difficult? Job security and FUD.
Web 2.0 is, and provides, RAD (Rapid Application Development) for the Web. (RAD came out of the client server era, and in many IT shops today the term or concept are never used due to negative connotations and associations of an historic nature). RAD was cool and good back in the day as it empowered less skilled application developers to be more productive...today Web 2.0 technologies allow both developers and non-developers to create powerful, compelling softwware solutions with minimal effort. Minimal effort means a faster time to market as well as lower entry costs, redo, scrap, do over, change all become more cost effective and viable (and faster too).
To see how effective web 2.0 can be for you here are few cool tools that I find valuable. Note, I am not affiliated with these companies, developers or communities in any formal business or even friendship manner; I simply like what they have to offer and I think you will too:
First, for any IT people reading this, you should go have a look at ActiveGrid. I blogged about AG before, and will do so again in the future. If I was in charge of a small IT shop (or a team in a large IT organization) that needed to provided higher value, reduced costs and enable greater agility, this is where I would start. I'd build and deploy new apps on AG, retool my IT employees and start a migration plan for existing applications. I'd also start with the open source version until I was nearly ready to go to production and would give careful consideration to a commercial license based on the information available to me. ActiveGrid would be a foundational technology platform upon which I would rebuild my IT infrastructure. Period, end of story.
These other products and technologies could be leveraged by IT too, but are more focused on business people that need to get business done rather than IT who are in the business of supporting business, i.e., they are more usable for non-IT business users.
RSSBus. Just go and have a look, they do a great job of splainin' (explaining) what they do. Basically, you take data from all kinds of sources, aggregate it and create new scripts to act on it, and you can do this recursivley; building up your own catalog of feeds and scripts and using those provided by others. Of course, you are encouraged to submit yours for use by others. Great way to pull all the data you need in one place with a very easy toolset. Kudos to the RSSBus team! I will have more to say about this technology in the future too.
You can combine RSSBus and ActiveGrid in many complimentary ways.
Another technology I wanted to mention is OpenKapow. They claim "mashups in minutes" and its very accurate and true.
There are also Yahoo Pipes and Google Gadgets.
There are some overlaps in these and complimentary combinations too. Please let me know if you are using any of these and where, or if you are using other Web 2.0 tools, I'd like to learn about what else is out there. These are the tools that I would look to use if I was in charge of IT direction at any company. I'm sure there are many others...what they all have in common is simplicity and utilization of core technologies available to everyone on the Web.
Now have a look at what some IT industry heavyweights are proposing for business application development: big, complex, costly and heavyweight solutions that are so last century. I noticed that many of the products of these large vendors are consistent with their own size and complexity, the bigger the vendor the more complex their solution strategy it seems. There is an easier, faster and cheaper way to provide technology solutions to business, its Web 2.0. So easy its almost magic ;)
Thanks for reading
Showing posts with label ActiveGrid. Show all posts
Showing posts with label ActiveGrid. Show all posts
11 May 2007
05 December 2006
Web 2.0: The new RAD
Web 2.0 is a great concept. If you take what I consider to be the seminal, definitive and diffinitive definition of Web 2.0, a key aspect is the coupling of data and processing logic...an extension of object-oriented concept of encapsulated state and behavior.
Other interesting aspects of Web 2.0 are also similar to aspects of the RAD trend in the 1990's Client/Server era. Many of the Web 2.0 vendors are enabling a web version of RAD - a RAD for Web Applications (RAD4WA) or Rapid Web Application Development.
Even though they dropped support of the Mac version of their tool :( , when it comes to Web 2.0 application development I like ActiveGrid. One of the first things you'll notice about AG is that nearly every artifact is represented by some open standard; the rest are open scripting language artifacts or represented by an XSD. Developing a Web application integrating web services and databases is simple. straightforward and quick.
Another brilliant move by AG is their server model. I can only imagine the discusion that lead to their server design: we don't want a cluster model, we want a grid of low-cost, commodity processing nodes (LAMP stack servers) that will provide enterprise scalability, fault-tolerance, etc. The big vendors are spending huge amounts of money to develop grid / utility computing, what will we do? What does nearly everyone have, or at least have access too? Apache Web Server. We'll write a grid module for Apache. Absolutely brilliant: simple and elegant.
Finally, AG lets you use any/all of a myriad of scripting languages and/or plug-in your own. If you are interested in Web 2.0 or developing Web 2.0 applications AG is worth a look.
Back to RAD...
RAD worked well. We were able to offload processing from expensive mainframes onto low-cost PCs and Unix boxes (where the databases lived). For the most part, the RAD solutions were primariliy data presentation and data entry with input validation (sounds familiar to what most commercial web sites provide, no)?
RAD tools and solutions had their issues and limitations too. They worked well for a certain class of applications where the business logic was not overly complex; they didn't have separation of concerns (e.g., MVC) which was invented and lived nearly exclusively in the Smalltalk world, as did much of the design patterns back then. As complexity rose and maintenance cycles accrued they became very brittle and difficult to maintain. Not to mention they were proprietary.
During part of the RAD era, I worked for a Smalltalk vendor named Digitalk, Inc. Unlike most of the RAD tools of the time, our's was based on Smalltalk. The RAD tool was called PARTS - an instance based RAD programming tool. That is, you build your Smalltalk classes as usual and used PARTS to create instances of any of the classes in your image and knit them together into an application. You could even combine instances into a component (called a Part), that you could save in Parts catalogues and reuse in other applications. Very simple and powerful. PARTS, though standalone too, was part of Digitalk's Visual Smalltalk Enterprise - IMHO the best enterprise C/S RAD toolkit available at the time. What Digitalk VSE was to C/S RAD, I see striking similarities to what AG is to Web 2.0.
It remains to be seen if the Web 2.0 application development vendors can provide more than Rapid Web Application Development and deployment tools. I think some can, are and will. I've picked my winner, what say you?
Web 2.0 is RAD for the Web. I hope it goes better this time around!
Disclaimer: I used to work for Digitalk, Inc. and I have a fond nostalgia for their products. I do not work for ActiveGrid nor do I have any business relationship with them. But if you are hiring or planning for an ActiveGrid project, please let me know. We should talk!
Other interesting aspects of Web 2.0 are also similar to aspects of the RAD trend in the 1990's Client/Server era. Many of the Web 2.0 vendors are enabling a web version of RAD - a RAD for Web Applications (RAD4WA) or Rapid Web Application Development.
Even though they dropped support of the Mac version of their tool :( , when it comes to Web 2.0 application development I like ActiveGrid. One of the first things you'll notice about AG is that nearly every artifact is represented by some open standard; the rest are open scripting language artifacts or represented by an XSD. Developing a Web application integrating web services and databases is simple. straightforward and quick.
Another brilliant move by AG is their server model. I can only imagine the discusion that lead to their server design: we don't want a cluster model, we want a grid of low-cost, commodity processing nodes (LAMP stack servers) that will provide enterprise scalability, fault-tolerance, etc. The big vendors are spending huge amounts of money to develop grid / utility computing, what will we do? What does nearly everyone have, or at least have access too? Apache Web Server. We'll write a grid module for Apache. Absolutely brilliant: simple and elegant.
Finally, AG lets you use any/all of a myriad of scripting languages and/or plug-in your own. If you are interested in Web 2.0 or developing Web 2.0 applications AG is worth a look.
Back to RAD...
RAD worked well. We were able to offload processing from expensive mainframes onto low-cost PCs and Unix boxes (where the databases lived). For the most part, the RAD solutions were primariliy data presentation and data entry with input validation (sounds familiar to what most commercial web sites provide, no)?
RAD tools and solutions had their issues and limitations too. They worked well for a certain class of applications where the business logic was not overly complex; they didn't have separation of concerns (e.g., MVC) which was invented and lived nearly exclusively in the Smalltalk world, as did much of the design patterns back then. As complexity rose and maintenance cycles accrued they became very brittle and difficult to maintain. Not to mention they were proprietary.
During part of the RAD era, I worked for a Smalltalk vendor named Digitalk, Inc. Unlike most of the RAD tools of the time, our's was based on Smalltalk. The RAD tool was called PARTS - an instance based RAD programming tool. That is, you build your Smalltalk classes as usual and used PARTS to create instances of any of the classes in your image and knit them together into an application. You could even combine instances into a component (called a Part), that you could save in Parts catalogues and reuse in other applications. Very simple and powerful. PARTS, though standalone too, was part of Digitalk's Visual Smalltalk Enterprise - IMHO the best enterprise C/S RAD toolkit available at the time. What Digitalk VSE was to C/S RAD, I see striking similarities to what AG is to Web 2.0.
It remains to be seen if the Web 2.0 application development vendors can provide more than Rapid Web Application Development and deployment tools. I think some can, are and will. I've picked my winner, what say you?
Web 2.0 is RAD for the Web. I hope it goes better this time around!
Disclaimer: I used to work for Digitalk, Inc. and I have a fond nostalgia for their products. I do not work for ActiveGrid nor do I have any business relationship with them. But if you are hiring or planning for an ActiveGrid project, please let me know. We should talk!
Subscribe to:
Posts (Atom)