Development
Rierino Development Apps
Most development work in Rierino happens across four apps. Each app “owns” a slice of the platform, so you can iterate without mixing concerns.
Devops
Use Devops to build and operate backend execution. This is where you define and deploy runners (microservices), design sagas (API flows), configure gateway routing/security, and manage deployments.
Start here when you are building APIs, orchestrations, or anything that needs to run in production. See Devops Overview.
Configuration
Use Configuration to store “logic as data”. This is where you define reusable queries, business rules, and dynamic handlers, which can then be executed by runners and sagas at runtime.
Start here when you want behavior to be editable without redeploying services. See Configuration Overview.
Design (Admin UI)
Use Design to build the admin UI. This is where you define apps, UIs, listers/widgets, and the Source mappings that connect screens to backend APIs. You also manage UI resources like options, translations, icons, and styles.
Start here when you want a screen for listing and editing data or operating flows. See Design Overview.
Data Science
Use Data Science to configure ML and GenAI assets that can be invoked from real-time APIs or batch processes. This includes ML models, GenAI models, MCP servers, CEP flows, visualizations, and customizations.
Start here when your use case needs inference, agents, personalization, or stream processing. See Data Science Overview.
How they fit together (typical workflow)
Most teams iterate in a loop: define runtime services in Devops, keep reusable logic in Configuration, expose operations through Design screens, and add intelligence through Data Science assets when needed. The boundaries are intentional, but the components are designed to compose cleanly.
Initial Reading
To start using Rierino right away, use the training microservices shipped with the standard installation. They let you explore the platform without building anything from scratch.
Focus on the following concepts first:
Start using existing training microservices with saga flows.
Integrate with 3rd party rest systems and call their APIs.
If you prefer a guided path, complete the self-paced interactive training. It introduces the main concepts and terminology using hands-on steps.
Examples
Once you are comfortable with the basics, use the examples below to build confidence. They are also a good way to validate that your deployment is working end to end.
Reviewing Training APIs & creating an API endpoint
Reviewing Training Microservices & creating a CRUD service
Reviewing Training UI & creating a UI screen
Reviewing Training AI Agent
Building a complete To-do List App
Videos
You can also visit our YouTube channel for QuickBuild videos. These are useful when you want to see a full workflow, start to finish.
Troubleshooting
Rierino provides multiple ways to audit and troubleshoot issues. Start with these quick checks:
Checking meaning or Error Codes returned
Performing checks for common errors
Checking feature availability by versions in release notes
If you are stuck early, validate that:
Your gateway is reachable.
Your training microservices are deployed.
Your data store is accessible (MongoDB by default).
Last updated
