Brief introduction of dynamic implementation of large application system based on Jython

Introduction

With the rapid development of the information age, the internet has penetrated into e-commerce, finance, telecommunications, logistics, resources and other fields and gradually become an integral part of it.

In the information age, time means money. With the popularization of a variety of large-scale applications, people's stability of the system, and 0 downtime hardware constantly put forward higher requirements, but often ignore the application system itself to bring problems.

What is Jython

Jython is a complete language, not a simple Java translator or Python compiler, which is a complete implementation of Python in Java. Because Jython inherits the features of both Java and Python, it makes it seem unique.

See here the reader will certainly ask, what is the relationship between Jython,java and Python? In fact, I understand that Jython is simpler, the Python interpreter implemented in the Java language, which means you can write programs in Python and use the Java library simultaneously.

Find problems

Large application systems can be broadly divided into:

UI Layer

This layer should be said to be relatively stable, or its changes will not have a particularly serious impact on the operation of the system as a whole.

Interface Layer

This layer is closely related to the upper UI and the underlying implementation, called far-reaching. As an architect or system designer for a large application system, it is often possible to make this level of design and definition relatively flexible for the sake of maintenance costs and development costs.

Implementation Layer

This layer can be said to be the core of the system level, the whole system's core processing logic will be placed on this level. And often this layer, in the actual use of the process is also the most unstable, the most easy to change from the perspective of demand.

Data tier

The layer is actually said that the database layer, for User data query, assembly, update and so on, to provide a durable data services, we can think it is also a relatively stable level.

The focus of the issue seems to be finding out how to make our implementation layer more flexible as a core problem. So how can the core of our system "keep pace with the Times"?

Analyze problems

Next, let's look at what the implementation layer of a system might do:

Receive user data passed through the interface

Processing user data According to certain business logic

Update processing results to the database (optional)

Responds the processing results to the UI layer and renders it

Analysis to here. We have a further intuitive understanding of the implementation layer's internal data flow. And we have to realize the definition of the so-called variables, it is more obvious, how to achieve the separation of business processing logic becomes our goal.

Solve the problem