Would you design an application differently based on the device it will be viewed on or would design a mobile application the same as a web application regardless ?
An example I have in mind would involve reports and the type of reports that would be available based on a device.
Figure 6.6 in Chapter 6 on SOA and modularity illustrates this perfectly. Use modularity to maintain the internal integrity of your services just as you'd use modularity to maintain the internal integrity of a monolithic application. But the day of the monolithic application where client and server-side presentation, domain objects, and data access objects are all bundled together into a single application is quickly coming to an end. It's not a sustainable development model in a multi-channel world. Unfortunately, Chapter 6 isn't available for download. So for the first time this week, I'll tell you ... Buy the Book. Or win a copy.:-) The first six chapters lay this out for you. The rest of the book (i.e., the patterns) help you do it.
Visit the book's website at modularity.kirkk.com where you can review all 18 patterns and download an excerpt of the book. There is also a mobile web application available that you can take with you wherever you go.
Joined: May 13, 2009
I was just starting look at the patterns on your web site.
One thing I think about my own applications is coordinating the relationship between objects and object reuse.
Applying this to services is a similar situation.
You want the service to be modular but to be useful, it has to be able to interact with other services.
The situation I mentioned about reports and devices is something I'm looking at now.
I have module that provides a report that provides many rows and columns that works on big screen but on a phone screen would be cumbersome.
So I am think of providing different/extra methods methods for reporting . Ie adding a method that only displays one record at a time that would work on a phone as well as a pc browser.