Separation Times front and rear end, Java programmers changed and unchanged!

It began like this, there is a small planet partners to invite Song Ge answer a question on almost know, the original title is:

• Before and after the end of the era of separation, Java back-end programmers technical advice?

Song Ge looked carefully at this issue, I feel for the front and rear ends of the initial contact with the separation of a small partner, there may be will be this question, and decided to chat with you through this article and the topic.

I try to say here is this question from a Java programmer's point of view, so that we may better understand.

Starting a digression

Many small partners may know, it is the college's undergraduate Song Ge, • Adam Smith's "Wealth of Nations" or to understand a little more or less. Mentioned in the book division of labor is the essence of human society, • Adam Smith believed that professional division of labor between humans can greatly improve productivity, create wealth, specialization is the industrial base of the revolution. The process of development of human society is to continue to refine a professional division of labor, the deepening of the process of separation from the earliest farmers and agriculture to handicrafts separation occurs and then to merchants, in fact continue to refine the division of labor reflects deepening.

Our development of the world is a small universe, continue to refine the division of labor is also a trend, from this perspective, separating the front and rear ends, are worthy of our efforts to embrace.

Before and after the end of the separation development approach in recent years, suddenly fire up, Song Ge I think there are two reasons:

1. The development of the front end. After several years of front-end development, it is no longer called HTML + our traditional drawing, and concepts emerging, webpack, RxJs, Node, Redux, ssr, NuxtJs and other front-end can already qualified for many things, can be completed more rich user interaction.
2. Development of mobile Internet. Two years ago the popular mobile Internet, many companies have product lines, Android, iOS, applets, public number, PC and so on each platform to be displayed on multiple platforms, it is impossible for different back-end equipment to develop a should be multiple front ends share the same rear end, which is not to use the traditional front and rear ends, regardless of the way to develop a back-end application. It is such a business needs to promote the separation of front and back end development.

Changed and unchanged

Change the way the division of labor between programmers, of course, will change along with the development mode. But this change is actually very subtle, very easy to use.

change

• Work content change

Honestly, after the separation of the front and rear end, the requirements of Java programmers becomes low, before we go out we interview Java engineer, regardless if it is, then the front and rear end, the front end will basically asked, a common problem is that the various elements selection device, which is also well understood, because the back-end development, regardless of the way in the front, the back-end engineers to write a little more or less front-end code, it's hard to completely write-only Java code. But in this case, the front-end code you write are actually very simple, it is not particularly difficult.

After separation of the front and rear ends, Java programmers only need to focus on the business logic of the background, foreground transmitted parameters received outside, can give different responses according to the parameters, the front end is substantially not need to write code. Because after this time is different from before and after the front end, regardless of when the front end, the front and rear ends of the splitter, the front still have some difficulty, SPA is more common applications, involving NodeJS, Webpack, etc., but also to make at this time if the back-end engineers write front-end code, the technical requirements for the back-end engineers will be higher.

But having said that, after the separation of the front and rear end, that is if you can write front-end and back-end write, then you can ask your boss for a raise.

• Interface change

Front and rear ends, regardless of the time, rarely comes to interface design to SpringMVC example, you might return it is always something ModelAndView a class, after the separation of the front and rear end, we basically do not need to return to the page, and the back-end mainly It returns JSON data, so the key is to design a good variety of interfaces.

A good practice program is designed to meet the specifications of RESTful interfaces, semantic clear, concise, see the URL you want to know why!

• Changes in development process

After separation of the front and rear ends, the front end can not wait to go back-end interface to better development after development, if so, had two months to finish the project may have four months to complete.

Prior to the general development of the entire project team will need to design a good interface documentation, Swagger generally can be used to do the interface documentation ( SpringBoot integration Swagger2, no longer have to maintain the interface documentation! ), A document agreed details of the interface, the front and rear end respectively, in accordance with the established interface specifications to develop, while not yet developed, it can be tested by means of Mock.

An analog front end is the use of test data, after the development is completed, the front and rear ends of the interface FBI, to complete the test.

constant

In fact, in addition to the changes before and after the end of the interaction, the other places are the same.

Before and after the end of the separation, it is generally not affect the back-end technology infrastructure, you use the SSM or Spring Boot or micro Dubbo or service, both before and after what these technical architecture can support both ends, regardless of your project, you can also support you separate the front and rear end of the project.

So I said back-end technology infrastructure separate from the front and rear end impact.

On the other hand, the same underlying technology, such as you do Java development, SSM of the association / SpringBoot / Redis / Nginx / Dubbo / SpringCloud / MySQL / MyCat / ELK / ... and so on, all have to be.

So, honestly or go to the line and bar code!

Epilogue

If only from a Java programmer's point of view, the front and rear ends in this way separate development, in fact, it is the liberation of Java programmers, allows us to focus on the back end of the work, did not have to write front-end code, industry specializing in surgery, can write better back-end code. But having said that, if you want to maintain a good competitive edge, or the need to look at the way the popular front-end development.

Before and after the end of the separation is not final, but software development methods evolved a point just under the tide, future long way to go, there are many things we need to learn, this is just a one only.

Finally, give the front and rear end of the separation of the article we wrote before recommending several Song Ge:

1. Front and rear ends of a Java program ape eyes of separation and entry Vue.js
2. Spring Boot + Vue separating the front and rear ends, two file uploads summary!
3. Spring Boot + Vue development separated front and rear ends, the front end of a network configuration request package and
4. Spring Boot + Vue separating the front and rear end development, is the idea of ​​rights management

And then recommend two prerequisites:

1. Micro Personnel
2. V tribe

Well, we stop here, there are discussion questions please leave a message.

Public concern number [south] a little rain, focused on Spring Boot + Micro service and front and rear ends of separation full stack technology, video tutorials on a regular basis to share concerns reply after Java, Java dry Song Ge receive carefully prepared for you!