Home

• explain
• command-line
• schemas
  • b: ms: base
  • c: msc: concept
• contact

Meshy Space

"Meshy Space" creates collections of information, which can easily be shared between people and organizations. All applications collect data —be it for configuration or user collected— but that activity is surprisingly underdeveloped. Meshy Space creates a powerful abstraction for managing data-sets together.

The implementation is underway. Many ideas still need to be written down. Even more plans still need to be implemented. Please contribute your thoughts.

• The schemas are under construction. Follow the daily process of interface development, mainly the ms: base schema and the msc: concept schema.

Overview

"Meshy Space" creates a distributed infrastructure to share any kind of data; for instance, pictures, software packages, or legal documents. It organizes the storage, provides additional meta-data, distribution and caching, access-right management, data life-cycle management, and more.

"Meshy Space" offers a super-set of data maintenance and transport features provided by file-systems, ftp-servers, micro-services, object storage, and databases. Actually, it is an additional abstraction level: it builds on those technologies. The maintenance of data is made more important, and the technology gets pushed back.

Besides, "Meshy Space" standardizes registration of licenses, jurisdiction, traceability, identities, revokation, and data collection rules: it implements advanced data governance, which can be executed outside the implementation of the service logic.

>> See the bigger picture, a bit more about the technical motives.

"Meshy Space" is primarily a specification, which can have different implementations. The specification currently supports XML and JSON serializations in all communication between layers.

Object Sharing

"Meshy Space Base" implements namespaces with Units. Every unit contains a collectable item. Every unit has a name, contains some payload (some bytes), documentation, and relations to other units. Most sophisticated: the Unit has a life-cycle from creation to destruction.

Typical Units are a picture, a PDF document, a set of translations, or a software release package. A bit more abstract purpose is a public identity, a piece of storage configuration, or filter settings. Really abstract Units are constants (the name of the Unit represents a constant) and interface descriptions. Everything is a Unit to be managed!

Object Governance

"Meshy Space Concept" implements Collections, which resemble our physical society collections. Collections group data for a certain purpose, for instance a Linux distribution, holiday photos, emails, or books.

To be able to share collections in real-life, you main need contracts, licenses, access-rights, and so on. This "concept" comes much closer to human behavior than existing storage approaches.

Collections can collect (sub-)collections, shard their data over physical servers, set rules about the collectables, and much more.

Compatible data-sharing

Over the years, many forms of data-sharing have been introduced. For instance, an ftp-server or a network disk. The users have to agree on the protocols and interpretation of the content via a side-channel: reading documentation, ad-hoc protocols.

In recent years, there was a move to object storage: the data contains more meta-data and transport is less visible. Still, users need to exchange web-site locations and access-rights for each application in a technical way.

Meshy Space makes an extra step: the objects are largely standardized and data-transport is hidden. The developer of services simply wrap their data in a Unit, and drop their Unit in a Collection. Who maintains and has accesses to the Collection is separated from the data collection itself. Collections are very flexible configurable and portable.

Smaller services

As the picture above shows, a heavy burden is taken away from the services: the input and output of information is taken care of. The full focus of the service is on the task at hand. It is less work to create multiple dedicated tasks: think in Components forming applications together.

Where micro-services (like SOAP or REST interfaces) provide a pull interface (specific data delivered on request), is Meshy Space designed to also support huge and fast changing data-sets (can distribute millions of Unit containing tera-bytes of data per day). It can also be used as micro-service on small Collections.

>> More on components, explained via the example of building a search engine.

Compatible communication

Meshy Space designs standard communication between Collection maintaining servers, owned by different businesses, organizations, and private people. Standardization is crucial for improved cooperation.

>> More on messages.