As far as I know, MVC is not a design pattern. It's more an architecture based on the Observer pattern. For example, in Swing, the GUI get updated automatically when its model changed. The GUI is an observer of its model.
If you want other modules are notified when your bacground processing module changed, make them as obervers of it. That's the Observer pattern. Java provide APIs to make things easier, please refer to Observable/Observer in Java API.
To be or not to be. It's a question.
Joined: May 11, 2005
Suppose If my application reads the data from the Message Queue and the data is validated by Business layer and stored in database using Data Layer. In this case No presentation Layer ot UI is involved.
What is the common pattern name we have? Please let me know.
How bad would it be if there was no pattern? If I didn't know one that helped me design the system, I'd happily go without for a while. Maybe one will emerge as you work.
I scanned Grady Booch's Pattern Catalog for anything with "message" in it. A Message Gateway encapsulates the message listener and treats is as one of many ways to trigger a Service Activator. Be careful not to stretch too far ... if these don't help you design or explain the system, don't misuse them.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Design Patterns work on a finer scale of granularity than you seem to be thinking. An application like the one you describe could easily make use of hands full of design patterns, to solve specific design problems.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
subject: Design Pattern - without Presentation layer