All geek questions in one place

Is the "reusable business component" a myth?

After reading the discussion How to create shared / reusable code with Scrum? I was thinking about my experiences with reusable components.

I created several "technical components" that were successfully used in other projects.

I also created several "business components" that were originally intended to be reused. But they were never used as one library, because the solutions for different clients were different. Of course, ideas and code fragments were reused from the business library, but not the library itself.

A large number of applications, such as SAP / R3, are used by many customers. In my opinion, this is a monolith, not an independent component.

So I asked myself: is the "reusable business component" a myth? If so, why is it so hard to create?

+3
source share
2 answers

I say that this is not a myth, but certainly a rarity in my experience.

It also depends on what you call the component, and at what grain level you look. Each user and business unit where I work uses Microsoft Office and Exchange, so they are very reusable.

-, , . . - , , .

, , , - /: : ? ?

" " , Identity and Access Management. ( ..), - ( IAM).

( ) , , , . , - ( ) -.

+1

Source: https://habr.com/ru/post/1779471/

More articles:


All Articles