This work is based on ideas and experience building complex data systems and applications using at times EJBs, Hibernate, myBatis or even plain JDBC. Those systems have included real-time predictive modeling, standard 3-tier transactional web applications, and classical data warehousing. Tilda aims to be as transparent and simple as possible for the modern data engineer. Its transparency is critical in helping use Tilda simply as a model management tool with minimal adoption risk, or as a full fledge data application building block (the all-in approach). All assets generated are human-readable from the get go and are easy to walk through and understand if need be (but you don't have to). Tilda takes a decidely model- and data-centric view of the world: we believe you cannot build a complex data application without thinking about your data model. We believe that no framework can hide your database, so why try? This is Data to the metal, all the way up full stack.
At this time, Tilda only supports Java 1.8+ as a target language, and Postgres 9.5+ as a target Database (while exploiting features from V10, V11 and V12 if available). However, it may not be too hard to implement other target languages in the future (such as JavaSCript or .Net for example), and other data stores (MS SQL Server, mySQL, and also non-relational backends such as Cassandra, MongoDB or Hadoop). Ultimately, we are aiming for an extensible data architecture that would enable integration with different formats, such as CSV, or HL7 (a standard healthcare data exchange format), and the ability to extend the patterns supported (feeding data to predictive models for example). Tilda ultimately strives at identifying core patterns used in a complex data-driven application, and capture them as reusable declarative bits so you can assemble them to match your needs.
We are making progress on the overall documentation for the project: Releases are posted in the standard Github location here. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this code except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
The copyright is retained by CapsicoHealth Inc as Copyright (C) 2015 CapsicoHealth Inc.
The code is currently setup as an Eclipse Java project. Once you fork/clone the repo, you should be able to simply import the project into your workspace. Tilda is all self-contained at this time, and can generally be used as a base project, for your application. You can also of course build your own JAR and take the libraries independently. Tilda is currently dependent on several other libraries both for the tooling and at runtime such as:- Apache Commons DPCP2
- Apache Commons IO
- Apache Commons Logging
- Apache Commons Pool2
- LMAX Disruptor
- GSON
- Apache Log4j 2
- Postgres JDBC driver
You are free to use those in your application if they fit your needs. However, we are always in the lookout to use other libraries if their functionality matches our needs, so it's very possible that over time, some of the Tilda utilities get deprecated and phased out.
We are working on getting-started tutorials and videos that will live in the Wiki.