##What?

• Enterprise/systems/services/applications create and modify organisational data databases
  • Storing data as information requires federated and heterogeneous storage capabilities
  • FD provides a standardised way of accessing this data.
  • Standardization enables discussions about information without loosing visibility of the data
• Visualise and operate on the semantic entities of your business
• Simplify management dashboards, operational metrics
• Look around and into your data to perform forensic analysis
• Deliver information and data to any digital platform
• Track data lineage back to originating systems of record

##FlockData

• Manages data as information
• Object model and services to deliver FDH-IP
• Exposed via RESTful web services
• Full text - help users find data irrespective of the system that created it
• Store history of data changes letting you keep audit out of transaction processing systems

Stable. Full support for ElasticSearch 1.7 and Neo4j 2.2.x in place.

Collect, Connect Compare and Explore - FlockData helps you find data you're looking for.

FlockData is a system of insight built as a DataShore using the principals of Microservices and Domain Driven Design. We define the service boundary for writes as Audit (tracking data changes) and Search (indexing your data). An exciting off shoot of this idea is that by tracking your data as information you also gain an analytics platform for the powerful query analysis, offered by graph and search databases, indexed in a consistent manner.

Turn your information in to an accessible resource. See if our data Mission aligns with your way of thinking.

##Design FD follows the design concepts of a Microservice. As a service it is in fact itself made up of microservices.

FlockData is inspired by Domain Driven Design (the way we look at information), ROA & SOA architectures (API access). It integrates sophisticated index technologies and document management logic in to highly scalable JSON databases. The result lets you look at your information in new and innovative ways to discover patterns in information.

Loosely coupled services have become the way to build systems to support independent scaling and reduce impact of change. Tracking the information that flows across these services becomes vital when it comes to analysing issues both technically and from the user's experience. FD supports this approach by using Event Sourcing techniques.

##Datastores FlockData coordinates and directs information to various highly scalable data sources to achieve functionality.

• elasticsearch
• neo4j
• redis
• riak
• rabbitmq

##Features

ElasticSearch is a specialized database enabling you to create complex keyword queries and sophisticated aggregations that respond quickly. Put Kibana on the front and you can start to accumulate realtime dashboards that give you the pulse of change in your business. With FD tapping in to your applications, you can offer your staff Full Text Search capabilities across your actual business data - FD makes it possible to search "the latest version" of your business document, i.e. your Customer record, Invoice, Inventory item, whatever; irrespective of data underlying system created it. 

Think LogStash for application data. FlockData maintains your ElasticSearch data giving you cross-system search capabilities in hours.

Neo4J is the world leading graph database enabling you to explore how your business information is connected. FD builds a graph for you by using information tags that you determine to be of value. Start exploring your enterprise information as a social graph in hours.

You need to gain a brief understanding of two of the key FlockData scalable micro services

• fd-engine - tracks changes to your data - think LogStash for business data
• fd-search - find entity information tracked by fd-engine into ElasticSearch

Familiarise yourself with the general API on our Wiki

Drop us a line over at flockdata.com and we'd be happy to see if we can help you reach your goals. Usual social media channels also apply - LinkedIn .

We encourage contributions to FlockData from the community. Here’s how to get started.

Latest code is on the develop branch. Master contains last stable release.

• Fork the appropriate sub-projects that are affected by your change. Fork this repository if your changes are for release generation or packaging.
• Create a branch
• Make your changes and run the test suite
• Commit your changes and push them to your fork
• Open pull-requests for the appropriate projects
• We will review your pull-request, suggest changes, and merge it when it’s ready and/or offer feedback

To report a bug or issue, please open a new issue in our Jira issue tracking system.

We want you and others to get the most out of FD. We use GPL to ensure that changes to FD code can be made shared with everyone. We lay no claim to any of your system or services that are talking to the FD API or databases. FlockData is an open source project. We support a Community edition under the GPLv3 license. The Enterprise edition is available under the AGPLv3 license for open source projects otherwise under a commercial license by contacting. Talk to us about clustering as there can be costs involved with the underlying stack.