Plug in exactly what you need
As a modular, pluggable system, Redakt makes sure you only have the features you need. This improves speed and responsiveness (and makes maintenance way easier) and gives you the opportunity to build your own custom components.
This minimalist philosophy allows the user interface to be simple, focused, and targeted at getting undistracted results. Increase or decrease the number of features that you want to use with our simple CMS construction. It can get as complicated or simple as you would like it to be.
This means Redakt is infinitely expandable but very simple. You can strip back to the functional minimum, then add functionality to cater to their needs.
Redakt has several different modules that can be used, accessed by simply installing and configuring the appropriate package. Every module includes a set of interfaces that can be selected as needed or, if you can't find what you're looking for, you can build it yourself.
Dependency trees are also optimized through this approach, giving you peace of mind and avoiding messy issues as you expand and change. Combined with cross-platform hosting, this makes Redakt one of the most flexible and deceptively easy CMS options for businesses of all sizes.
What does pluggable architecture look like?
Pluggable modular architecture allows you to add or remove any technical module to the existing CMS. You can add data stores, service buses, file storage libraries, application caches and more. Not every site will need to add in every possible feature of the CMS so this is fully customisable and dependent on your needs.
The core Redakt system does not include a data store implementation by default. Instead, you can plug-in the data store of your choice, allowing the flexibility to install the CMS in many different situations. Redakt supports a number of data stores out of the box including MongoDB and RavenDB, fast document databases that are run on-premises or hosted, Azure CosmosDB and Amazon DynamoDB for storing data in the cloud, and LiteDB, a local file database for smaller projects.
In a load-balanced environment, Redakt CMS communicates with service instances through a service bus. This can be done through a specialized collection in a MongoDB database, in the cloud with Azure Service Bus, or with Amazon SNS/SQS. A service bus is not required for single service instance environments where all communication is direct. The service bus is only used as it allows you to group operations against multiple messaging entities within the scope of a single transaction.
File storage options
All your images, documents and other large files are saved and retrieved by a storage module. Redakt can keep everything locally, in a network share, with the data in a MongoDB or RavenDB database, or even in the cloud with Azure Blob Storage or Amazon S3.
Redakt makes heavy use of application caching. This speeds up your response times and helps to prevent expensive round trips to the data store for objects that are retrieved often. Objects can be cached in local server memory, in a Redis cache, or a Memcached service.
Optional feature components
You may not need everything that Redakt has to offer, so you can pick and choose the things you want. This improves performance and keeps your project clean and easy to maintain. Optional feature components include the Redakt back office, full-text search, and global dictionary.
We imagine most of our clients will want to use the Redakt back office in their projects, but we make it optional. This allows you to keep your back office behind a firewall, where only your employees can reach it, to improve security and performance.
Alternatively, you could use a separate headless application to script tasks based on automation. Redakt can take care of all the communication between your separate services due to its built-in support for distributed hosting. No matter how complicated the process is, Redakt can handle it.