Membrane - Apache MetaModel - Apache Software Foundation
This project has retired. For details please refer to its
Attic
page.
DUE TO SPAM, SIGN-UP IS DISABLED. Goto
Selfserve wiki signup
and request an account.
Apache MetaModel
Pages
Space shortcuts
How-to articles
Page tree
Browse pages
tachments (0)
Page History
Resolved comments
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Copy Page Tree
Jira links
Membrane
Created by
Kasper Sørensen
, last modified on
Nov 08, 2018
Membrane is Data Federation as a RESTful service, based on Apache MetaModel.
Project status
The project was just recently accepted as a subproject of Apache MetaModel.
Our first release, version
0.1
, is out! Check out our
Docker Hub page
for easy-to-use set up steps.
Project information
What
Where
Git repostory
GitHub mirror
Mailing lists
Same as Apache MetaModel
Issues
Same as Apache MetaModel (
JIRA
Docker image
Core concepts
Tenant
A "tenant" in Membrane can be used traditionally as a tenant in a multi-tenant system, where each tenant of the system essentially has his own workspace.
Tenants can also be seen simply as a logical grouping of data sources (see below).
Data source
A "data source" in Membrane is the data that defines a connection to a datastore such as a JDBC database, a file or something else.
Data sources are configured using key/value properties. For example:
"type": "csv",
"resource": "/path/to/file.csv",
"quote-char": "\"",
"separator-char": ";",
"escape-char": "\\",
"encoding": "UTF-8"
or
"type": "jdbc",
"url": "jdbc:postgresql://localhost:5432/mydb"
"username": "johndoe",
"password": "secret"
Security in Membrane
Currently Membrane does not attempt to implement its own security layer. Rather it leans on RESTful principles which would make it easy for you to define a secure HTTP proxy as a security gateway for the service.
Essentially a security gateway could be implemented based on HTTP path and method, like this:
Consider access rights based on the tenant name.
Assign each user to one or more tenants.
First part of the path is the tenant name, so validate access rights based on that.
Consider permissions based on the HTTP method
GET is for "read" access.
PUT, POST, DELETE is for "write" access.
No labels
Overview
Content Tools
Atlassian Confluence Open Source Project License
granted to Apache Software Foundation.
Evaluate Confluence today
Atlassian Confluence
8.5.31
Printed by Atlassian Confluence 8.5.31
Report a bug
Atlassian News
Atlassian
{"serverDuration": 63, "requestCorrelationId": "623f509754aca978"}