[Cloud native] iVX low-code development introduces Tencent Maps and previews it online

Hits: 0

! Hello everyone , I’m [ Bug Terminator ] , [Quality Creator in CSDN Java Field]🏆, Alibaba Cloud invited expert blogger🏆, 51CTO popular blogger🏆.
A highly motivated, strong learning ability in the [ Java field ] Blogger ]😜😜😜
🏅[Bug Terminator] The field of blog is the learning of [back-end technology], and will continue to update more [back-end technology] and [learning experience] in the future. Occasionally, I will share some basic knowledge of the front-end, update the actual project, and develop applications for the enterprise level !
🏅 If you are interested in [back-end technology] and [front-end field], please pay attention to [Bug Terminator] 💞💞💞

❤️❤️❤️Thanks to everyone, cute and cute! ❤️❤️❤️

Article directory

1. iVX first chapter

iVX official website address

This article explains the use of iVX development to introduce online maps

iVX is the world’s first low-code development platform. Its visual editor and zero-code development greatly improve development efficiency!

2. Why use iVX?

The iVX platform provides developers with a one-stop service for the entire life cycle of application development based on the cloud development model

Based on the cloud development model, the iVX platform provides developers with a one-stop service for the entire life cycle of application development. Users can complete application development, testing, release, and operation and maintenance without any environment configuration. The tools provided by the iVX platform include: application development tools cloud IDE (iVX editor), application management tools (iVX workbench), and application operation and maintenance tools (iVX work statistics, iVX application services), etc. Provides team coordination tools, as well as application data management tools, application version management tools, etc.

Cloud native IDE, you can write directly by opening the web page

Open the webpage and use it, drag and drop + configuration to achieve code-free development . “Full scene + full system” support, can be published as web pages, APPs, desktop applications, small programs and small games with one click.

3. The advantages of low code, fully [visual] editing

iVX is committed to a new domestic “programming system”, “removing program syntax and retaining program logic”, making “everyone programming” possible

With the help of iVX’s advanced language features and platform’s one-stop full-cycle services, both individual developers and enterprises can gain huge advantages in the competition in the Internet and software markets. In addition, the iVX platform has also built a number of marketplaces that facilitate value exchange for developers and enterprises in the iVX ecosystem.

Fourth, the overall architecture design of iVX

Overall system architecture design

The front-end and back-end separation architecture is adopted, that is, the logic of the front-end part and the back-end part are completely independent, and the two communicate through service components:

⛅Front-end application type

The front-end core framework of iVX is a web application, the main body uses the react architecture, some internal modules use the self-developed object-driven engine, and reference canvas rendering libraries such as pixi.js and three.js. At the same time, web applications can generate other types of applications through different packaging methods

Internal structure of web application

As shown in the figure above, iVX’s web application includes two environments, one is a data-driven environment, that is, a dom environment based on react, and the other is an object-driven environment, which is an animation and game environment based on html canvas. The two environments are relatively independent. The object-driven environment is mounted in the data-driven environment in the form of a react node. Therefore, regardless of whether the components of the data-driven environment are used in the application, the data-driven environment will be loaded first.

In each set of environments, there is a corresponding component set. The above figure lists all the main component sets currently provided by iVX, as well as the basic libraries it depends on.

☁️Back-end technical architecture

Background logic structure

1. Service request processing layer

The front end of the service logic, responsible for receiving service requests, request routing, certificate generation, etc. In iVX, this layer is a program implemented by the GO language (caddy, which can be understood as a lightweight nginx).

2. Service logic layer

Core service logic processing, further including default services and custom microservices. The default service, that is, the business logic we define in the editor “service component”, this part of the logic is currently defined by JS, and then further compiled into a web assembly program that is run by the GO language. Each service, corresponding to a GO coroutine (goroutine), will automatically complete the service concurrent processing in the background. Application developers only need to be responsible for the definition of service logic and do not need to care about the processing of the underlying concurrent business.

Custom microservices allow users to define part of the background logic in other background languages ​​(temporarily support java and node js), and then call them through RPC methods in the service. To customize a microservice, you need to define a background custom component first. After the component is compiled, it will run as a docker image.

The service logic layer, whether it is a default service or a custom microservice, is a “stateless” service, that is, it does not store any data locally on the server, so the “state” data is stored in the background resource layer (including the redis cache). , message queues, mysql, es databases, files, etc). The advantage of this is that the deployment of the service logic layer can be completely “serverless” to achieve high-performance elastic expansion.

3. Background resource interface layer

iVX provides interfaces for connecting and operating various common background resources, and encapsulates these interfaces as resource components, including various databases, caches, and message queue components. In the [2] service logic layer, we only need to directly call the method of the component to realize the operation of various background resources. For example, we call the database output service in the service. At this time, we actually call the database output interface provided by the background resource interface layer. In this interface, iVX realizes the database connection, SQL generation, and return result processing steps, all These logics are implemented by the background resource interface layer. The background resource interface layer is a microservice cluster implemented by the GO language, based on the go micro microservice framework.

Like the service logic layer, the background resource interface layer is also a “stateless” service, enabling “serverless” deployment.

4. Background resource layer

The background resource layer is a variety of existing background resources, mainly various types of data storage services, including databases, caches, message queues, file object storage, etc. [3] The background resource interface layer provides operations on these resources method.

Note that in the above figure, the background resource layer is represented by a dashed line, because iVX itself does not provide these resources. For example, iVX does not provide a mysql database. The mysql database is an existing resource, and iVX is only responsible for operating it. On the public cloud platform, various background resources use the related services of aws Amazon cloud, all resources are configured, and developers do not need to manage; in private deployment, these resources need to be prepared by developers themselves, which can be stored on the local server. Install the software, or use the resources provided by various cloud platforms. iVX does not limit these resource deployment methods, you only need to specify the methods and methods of related resources in the config file of private deployment.

For more information, please visit the ivx official website to view the detailed information ivx official website

5. Use the iVX online editor to introduce and deploy Tencent maps

⛄New project

Open the iVX official website , register an account, click to experience it now

select web application

The following interface is created

⏳ Introduce map, button components

Introduce button, click btn button, automatically generate button style

Click the button or the menu on the right to edit the properties after selection

Edit text information to map information, center display

Centered display can add custom styles

Add map component

Select the front-end component and add map information to the front-end component

Edit map-related information

Query latitude and longitude tool

Enter the latitude and longitude you want to achieve to display different geographic location information

✅ Release preview

Click Compile and Preview to jump to a new page to preview the effect



The above is a brief introduction of [ Bug Terminator ] to [Cloud Native] iVX low-code development introducing Tencent Maps and online preview . iVX low-code development makes everyone programmable~

If this [article] is helpful to you, I hope you can give [ Bug Terminator ] a like👍, it is not easy to create, if there are cute little ones who are interested in [ back-end technology ] and [ front-end field ], please pay attention ❤️ ❤️❤️ 【Bug Terminator】❤️❤️❤️, I will bring you a huge 【Harvest and Surprise】💝💝💝!

You may also like...

Leave a Reply

Your email address will not be published.