Skip to content
Pierre T. edited this page Jan 9, 2015 · 5 revisions

For IT organizations of a certain size, the concept of corporate stack appears as a standard response to a wish for exhaustive development guidances. Indeed, the enterprise stack is seen as the only solution for the organization to meet all of its IT development needs, whether internal or external.

For this, an enterprise stack is seen as the set of Frameworks managed by the organization that help provide well-defined solutions to all problems of software development organization.

Ideally, all these Frameworks comply same model / programming paradigm to ensure consistency in the development teams. For this, the Frameworks of the enterprise stack are based on common libraries that provide behavior, good practices and shared conventions.

This imply to consider new concepts and new roles:

  • New roles:
  • Stack developer: Architect / Designer designing and creating Frameworks. Often with a higher technical level and greater experience than business developers.
  • Business Developer: "classic" Developers designing and creating business applications using the frameworks of the enterprise stack.
  • New concerns:
  • Nuun delegate behavior to Frameworks to using it,
  • But its interfaces should not be exposed by enterprise stack, neither API nor SPI.
  • It must use high-level mechanisms to delegate properly the behavior and configuration to stack developers.

Content

Clone this wiki locally