Comparison of different approaches to creating a product / system

System Type Typical CMS Custom Development Finished product
sass services
Falcon Space Platform
Example system Wordpress, Joomla, Bitrix et al. PHP, ASP.NET frameworks Bitrix 24, Megaplan, AMO, etc. Typical Falcon Space Solution
Customization for yourself In general, this is a component setup, but you can write your own components with CMS restrictions You can change anything and anything. There are essentially no platform limitations. You can only change within the limits provided by the vendor. Often this is not enough to make a convenient solution for yourself You can do your layout, your business logic in SQL. There are limitations, but it does not concern business logic
Making quick changes Realtime Changes Only settings can be changed quickly. Business logic cannot be changed quickly due to the full development cycle You can only make changes within the settings Interface changes and business logic in realtime
Ready Integrations Large catalog of plugins The decision is made for the project and each integration is the work of the programmer A fairly large number of integrations with all kinds of systems There is a certain basic set of solutions that covers the basic basic needs of users of such programs. But there are no possible integrations when compared with standard CMS
Public Content Management Lots of special content plugins In general, the default content management capabilities are very meager, and all the required features must be done and implemented for the project. If this is required in the system, then usually these tools are implemented at a good level with many features (but still they are not as wide as those of typical CMS). By default, there is control over all the basic features for working with content. If necessary, you can implement and implement additional features
Ability to change business logic Most systems in general are not geared towards working with business logic Business logic can be changed as desired in a custom development project Usually there is a certain interface with settings and the possibilities of customization are limited on this This is the main advantage of the system - any business logic is written in SQL and changes through the office directly on the site
Speed ??of creating new functionality Basically, it’s setting up ready-made components, not development The full development stack assumes a TK cycle - design - coding (backend, frontend, layout) - testing - implementation on PROD In general, it is problematic to create new functionality The new functionality is a pinch of markup in the form of snippets and the implementation of typical SQL procedures.
No development bugs Bugs are mainly found not in the CMS core, but in installed plugins There are a lot of bugs since it's development from scratch Not relevant since few development possibilities Bugs occur in the main only in 1 layer - in SQL. Therefore, they are smaller and easier to debug when compared with custom development
Upgradeability The kernel is updated, but crashes are possible The decision is made for the project and generally does not provide for regular updating of the platform. If there will be an update of the whole framework, then it is done manually The update is performed by the vendor. The absence of customization simplifies this process Both the kernel and the SQL code of individual cabinets can be updated.
Security Many attacks target typical CMS High probability of introducing security and optimization problems with an inexperienced team The code is tested by the vendor and there is a high probability of quick error detection due to the large number of service users The main problem is the human factor. The platform contains all the tools for role-based access control and blocking of unauthorized access
Cost of Ownership There are free CMS + if you don’t need a lot of changes, then you don’t need much money to support It’s very expensive to change and develop. The need to keep a whole staff of specialists in various fields In general, use is free or there is some fee per month. But at the same time, the fee is constant + usually there is a limit on the number of users (for each workplace you will need to pay extra). For support and development you need to know only sql and layout. However, for the development of the system, in any case, a technical specialist is required. There are no restrictions on the number of users and time of use.
Quick Start Installation and configuration can be done in 1 day The full development cycle implies a long process of delivering the initial result Registration and initial setup in your account are required. No installation required. Requires installation of the box and installation of the necessary turnkey solution. If a change in business logic is required, then this delays the process (but it is important that this change is possible)
When to choose You need a content site, you have a typical online store. You do not plan active customization of the project You have a unique project with special requirements for performance, security, design and integration There is a ready-made product that covers all your needs. However, you do not need to develop it in the future. A project with an emphasis on user accounts and functionality for them. The project will gradually develop and change as new tasks and needs arise
When definitely not suitable For projects with unique functionality and changing business logic of the project For blogs, simple stores, and other sample projects You have atypical processes, in the future you plan to develop a system for yourself For content sites, for promo sites and landing pages
Major Cons It’s difficult to change the existing business logic and the complexity of customizing finished components. Long, expensive, many errors, delays in changes, problems with developers. Project Infrastructure Support Complexity It’s difficult to fully adapt for yourself. Dependence on external service. There are few ready-made integrations with external services (but there is a universal API). No third party ecosystem of components written (for Wordpress or Bitrix)
Main Pros Many ready-made components and integrations. A large market for developers on typical CMS You can do almost anything and in any form, optimize performance for the project You can get started very quickly if there is a suitable solution. You do not need to know programming for maintenance. Ability to change and develop business logic through SQL. Fast cycle of changes to a working system. Performance (due to direct SQL execution). The database structure was made for the project (not universal, which is good for the speed and development of the project). A set of ready-made solutions. For the development of the system you need to know only SQL and Bootstrap.