Skip to content
Everything-as-a-service
Java Other
Find file
Failed to load latest commit information.
auth Update to cope with refactored fathomdb-shared
bash_completion
bin Update to cope with refactored fathomdb-shared
bindings Update to cope with refactored fathomdb-shared
db Fix job_logs item-key column type int -> text
examples Created examples directory
meta/findbugs Initial import
ops Support lazy-delete, so we can shutdown when a server is dead
packages Initial import
schemas
services Support lazy-delete, so we can shutdown when a server is dead
shared Support lazy-delete, so we can shutdown when a server is dead
utils/gwt-codegen Changed path to JsHelpers
xaas Create SimpleConfigurationModule
.gitignore Add tests for openldap and fix a few problems found along the way
LICENSE Fixed company name in license
README.md Updated README to link to wiki and to point to the most stable services
install.sh Move scripts to bin
pom.xml Support lazy-delete, so we can shutdown when a server is dead

README.md

PlatformLayer: Everything-as-a-service

Introduction

PlatformLayer is open-source platform-as-a-service software. Instead of tying you in to one stack though, you can build your platform from whatever components you want (pick your own database, webserver, load balancer etc).

PlatformLayer builds machines on clouds running OpenStack.

Because there are so many choices of software you could make, PlatformLayer makes it super-easy to build a new service if one doesn't already exist. That's why we say PlatformLayer is everything-as-a-service.

Right now it's early days, so please do contribute if your favorite service isn't yet available. Have a look in the services directory at the services we're working on. To build a service, you create a java classes which define the 'model' which the service will expose; you create a 'controller' for each model which describes how to build the model; you also create a service class which ties it all together.

The intention is to have a lot of simple services which work together, rather than a complex design. Services build on each other to produce complex systems.

There's lots of code for lots of different services in the tree, much of which is still fairly experimental (it's early days).

These are good ones to try out first:

  • memcache: Runs memcache, which is the simplest service (Cache-aaS)
  • solr: Runs solr, allowing full-text indexing & search (Search-aaS)

Check the wiki for more information!

Installation

Please see the wiki

Something went wrong with that request. Please try again.