Modern enterprise companies are increasingly adopting hybrid development models. This allows them to combine the speed of low-code platforms with the security and architectural control of custom software.
Risks of isolated low-code adoption
Completely abandoning traditional coding in favor of proprietary visual builders creates architectural risks. Over time, companies face limitations in implementing unique business logic, integration challenges, and the emergence of uncontrolled "shadow" IT systems. According to the Thoughtworks Technology Radar report, engineering discipline, including automated testing and code reviews, remains critical for any approach.
Market implications
The shift toward hybrid development models allows enterprise businesses to significantly accelerate software delivery without sacrificing security or architectural integrity. By combining low-code platforms with custom development, companies can eliminate the risks of "shadow" IT, improve DORA metrics such as lead time for changes, and maintain full control over their core business logic.
Hybrid architecture based on UnityBase
An effective solution is a hybrid architecture where the core business logic is built as custom code, while routine operations and interfaces are delegated to the platform. An example of such a tool is the Ukrainian low-code platform UnityBase. It functions as a full-stack JavaScript framework where the data structure, interface, and API are described by a single metadata model. The platform automatically generates a REST API and Admin UI, allowing developers to focus on complex server-side logic.
Development standards and quality control
Hybrid development must align with cloud engineering standards. According to The Twelve-Factor App methodology, code and configuration must be strictly separated. Storing configurations in a Git repository enables the use of standard CI/CD pipelines. Research by Google Cloud / DORA confirms that process automation improves deployment frequency and shortens lead time for changes.
Key focus areas of architectural audits
According to the AWS Well-Architected Framework, regular reviews help prevent system degradation. When auditing hybrid projects, special attention should be paid to the following aspects:
- API contracts: interaction between services must occur exclusively via REST APIs or message queues, avoiding direct database manipulations.
- Access control: using a unified authorization context and built-in access control mechanisms (RBAC, RLS).
- Performance: analyzing high-load performance on automatically generated ORM queries.
Operational aspects of hybrid solutions
Configuration in hybrid platforms is stored as declarative files, enabling full use of Git and code reviews. Platforms like UnityBase support on-premises deployment for projects with high security requirements. This approach improves DORA metrics, particularly lead time for changes, thanks to the automatic generation of basic system components.
A practical checklist
To successfully implement a hybrid development model, organizations should adopt the following practical steps:
- Combine custom code with low-code: Build core business logic as custom code while delegating routine operations and interfaces to platforms like UnityBase.
- Enforce engineering standards: Align development with cloud standards, such as The Twelve-Factor App methodology, by separating code from configuration and using Git-based CI/CD pipelines.
- Conduct regular architectural audits: Focus on securing API contracts, implementing robust access control (RBAC, RLS), and monitoring ORM query performance under high loads.
Prepared by a Software Ukraine member. Original publication.