Ryax versus other similar tools¶
Thank to its flexibility, Ryax can solve many different problems. You may use it to handle a single, simple use case but you may also leverage it to process the entirety of a company’s backends.
Thus, several tools on the market can seemingly overlap with the capabilities of our product. In order to better understand what Ryax does, let us compare it to a number of these tools.
Home made tools¶
Lots of companies develop their own tool internally, when they start to develop backend software. It usually starts with a simple script and then evolves into a larger solution. These hand-made approaches are error-prone and become hard to maintain when the needs in automation grow. In fact, going into production requires much more than a simple script: a data science workflow has to be developed, monitored, debugged, and updated.
Ryax is doing exactly this. It allows you to focus on your projects while taking care of the whole life-cycle of your pipeline.
Airflow is an open-source platform that can trigger code at some given time window. It is sometimes referred to as the “Cron 2.0”. Airflow is different from Ryax on 3 main aspects:
Airflow’s workflows are dynamic: a workflow step may produce some other steps during runtime, while Ryax workflows are defined beforehand and will not change their own definitions unexpectedly. Even if dynamically-defined workflows give more flexibility, they make it harder to debug and thus robust executions are rare, and achieving it requires to go through steep and time-consuming learning curves.
Airflow’s workflows can only be triggered at given interval times, while Ryax supports any kind of trigger: time based, manual, API endpoint, chat messages, emails, webhooks…
Airflow’s workflows are defined through code. In Ryax, you don’t need to learn some obscure language. We provide an intuitive user interface on which you can start to create right away.
Kubernetes, Mesos, Docker Swarm…
Kubernetes is a general purpose container orchestrator made for any workload that a Data Center might encounter. It attracts a lot of attention, has an army of contributors and is currently becoming an industry standard for running web application and services.
Ryax is a much more specific tool that focuses on backend software. In fact, Ryax is built on top of Kubernetes and leverages it to manage your workflows’ deployments. So, in a way, Ryax can be considered as a kind of orchestrator, but one that only focuses on running backend code.
Automation tools are designed to provide a simple way to automate interactions between separated tools. These event-based platforms have a lot of integrations with external services. Thus, they can trigger the execution of a pipeline from a lot of events.
While Ryax is also able to automate this kind of interactions it provides much more features dedicated to the creation of backends, like the ability to create APIs.
Putting a backend in production means automating the execution of your codes, but it also means packaging, building, distributing, connecting, orchestrating, and monitoring these codes. Ryax does all of that for you :-).