To extend on an earlier blog posts by a colleague here at M&S, I’m a firm believer in using different technologies in different situations. Trying to make a technology ‘work’ when another is clearly a better choice is very often a critical mistake. Reasons why these decisions get made are numerous (familiarity with a technology, existing infrastructure, etc). With that said, my own take on ADF vs. other Java web frameworks (such as Grails) is actual a lot more black & white than I thought it would be.
At this point, I asked myself, when would I use ADF vs. another conventional Java web framework? Here are the characteristics that I’ve come up with that best suit ADF or another Java web framework. What are your thoughts?
ADF Typical Project Characteristics
- Internal / Intranet
- Proprietary components ok (ADF Faces, ADF BC)
- Style unimportant
- Large datasets
- Rapid development critical
- Abstraction from underpinnings ok
Other Conventional Web Framework Project Characteristics
- Startups / Consumer Web Apps
- Style Important / particular UI requirements
- Bulk UI changes probable
- Open Source required
- Dev team familiar with technology at a low level