Use a corporate library or not?

Question

I work with a multi-level SOA-based enterprise application with all the complex business logic. Many business checks require large amounts of database support data, which slows down performance. The number of concurrent users is about 1000. The client is multi-level with WinForms on top.

We consider almost all blocks of the corporate library.

• Caching Application Block
• Data Access Application Block
• Exception Handling Application Block
• Protocol Logging Unit
• Injection Application Block
• Security Application Block
• Unity Application Block

• Validation Application Block

  • Is the corporate library right?
  • Please suggest libraries / frameworks that are better in your opinion, but consider how they are better.
  • Would it be bad practice to mix a corporate library with other libraries? For example, we are considering using log4net for logging.

Answer 1

In my opinion, there are more effective tools for most of everything that a corporate library does.

• Data access unit

  , , EntLib , , , , . ORM, NHibernate Entity Framework, , SubSonic, . , , NHibernate, , " " NHib.

• ORM , .

• , . Rinat Abdullin .

• NLog log4net. . , Simple Facging Facade Common.Logging. - . . .

• DI/IoC . . , .

• EntLib, . , (Rhino Security) Validation (xVal, Lokad)

Answer 2

( ) .

, , - ( ).

, - , , .