lightblue-core

KO | EN

gitlite — search

#python #nodejs #javascript #dart #flutter #typescript #rust #template #react #mod #android #html5

★ 34 Open GitHub ↗

Document based data access layer framework

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

[![Coverage Status](https://coveralls.io/repos/lightblue-platform/lightblue-core/badge.png?branch=master)](https://coveralls.io/r/lightblue-platform/lightblue-core?branch=master) [![Stories in Ready](https://badge.waffle.io/lightblue-platform/lightblue.svg?label=ready&title=Ready)](http://waffle.io/lightblue-platform/lightblue)

# Books!

* [Overview](http://jewzaam.gitbooks.io/lightblue/)
* [User Guide](http://jewzaam.gitbooks.io/lightblue-user-guide/)
* [Developer Manual](http://jewzaam.gitbooks.io/lightblue-developer-manual/)

# lightblue

Cloud focused data services with dynamic querying, versioned schemas, and robust security.

![lightblue architecture](https://raw.githubusercontent.com/lightblue-platform/lightblue/master/docs/lightblue-puzzle.png "High Level Architecture")

## Why lightblue?

Developing enterprise services for access to data (CRUD) can be deceptively simple.  Just write something that gives access to the data you need.  Done!  The challenge is how do to deal with growth over time and not replicate the data access layer for every component.

### Why is it so hard to add a new field?
* Adding a field may break backwards compatibility for clients of a service.
* Updating all service clients is not easy to schedule.
* Adding new APIs on the service solves the above problems but leads to sprawling APIs and inconsistency.

### Can we move our data to MongoDB?
* Migrating from one type of tech to another is not trivial, such as RDBMS to NoSQL.
* Moving some proprietary database technologies outside of a traditional datastore can be very costly.
* Changes in underlying datastore will lead to optimized ways accessing the data.  This changes APIs!

### Why is Information Security so concerned with moving to a cloud provider?
* When you control your data and application tier hardware it is easy to be lax with security.
* Moving data and applications off of hardware you control requires robust security.
* Enabling the move to public API access to even sensitive data requires a lot of rigor.

### Do more with less!
* IT budgets are shrinking while business demands continue to rise.  Any place cost can be reduced relative to gains is great!

### How does lightblue benefit developers?
One of the time sinks for developers is adding new features for clients of their software.  To address this for data access, lightblue provides a robust and very capable API, supports a growing number of datastores, and enables changes to data models without impacting existing clients through the use of versioned metadata.

#### Robust API
The REST API of lightblue is designed to do everything a client could want.  There are some key points that the API addresses:
* Query: a very rich query language
* Projection: return only the data a client wants
* Bulk Operations: ability execute CRUD operations against many records or entire collections

#### Datastore Agnostic
Clients do not care where data is stored as long as it is available and secure.  With lightblue we have controller implementations for:
* MongoDB (1.9.0 and higher)
* RDBMS (ANSI SQL92)

Not seeing a contoller you need?  We welcome new implementations and contributions in general!  From opening a request for enhancement to writing code, your ideas and help are greatly appricated.

#### Versioned Metadata
All data in lightblue is controlled by its metadata.  Think of this as all the DDL for a table in a relational database.  
A specific version of this metadata provides a view of the stored data.  You can have many versions of metadata active at a time, providing different clients with different views of this data.  Key points to remember:
* all data structures are captured as metadata
* each data stucture can have multiple versions active at a time
* each client deals with data of a specific version
* clients using different versions are seeing the same data, just viewed through a different window

### How does lightblue benefit operations?
One of the challenges with maintaining enterprise applications is ensuring they are always on.  When any change to a data structure requires application deployments it requires operations resources and can require outages to execute.  With lightblue any changes to a data structure is simply a change to metadata.
* metadata updates are not software changes
* metadata updates are guarenteed backwards compatible

Example workflow to update a single field without lightblue:
![Slow](https://raw.github.com/lightblue-platform/lightblue/master/docs/slow.png)

Example workflow to update a single field *with* lightblue:
![Fast](https://raw.github.com/lightblue-platform/lightblue/master/docs/fast.png)

Some other benefits beyond simply reducing operations overhead are:
* lightblue is designed to be deployed anywhere
* lightblue employes a flexible component architecture that enables components to be deployed and scaled independently
* lightblue is built to be both latency and fault tollerant
* lightblue works with your preference of authentication and authorization

### What about support and development tools?
If lightblue enables data access across many datasources and technologies we also need to provide tools to support that stack!  Enter the management applications:
* Metadata Management Application
* Data Management Application

![Lightblue Applications](https://raw.githubusercontent.com/lightblue-platform/lightblue/master/docs/overview.png)

Each of the applications provides access to the corresponding service layer.  The point of them is provide a nicer interface to the service layer without having to deal with the service directly.  Each application can be secured independent of the service tier, as noted in the diagram.

## See lightblue in action!
* Deploy lightblue on OpenShift: [openshift-lightblue-all](https://github.com/lightblue-platform/openshift-lightblue-all)
* Deploy lightblue with basic-auth:
* Deploy lightblue with SAML 2.0:

# License

The license of lightblue is [GPLv3](https://www.gnu.org/licenses/gpl.html).  See LICENSE in root of project for the full text.

# Dependencies

| Dependency | Why | License
| ---------- | --- | -------
| [Jackson](http://wiki.fasterxml.com/JacksonHome) | Java library for processing JSON documents.  Use in complicated cases where processing is required on the JSON document. |[Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
| [JSONassert](https://github.com/skyscreamer/JSONassert) | Used in unit tests to compare JSON documents before and after processing.  Useful for verifying parsing and type conversions (JSON -> Java -> JSON for example) | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
| [json-schema-validator](https://github.com/fge/json-schema-validator) | Validation of JSON documents against a JSON schema.  Similar to XML Schema validation. | [LGPLv3 or later](https://www.gnu.org/licenses/lgpl.html)
| [Flapdoodle Embedded MongoDB](https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo) | In memory MongoDB used in unit tests to test against a real database. | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
| [mongo-java-driver](https://github.com/mongodb/mongo-java-driver) | MongoDB driver for Java.  Used for all interactions with MongoDB from Java. | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
| [pyresttest](https://github.com/svanoort/pyresttest)| Python utility for testing and benchmarking RESTful services. | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0)

lightblue-core

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README