GitHub code related explaination
We are very grateful for the professional review and suggestions for Uranus’s GitHub from Mr. Andre Cronje.
Currently, Uranus is in its early stage. Therefore our GitHub is still under full development. As we share the open source ideology and hope to contribute to both our society and the blockchain ecosystem, we welcome every suggestion and contribution from the community. According to the stage of project development, part of code is currently available at GitHub address: https://github.com/uraners, such as UraAgent, UraAuth, UraEngine, UraEP, runtime, kubernetes, tendermint.
1. GitHub code and code structure related explaination
【Reply】Current uploaded code structure explaination:
Related code: Tendermint
Related computing power container: UraAgent、UraAuth、UraEngine、UraEP、runtime、Kubernets
2. Explaination of Andre Cronje’s suggestions
2.1 uraAuth coding explaination
【Original comment】Authentication system. Just backend and Flask (Python HTTP library), but let’s have a look.
It’s not often I see SQL scripts in the code, so this is actually a nice oppurtunity for me to talk about some SQL design choices. Data architecture is one of my passions so I take a lot of time and effort with the data modelling side of my designs.
So looking at the above, we see Tel (telephone number) as the primary key and we see it is defined as a bigint (30) with an additional btree index added on top.
1. Maximum regional (with international code) number limit is 36 characters. So I recommend this to be 36 not 30.
2. Primary key already creates a btree index, so the secondary index is redundant
3. As a bigint you will lose the leading 0 and can’t differentiate between local or international numbers.
I have some other concerns, the data types for name/password/email are a bit lazy, just making them 255. And then the rest are more personal preference things, like table names should be plural, and stick to one naming scheme, here we have camel case, we have underscore notation, we have inconsistent capitalization. So probably just a rushed job.
【Reply】This is a very good question, the script mentioned by Andre Cronje is part of the code frame of the uraAuth subsystem. Currently uraAuth is still in its very early stage and the design of the first version is focused on the Chinese market. Therefore this version has ignored the national numbers such as 0086 or +86 to simplify the usage by Chinese users. Without the country code, the bigint(30) will be sufficient to cover all number possibilities. This will be expanded in the coming versions of the uraAuth.
2.2 uraEP coding explaination
【Reply】Andre Cronje has mentioned UraEP is part of Uranus’s high performance byte stream protocol.
Get Uranus’s stories in your inbox
Join Medium for free to get updates from this writer.
UraEP is an asymmetric double-ended connection protocol, which means the server can be connected to both a single client or multiple clients. This protocol is designed to achieve high speed transfers of large amounts of data, and realize features such as multi-ended connection and rapid response. To increase efficiency, Uranus has selected C++ as development language, using IO completion ports to achieve high throughput. These components will also support systems such as linux/Android in the future.
2.3 uraAgent coding explaination
【Reply】Andre Cronje has mentioned that UraAgent is part of Uranus’s computing power container Agent.
UraAgent’s computing container contains lightweight VM’s and containers. In order to achieve high efficient and fine-grained management, the system pre-embedded probes and Agent programs, realizing a life cycle monitoring system of the resource exploration of the computing power containers and task executions conditions.
2.4 uraEngine coding explaination
【Reply】Andre Cronje has mentioned that the UraEngine is part of Uranus’s management engine of the computing power container. Its core architectural framework is partially based on the past projects of the Uranus development team. The current submitted codes is only a small part of the entire frame. It is still under development and will be updated continuously in the future.
3. Uranus project’s open source related plans
In order to further improve Uranus project’s code quality and transparency, Uranus plans to implement the following open source related programs.
During the early stage of the project’s startup, the project development progress will be synchronized and updated through the following weekly code report:
● This weeks code upload
● Next weeks expected code upload
● Total uploaded code
● Code update summary
During the mature stage of the project, the transparency of the project will be enhanced through the following third-party tools:
● Travis CI: Provides continuous integration
● Coveralls: Provides code coverage
● Code Climate: Provides code analysis
● David: Provides dependency analysis
4. Uranus code and Cloud Times code structure related explaination
No clue what’s going on here. Just code copied and some renames. Not sure what the basic HTTP API, Ovirt Engine, and the C client/server have to do with each other, but nothing here yet.
【Reply】The code mentioned in the article is related to the container technologies related virtualization and terminal management software. These codes have been developed by the same team. Part of it falls under to the intellectual property of Cloud Times, but Uranus has paid for the sole right of its usage.
✅Official Channels ✅:
Official Email Address: contact@uranus.io
Official Website Link: uranus.io
Official Announcement Channel: https://t.me/UranusAnn
Official Telegram Group: https://t.me/Uraners
Official Twitter: https://twitter.com/Uraners
Official Facebook Page: https://www.facebook.com/Uraners
Official GitHub：https://github.com/Uraners
