Difference between revisions of "User talk:Bucheron"
Jump to navigation
Jump to search
m |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Well, this is the place where you can chat with me !! | Well, this is the place where you can chat with me !! | ||
| − | My vision of pdb | + | == My vision of pdb == |
* a central RDBMS managing one or more databases | * a central RDBMS managing one or more databases | ||
| − | + | ::- databases with strong long-term definitions of object classes | |
| − | + | ::- with event data synchronization capability on regional "slave" servers | |
* Dedicated projects separated by "domain of interest", each implementing services or micro-services on https servers | * Dedicated projects separated by "domain of interest", each implementing services or micro-services on https servers | ||
(eg interaction with the public, interaction with "manufacturers", synchronization with external data, media management, authorization management, etc.) | (eg interaction with the public, interaction with "manufacturers", synchronization with external data, media management, authorization management, etc.) | ||
| Line 11: | Line 11: | ||
| − | My doubts | + | == My doubts == |
* Is it a good idea to split the "attributes" of an object into two parts : | * Is it a good idea to split the "attributes" of an object into two parts : | ||
| − | + | ::- id (PK), uniqueName ... in SQL columns | |
| − | + | ::- attributes "nullable" in one or more JSONB columns | |
* how to manage object "variants" | * how to manage object "variants" | ||
* how to define "family", "category", "type", "group", "product" ... for an efficient hierarchy | * how to define "family", "category", "type", "group", "product" ... for an efficient hierarchy | ||
* is it possible utilize a world-wide unique product-id | * is it possible utilize a world-wide unique product-id | ||
* where to place internationalization (database or file-system) | * where to place internationalization (database or file-system) | ||
| − | |||
| − | + | == Softwares I use == | |
| − | Softwares I use | ||
* Proxmox | * Proxmox | ||
* Debian | * Debian | ||
| Line 34: | Line 32: | ||
* Mattermost | * Mattermost | ||
* Zimbra | * Zimbra | ||
| + | |||
| + | <br><br><hr> | ||
| + | [[User:Lx&R|Lx&R]] ([[User talk:Lx&R|talk]]) 08:12, 1 April 2019 (MSK) | ||
| + | :: It's a kind of discussion that should be made point by point and not right now. | ||
| + | :: Our plan: | ||
| + | ::# Domain name and hosting | ||
| + | ::# People are starting to fill in the database | ||
| + | ::# The database begins to be in demand. | ||
| + | ::# We are expanding hosting options | ||
| + | :: Wiki is a powerfull engine: [https://en.wikipedia.org/wiki/Special:Statistics Wikipedia statistics] | ||
| + | |||
| + | <br><br><hr> | ||
Latest revision as of 03:16, 2 April 2019
Well, this is the place where you can chat with me !!
My vision of pdb
- a central RDBMS managing one or more databases
- - databases with strong long-term definitions of object classes
- - with event data synchronization capability on regional "slave" servers
- Dedicated projects separated by "domain of interest", each implementing services or micro-services on https servers
(eg interaction with the public, interaction with "manufacturers", synchronization with external data, media management, authorization management, etc.)
- authentication with a key in HTTP header (no session)
- role-based authorizations
My doubts
- Is it a good idea to split the "attributes" of an object into two parts :
- - id (PK), uniqueName ... in SQL columns
- - attributes "nullable" in one or more JSONB columns
- how to manage object "variants"
- how to define "family", "category", "type", "group", "product" ... for an efficient hierarchy
- is it possible utilize a world-wide unique product-id
- where to place internationalization (database or file-system)
Softwares I use
- Proxmox
- Debian
- Nginx
- PostgreSQL (PostGIS)
- Java
- Vert.x
- Javascript
- Gitlab
- Redmine
- Mattermost
- Zimbra
Lx&R (talk) 08:12, 1 April 2019 (MSK)
- It's a kind of discussion that should be made point by point and not right now.
- Our plan:
- Domain name and hosting
- People are starting to fill in the database
- The database begins to be in demand.
- We are expanding hosting options
- Wiki is a powerfull engine: Wikipedia statistics
