tjsavage511 | 2 years ago | on: Show HN: Retool Portals and Retool Embed
tjsavage511's comments
tjsavage511 | 3 years ago | on: Retool Database
No custom extensions - we wanted to make it a lightweight and effective layer on top of Postgres. So it’s just a vanilla Postgres database under the hood. The UI gives you access to a lot of the power of Postgres, and for anything that you can’t do via the UI you can use the connection string directly: e.g. create triggers, create compound unique keys, etc.
tjsavage511 | 9 years ago | on: Ask HN: Anybody using web components (or Polymer) in production?
tjsavage511 | 10 years ago | on: Show HN: A Highcharts Library for Polymer 1.0
- Retool is datastore/backend-agnostic, so from a backend/data perspective it will be as scalable as whatever backend you’re using to process/store those orders. You can connect Retool to make requests to your own API, to directly query a database, etc.
- From a frontend perspective, you can choose to deploy Retool using Retool’s Cloud, or self-host Retool on your own private cloud. The former is quite scalable, but if you wanted full control over scalability you’d likely opt to self-host. If you’re self-hosting you have all of the “typical” scaling techniques available to you: you can e.g. run Retool on Kubernetes, and vertically or horizontally scale however you need.
For more on scaling self-hosted deployments, see: https://docs.retool.com/docs/horizontally-scaling-retool