Speed is what RUAL stands for.
Rual blocks are the ultimate independent elements that software architecture has been trying to identify in order to fight legacy problems. Other options like microservices, service-oriented architecture and reusable components still require your engineering team to spend time on updating these software parts.
The powerful Rual technology makes it possible to combine independent apps in one cluster. Each app can have it's own domain name, it's own databases and API's. Upload multiple HTML/CSS templates and choose per page which one you want to use.
Scopes can be set on every level, from users to pages to columns in a table or button visibility. This way you can efficiently organize user access for each separate application in your cluster.
Pricing depends on actual hosting capacity, number of active users, and concurrent queue jobs.
- Audience overview
- Website error rate
- Queue activity
- Users active in blueprints
Further details can be found in the Cluster Management menu. One of the menu items covers the recent API history, including the source/response messages for every exchange.
For every cluster you can also set preferences and other variables that are accessible throughout the system. For example if you have a token for a third party service, you can add this token to the system settings, choose a name for it, and use it in your blueprints by getting the reference to this token. This way you can change important settings at one place in your cluster. Another good example could be a VAT percentage that is valid for quite some time but can be changed in the future.
RUAL. Development technology.
RUAL. Performance driven.
RUAL. Let's code together.
A simple "get document" command retrieves the data in tenths of milliseconds anytime and anywhere you need it.
Your data is stored in ElasticSearch, known for its unparalleled search performance. The Redis cache keeps all hot-documents handy, ensuring even faster operation.
The JSON flexibility allows for easy, anytime addition of fields to a storage. Its an excellent combination with the ElasticSearch query facilities.
The simple JSON format makes it easy to read for humans. With the right scope, users can see the JSON document in the frontend by using the right mouse button on a line in a datatable, a quick "zoom in" on the record.
To test your changes you can use simulation and staging facilities that enable live debugging your pre-saved software on production data.
RUAL. Development technology.
RUAL. Performance driven.
RUAL. Let's code together.
For example if you include an import option in your application, you can use the execute function in queue block to automatically split the execution in batches. The platform will process the batches for you, no need to write queue management yourself.
Queue management also handles scheduled tasks for you. These actions are set using the repeating event blocks. This way you can schedule actions, or just check for updates, yearly, monthly, daily or even every minute.
In Rual you can set a revision history, ranging from 1 day to 8 years for any storage.
Revisions are visible in the frontend datatables for authorized users. Click on an item in the list to see who made the changes and what mutations were made.
Automated document expiry can be added when a document is created or updated. By selecting immediate expiry on removal and documents will be cleared entirely from your databases, thus complying with GDPR regulations.
The staging mode is used in the frontend to test alterations in the program or to preview styling before deploying your new software.
Simulations can be run to test the backend, calculating data at every pin that is used, which can be checked and altered while the simulation is running. Additionally debug screens or console logs can be placed at any point in the programming flow to stop or check results. Simulations show the effect of changes pre-saved, running right there in production, before deploying.
This tutorial shows how it works: Simulate functions
For the second step the user can select from:
- receive SMS code
- security card or key
- authentication app
The same functionality is available for your own applications. You can change the HTML templates for login, password reset and security to match your own look and feel.
OAuth 2.0 creates a Single Sign On (SSO) experience for your user. In your own cluster you can add the applications that you want to use for OAuth, with optional OAuth scopes. We currently offer connections for login with Microsoft, Apple, Google, GitHub and Slack.
Setting up a REST API is basically a matter of defining an endpoint, and a flow that handles the connection, and you are ready to share. Check our tutorial: Create an API
Rual also provides blocks for setting up a SOAP connection and has built-in functionality for using webhooks.
At any moment in your program flow you can dynamically generate PDF files which can be downloaded, saved in your storage or sent by mail. Or any combination of these.
In our tutorials section you can see how to create a PDF and other file types: Generate files
- GitHub, share issues, pull-requests and reviews
- Discord, Slack, post messages, bots
- MSSQL queries, apply extensive queries without rewriting
- Electron, save web applications as desktop apps
- Google Maps, GeoPoints, directions and places
- Postmark, email
- Messagebird, sms and Twilio, whatsapp / phone
- Mollie payment provider
- SEPA and MT940, banking standards
- Twinfield, bookkeeping
- domotica: Philips, Honeywell and car kits
- Text to speech, voice controlled order picking
- Floriday API, Floramondo VMP, Dutch flower auction
- Edifact, import & export logistics message standard
For the applications you built, you can add unlimited translations in the backend or in the frontend. In the platform settings you can choose which languages you need. There is no limit on the number of languages. Every text that is visible for the user can be translated. Translations can be single words, or entire paragraphs including simple HTML mark-up. This whole paragraph for example, is a translation of one single key.
Translations are not only used to read the frontend, but also work for confirmation mails, PDF exports and for example command sets used in the pick-by-voice integration, which makes it easier to work with employees from different nationalities.
A big plus is that translating can be done by professionals right in the frontend, no coding needed.