Retter.io (Rio) is an abstraction on top of cloud infrastructure. Basically instead of writing apps directly running on AWS, you write apps running on Rio which runs on AWS.
We like to call Rio as cloud operating system that manages the resources of cloud computer (AWS). Instead of writing an application that directly accesses the intel chip, it is preferable to have an operating system such as Windows, Macoss or Linux. Writing an application on top of Windows is much faster and easier compared to directly using the underlying hardware. Additionally, there are many high level components you might use such as UI components. The ease of use of an operating system is aimed to give to developers with the Rio.
There are some apps such as realtime gaming that you cannot use Rio. These may require very low level networking components etc. For instance, if you like to write an Internet scale cloud app for retail, Rio gives you speed and ease of use.
We created Rio for our internal use in Retter while writing custom software for our clients. Now, we can use Rio to deliver cloud software up to 10x faster than directly using AWS.
Projects are simply applications running on your Rio operating system.
Classes are basic building blocks in Rio.
Rio has SDKs for iOS, Android and Web platforms.
Rio CLI is a nodejs program to help you create projects and deploy them.
Rio is running completely serverlessly on AWS. We use Lambda, DynamoDB, S3, Kinesis, SNS, Event Bridge etc in the background. However anyone using Rio doesn't have to have any experience on these services. Rio handles everything seamlessly.
Serverless + NoSQL databases gave us a development pattern which we think is object oriented. A set of lambda functions are running and reading and writing to a partition in a NoSQL db. We have created Rio to handle this scenario, so the developer doesn't have to. Rio takes care of following three things:
- Object state handling
- Single concurrency execution for each object instance
- Realtime streaming of instance state updates to connected clients
We are yet to publish best practice documents. You can follow us on twitter.