First, give conclusions that can be used for decision-making
The front end of the small program operates in a platform environment, and the order, membership, inventory and content operations are usually still in need of back-end API and database. Enterprises can use their own cloud server, hosting cloud development or SaaS backstage, but three different ways to control, expand, and transport peacekeeping costs.
What conditions need to be identified before judgement is made?
The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.
Suggested order of advance
First, we'll be clear about the target and the border.
The front, back, database and third party services are divided according to function.
Validation Key Dependence
Identification of enterprise-controlled domain names, cloud accounts and deployment areas.
Development of assessable outcomes
Complete filing, HTTPS, white list and access security configuration.
Make sure you decide the next step with the real results.
Validation of certificate renewal, backup, monitoring and permissions before you can go online.
How do you understand it in the actual business?
The appointment program places the entire data on the developers’ personal cloud account, which the enterprise cannot renew and export after the person leaves. The project is launched by a company registered domain and cloud account, which authorizes the team to deploy, thereby avoiding the reliance of technical assets on individuals.
The easiest pit to step on.
Place database key or AppSecret in front of applet
Domain name, cloud server and certificate registered under the developer ' s personal name
Configure HTTPS only, without renewing and monitoring certificates
How should we end up receiving and confirming?
The delivery should check domain names, filings, certificates, cloud resources, databases, keys and platform privileges, and test different networks, certificate anomalies and interface failures. The enterprise should be able to maintain independent renewal fees, backups and replacement maintenance teams.
When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.