kiloton

Version, currently master branch1 version
  • master branchlatestSep 10, 2019

github.com/jeremycw/kiloton

No description declared in shard.yml.

0 stars
0 dependents
License: MIT

Installation

# Add this to your shard.yml
dependencies:
  kiloton:
    github: jeremycw/kiloton
    branch: master

master is a branch, not a release, so this tracks it rather than pinning a version.

Then run:

shards install

shard.yml

Crystal
no constraint declared
License
MIT

Dependencies

Runtime Dependencies

  • mysql~> 0.5.1github: crystal-lang/crystal-mysql
  • redis~> 2.1.1github: stefanwille/crystal-redis
  • cannon~> 0.2.1github: Papierkorb/cannon
  • schedule~> 0.2.1github: hugoabonizio/schedule.cr
  • query-builder~> 1.1.0github: izniburak/query-builder
  • baked_file_system0.9.8github: schovi/baked_file_system

README

Kiloton

Kiloton is a web framework for Crystal that is loosley inspired by Ruby on Rails. It does not aspire to be as featureful as Rails but intends to provide a more comprehensive out of the box experience for the core components of a web app.

For me this means:

  • Compiles to a single static binary for easy deployment
  • No need to be running auxilliary services. Infrastructure you need is builtin.
    • No need to run sidekiq or equivalent, scalable job running is builtin.
    • No need to run seperate websocket server because the builtin one will Just Work at scale.
  • Seamless horizontal scaling with no need to worry about primary/secondary semantics
    • Cron/Scheduled jobs will be scheduled by one server but executed by many
  • Production ready by default
    • Automatically scales vertically on a single machine to the amount of cores available
    • All default behaviour will be scalable. No toy/cute behaviour that needs to changed later.
  • First class async workflows
    • Sometimes a business process is more complicated than a single endpoint
    • These highlevel flows should be first class instead of adhoc