When designing distributed applications, developers typically create
components based on required functionality, or related services. Some
components will be entirely service oriented, but most will be standard
components with a mix of retrieves, updates, and some processing logic.
Typically, these components reside in many different packages. As your
enterprise grows, more and more components and packages are added, while
simultaneously maintaining existing components. The process can get quite
complex. One way to simplify this scenario is to reduce the number of
components on the server. Since probably 75% of all retrievals done in
applications are simple and don't require a lot of business logic, why create
multiple components? The answer? Don't.
Generic Component
I'll show you how to create a single component to handle most of your
retrievals and even do updates... (more)
When designing distributed applications, developers typically create
components based on required functionality, or related services. Some
components will be entirely service oriented, but most will be standard
components with a mix of retrieves, updates, and some processing logic.
Typically, these components reside in many different packages. As your
enterprise grows, more and more components and packages are added, while
simultaneously maintaining existing components. The process can get quite
complex. One way to simplify this scenario is to reduce the number of
components on ... (more)