{"__v":21,"_id":"57240befeae5090e00ee622f","category":{"project":"5723ead0fda3c70e005b88e5","version":"5723eaebeae5090e00ee61f1","_id":"572a28f6d10a200e00b1cb14","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-04T16:53:10.034Z","from_sync":false,"order":1,"slug":"concepts","title":"Concepts"},"parentDoc":null,"project":"5723ead0fda3c70e005b88e5","user":"5723ea8efda3c70e005b88e3","version":{"__v":3,"_id":"5723eaebeae5090e00ee61f1","project":"5723ead0fda3c70e005b88e5","createdAt":"2016-04-29T23:14:51.190Z","releaseDate":"2016-04-29T23:14:51.190Z","categories":["5723eaebeae5090e00ee61f2","5723f854110e570e00486c7a","572a28f6d10a200e00b1cb14"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"0.1.0","version":"0.1"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-04-30T01:35:43.517Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Lever OS is a **serverless** platform for **microservice**-oriented **backends**.\n\n... Whaterver that means!\n\nWell, allow me to explain.\n\n# Serverless\n\nLever OS allows you to deploy your code in the cloud without having to worry about infrastructure. You don't think about servers, you think about **services**. Everything else should just scale. Load-balancing, routing, auto-scaling are things that we've become accustomed to worry about, set up, configure and maintain. Well, no more. Because Lever OS comes with these things out of the box.\n\nLever OS's core idea is that you should just throw your business logic at it and it should just work. We handle the complicated infrastructure. You handle your application-specific code and nothing more. It works the same way regardless of whether you run your cloud app on your laptop, for development, or in the cloud.\n\n# Microservice-oriented\n\nLever OS's main building blocks are the services. Under the hood, services may span multiple physical servers across a Lever cloud. Services can communicate with each-other via a builtin RPC system with batteries included. We say batteries included, because it's already set up for you and includes everything you need, out of the box. Things like load-balancing, auto-discovery and sharding, which are normally difficult to set up.\n\nIn fact, we're so keen on the microservice concept that we've designed a standard way for addressing Lever services uniquely, globally, via [Lever URLs](doc:lever-urls). Any service hosted anywhere in the world could RPC into any other service (provided that it has the right permissions).\n\n# Backend\n\nAnd finally, Lever OS is meant as a host for backends. Web app backends, API backends, mobile backends, backends for other backends - you name it!\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Where to next?\"\n}\n[/block]\nTo learn more about how Lever OS works, continue reading about [Services](doc:services).","excerpt":"This page will teach about the building blocks of Lever OS apps","slug":"basic-concepts","type":"basic","title":"Introduction"}

Introduction

This page will teach about the building blocks of Lever OS apps

Lever OS is a **serverless** platform for **microservice**-oriented **backends**. ... Whaterver that means! Well, allow me to explain. # Serverless Lever OS allows you to deploy your code in the cloud without having to worry about infrastructure. You don't think about servers, you think about **services**. Everything else should just scale. Load-balancing, routing, auto-scaling are things that we've become accustomed to worry about, set up, configure and maintain. Well, no more. Because Lever OS comes with these things out of the box. Lever OS's core idea is that you should just throw your business logic at it and it should just work. We handle the complicated infrastructure. You handle your application-specific code and nothing more. It works the same way regardless of whether you run your cloud app on your laptop, for development, or in the cloud. # Microservice-oriented Lever OS's main building blocks are the services. Under the hood, services may span multiple physical servers across a Lever cloud. Services can communicate with each-other via a builtin RPC system with batteries included. We say batteries included, because it's already set up for you and includes everything you need, out of the box. Things like load-balancing, auto-discovery and sharding, which are normally difficult to set up. In fact, we're so keen on the microservice concept that we've designed a standard way for addressing Lever services uniquely, globally, via [Lever URLs](doc:lever-urls). Any service hosted anywhere in the world could RPC into any other service (provided that it has the right permissions). # Backend And finally, Lever OS is meant as a host for backends. Web app backends, API backends, mobile backends, backends for other backends - you name it! [block:api-header] { "type": "basic", "title": "Where to next?" } [/block] To learn more about how Lever OS works, continue reading about [Services](doc:services).