Posted by Phil Murphy on December 16, 2010
What is the definition of an "application"? We are "applications development and delivery professionals" - surely we have this question nailed, don't we? The question keeps coming up in different contexts, and since there are many potential opinions, a blog is the perfect place to spur debate. Here are some (simplistic) questions to generate debate:
- Is a Web page an application?
- If not, how many Web pages does it take until I consider it an application - 10, 100, 1,000?
- Does size matter? (Please behave yourselves with this one.)
- Is the size of the code base a pertinent factor?
- What about SharePoint sites, Access databases, and spreadsheets? Are they applications?
- Where do COTS and packaged apps fit?
- Does the technology I use affect the definition?
- If I use a scripting language for a quick-and-dirty task, is that an application?
- Does SOA erode the definition of an application?
- Do we cease thinking about applications as entities and think about them more as containers that hold collections of SOA services?
- How does open source affect the definition?
- How does my role affect my perception of an application?
- Do developers and users use similar definitions?
I have my opinions - in fact I just finished a draft piece of research on it that will be published in January, but what are your opinions?
- Anjali Yakkundi (21)
- Boris Evelson (129)
- Claire Schooley (2)
- Clay Richardson (1)
- David Aponovich (21)
- Diego Lo Giudice (12)
- George Lawrie (14)
- Holger Kisker (37)
- James Staten (6)
- Jeffrey Hammond (26)
- John R. Rymer (45)
- Jost Hoppermann (30)
- Kate Leggett (105)
- Kurt Bittner (3)
- Kyle McNabb (12)
- Manish Bahl (2)
- Margo Visitacion (9)
- Mark Grannan (5)
- Martha Bennett (8)
- Michael Barnes (20)
- Michael Facemire (13)
- Mike Gualtieri (110)
- Noel Yuhanna (10)
- Paul Hamerman (2)
- Phil Murphy (22)
- Randy Heffner (14)
- Stephen Powers (20)