Factors for choosing a CMS type for a corporate customer
The question of which items the corporate customer comes from when choosing a CMS. The choice is not specific, but the choice of type - frivarnaya CMS, box or self-written “studio development”.
The advantages of the popular “box” (in our realities this is Bitrix, or, with some stretch of Yumi, in the extreme case Netkat) are clear:
- a lot of projects of different scale, implemented on this system
- a solid amount of ready-made functionality covering at least 90% of mainstream requirements
- documented
- the ability, using api, to add the necessary functions
- at least declared security concerns, or even an external security audit
- the presence on the market of a large number of specialists in this system
- availability of certified partner companies engaged in development for this system
- service of those. producer support
- the presence of the manufacturer, which paid the money, and which should answer for their promises
')
Minuses…
- price
- clearly defined system logic, which is often difficult to change
- for many systems - code closure
Advantages of a free system (according to my experience, first of all, I am talking about Drupal, plus maybe Mamba / Yumla ...)
- price!
- again, a huge number of implemented projects of various sizes
- the presence of a huge number of modules
- crowds of freelancers who know the system
- active community
The disadvantages of the free system include exactly what are the advantages of the boxes:
- there are often gaps in functionality where it is most interesting for corporate clients - integration with internal corporate systems, ensuring integration with internal authentication systems, etc.
- untested code most of the free modules available, the authors of which do not bear any responsibility
- lack of official service of those. support that has appropriate responsibilities and is required to keep the user
- the almost complete lack of studios, or at least the lack of competition between them (say, companies that are official Bitrix certified partners - dozens, there is no such thing with Drupal)
- free of charge (absurd ... but if no one was paid for the money system, then no one guarantees its stability, security, etc.)
- in most cases - the absence of an external security audit.
Studio solutions (the choice of the system is almost always unique to the choice of studio, the studio is responsible for the final product as a whole)
- availability of a list of projects, usually the scale of the implemented solution made for corporate customers by a specific development team
- the ability to create / rewrite for your needs almost anyone, albeit for frequent and for a lot of money
- the presence of a specific company responsible for its product and providing the appropriate guarantees
Minuses…
- there is almost certainly no external security audit.
- a solid part of the functionality will be written exactly for the client, with the corresponding cost and development time, plus the customer will act as a beta tester
- absence of specialists on the market who already know this system, i.e. in fact, dependence on a specific manufacturer (important for any solution that surpasses in complexity just a business card site)
What did I miss / distort?
The advantages of the popular “box” (in our realities this is Bitrix, or, with some stretch of Yumi, in the extreme case Netkat) are clear:
- a lot of projects of different scale, implemented on this system
- a solid amount of ready-made functionality covering at least 90% of mainstream requirements
- documented
- the ability, using api, to add the necessary functions
- at least declared security concerns, or even an external security audit
- the presence on the market of a large number of specialists in this system
- availability of certified partner companies engaged in development for this system
- service of those. producer support
- the presence of the manufacturer, which paid the money, and which should answer for their promises
')
Minuses…
- price
- clearly defined system logic, which is often difficult to change
- for many systems - code closure
Advantages of a free system (according to my experience, first of all, I am talking about Drupal, plus maybe Mamba / Yumla ...)
- price!
- again, a huge number of implemented projects of various sizes
- the presence of a huge number of modules
- crowds of freelancers who know the system
- active community
The disadvantages of the free system include exactly what are the advantages of the boxes:
- there are often gaps in functionality where it is most interesting for corporate clients - integration with internal corporate systems, ensuring integration with internal authentication systems, etc.
- untested code most of the free modules available, the authors of which do not bear any responsibility
- lack of official service of those. support that has appropriate responsibilities and is required to keep the user
- the almost complete lack of studios, or at least the lack of competition between them (say, companies that are official Bitrix certified partners - dozens, there is no such thing with Drupal)
- free of charge (absurd ... but if no one was paid for the money system, then no one guarantees its stability, security, etc.)
- in most cases - the absence of an external security audit.
Studio solutions (the choice of the system is almost always unique to the choice of studio, the studio is responsible for the final product as a whole)
- availability of a list of projects, usually the scale of the implemented solution made for corporate customers by a specific development team
- the ability to create / rewrite for your needs almost anyone, albeit for frequent and for a lot of money
- the presence of a specific company responsible for its product and providing the appropriate guarantees
Minuses…
- there is almost certainly no external security audit.
- a solid part of the functionality will be written exactly for the client, with the corresponding cost and development time, plus the customer will act as a beta tester
- absence of specialists on the market who already know this system, i.e. in fact, dependence on a specific manufacturer (important for any solution that surpasses in complexity just a business card site)
What did I miss / distort?
Source: https://habr.com/ru/post/11654/
All Articles