简体   繁体   English

FIWARE Orion和用户数据管理vs mysql数据库

[英]FIWARE Orion and user data management vs mysql database

I was asked to create a backend server for storing and managing user information data, specifically using Orion Context Broker. 我被要求创建一个后端服务器,用于存储和管理用户信息数据,特别是使用Orion Context Broker。 How can Orion help me avoid using my own database (for example a local sql)? Orion如何帮助我避免使用我自己的数据库(例如本地sql)? I'm new to FIWARE Orion, and as far as I've read in the manuals, I can create entities and attributes associated with them, something amazing when using node-like entities such as sensors. 我是FIWARE Orion的新手,就我在手册中所读到的,我可以创建与它们相关的实体和属性,这在使用类似节点的实体(如传感器)时会非常惊人。 But how can I store information about many authenticated users if it's mandatory to have a parent-child entity relation like this: user 1 -> car 1 -> cylinder 1 -> tempCyl.. Can I refer to "tempCyl" with only one request? 但是,如果必须有这样的父子实体关系,我该如何存储有关许多经过身份验证的用户的信息:user 1 - > car 1 - > cylinder 1 - > tempCyl ..我可以只用一个请求来引用“tempCyl” ? Or is it mandatory to chain requests (for example set attribute child "tempCyl" to "cylinder 1" and vise-versa? 或者是否必须链接请求(例如将属性子集“tempCyl”设置为“柱面1”,反之亦然?

Also if under "user 1" entity, the information is sensitive, is there a way to protect data with a valid token (like OAuth for example)? 此外,如果在“用户1”实体下,信息是敏感的,有没有办法用有效的令牌保护数据(例如OAuth)? Or do I have to create my own internal (non internet accessible) Orion instance? 或者我是否必须创建自己的内部(非Internet访问)Orion实例?

The easier way of building relationships in an entity-attribute model like the one that Orion implements (eg relationship between A and B entitiesas) is to use some attribute in entity A to point to entity B, eg A.rel = B. If you need bi-directional relationship, then use also some attribute in B to point to A. 在Orion实现的实体属性模型中构建关系的更简单方法(例如A和B实体之间的关系)是使用实体A中的某个属性指向实体B,例如A.rel = B.如果你需要双向关系,然后使用B中的某些属性指向A.

Regarding sensible information, Orion implements a multitenancy mechanism that allowa to partition different set of context information using the same Orion instance. 关于敏感信息,Orion实现了多租户机制 ,允许使用相同的Orion实例对不同的上下文信息集进行分区。 Isolation is done in per-DB basic and can be combined with the FIWARE security framework so only the users beloning to a tenant can access information in that tenant but not the others (have a look to the Orion's PEP documentation ). 隔离在per-database basic中完成,并且可以与FIWARE安全框架结合使用,因此只有属于租户的用户才能访问该租户中的信息而不能访问其他人(请参阅Orion的PEP文档 )。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM