Typical Project Case 25——AR, third-party services, user triangle super stable coupling

1: Background introduction

We have developed an AR teaching assistant robot, so that users can see, grasp and help in learning. It is a cooperative relationship with third-party services. Teachers create courses on third-party services and then synchronize them to the AR teaching assistant robot. Teachers log in to the AR teaching assistant robot to push courses, and students log in to the AR teaching assistant robot to learn. This whole process will use 1. The login of the third-party service because some teachers and students' information is on the third-party service; 2. The courses made on the third-party service will be used and need to be synchronized to the ar teaching assistant robot.

It can be seen from the above that the ar teaching assistant robot relies on third-party services, and users also need to rely on third-party services. If the third-party service terminates the cooperation and stops the service, it will be devastating for our ar teaching assistant robot.

Two: ideas & solutions

The main idea is to separate from third-party services, completely separate from third-party services, and partially separate from third-party services. We manage our users ourselves, and we make courses ourselves.

Three: Process

At present, we are mainly divided into two stages. The first stage (transition stage) saves user data in our ar teaching assistant robot for a certain period of time; saves all courses on third-party services in our ar teaching assistant robot, and at the same time Develop our own course-making system.

first stage

In this stage, compared to the previous stage, the coupling is weaker. If the third-party service no longer provides services, the ar teaching assistant robot can still provide services. But the service provision is incomplete (some problems with courses and users, no new courses, and new users on third-party services).

second stage

Authority system (user management), AR teaching assistant robot (push courses, learn courses), TAR course making system (do lessons, synchronize courses)

At this stage, we have completely broken away from the third-party service, we have our own course-making system (and we also have the course-making data in the third-party service before), and we have all the user data of the third party (also supports registration of new users ). We got rid of the coupling to third-party services, and turned the coupling to the Tar class system that we manage and maintain.

Four: Summary

1. Reduce uncontrollable factors, such as third-party services, and replace them with the Tar class system that we can manage and maintain, increase certainty, reduce uncertainty, and provide stable services.
2. High cohesion, low coupling. Each module is responsible for doing one thing. Permissions (management) Tar (classes) AR (teaching). Dependency management after each other. The advantage of this is that it is convenient for later expansion and respective maintenance.