The technological changes and ups and downs of the past years

Recently, a small Java Web application was written from beginning to end, and the last full write Web application was three years ago,
After all, in recent years, focus on the backend service architecture, but there is less opportunity to write a complete Web program from the front to back end.
And every time there is such a chance, I always follow up with the latest web technology to develop, after all, three years ago, the hand of the technical tools now seem to be senile,
Recalling these years of technological change and ups and downs, can't help feeling.

The end of C/s

When I entered the programmer this profession, the mainstream enterprise application development is also in the C/S era, and the B/s structure is in the ascendant.
The mainstream enterprise system architecture is C/s. For example, the database acts as the Server side, and many of the business logic of the year is also implemented in the database with stored procedures.
The mainstream of client development is the three tool pb/vb/delphi shown in the figure.

Early I used PB development, and later turned to Delphi, contact with Object Pascal, for the first time to understand the object-oriented language and design ideas, Borland This company is also full of admiration.
Then the B/s structure is gradually rising, some project customers require B/s structure, and have to start the transformation.
At that time for Web development faced with two options ASP and JSP, although there is only one letter of the difference, now look back to this choice on the post-transition career development can be greatly affected.
Finally, I chose JSP, the follow-up on the Java programmer this road, but the basis for decision-making is only because I heard that Java mainstream development tools JBuilder is also Borland developed.

The chaotic rule of JSP opening

Just beginning to learn Java into the era of writing JSP, basically is the chaotic era of Java.
JSP has the business logic Java code, has the Operation database SQL statement, also has the page to display the style CSS and the page itself HTML, occasionally also scattered several paragraphs JS to control the pop-up window and so on.

When I write a JSP file to 10,000 lines of code, I finally can not stand, and then a large number of reading, Internet search in the end how to write JSP is right?
Then I knew the design pattern, not just the 23 patterns mentioned in GoF's book. Big mode has to say how the enterprise application of the architecture, small mode has to say for some kind of work how to write code.
The most divisive is that the Java industry is going through two factions of the great melee, each faction has a variety of different models of best practice books, articles to prove that they are the best choice.
Finally I do not know how to write the program, some people say:

For a novice programmer, the design pattern is no more troublesome than the problem it solves.

Yes, I should have the same feeling, originally wrote the program belongs to take the sword on the Thorn, although not the discipline is also quick, but learned a lot of moves after every time the sword is in consideration of the moves with no, the sword is creaky many.

EJB vs Lightweight Java EE

At that time Java Enterprise application development of the Orthodox non-Java, and the core of the EJB,EJB is essentially a distributed object technology, advocating object-level component reuse.
EJB is also the technology of Java Standards Commission, and the grassroots of Rod Johnson has launched a technological revolution,
In the translator's preface to the book "Development without EJB", there is a sentence:

Any programmer who engages in the development of the Java EE application has had this feeling more or less: the world is full of concepts and "big words",
Like a deep, magical forest of magic, I don't know whether to follow this mentor or believe in that door.
At this point, Rod Johnson issued a amazing publication: Ye do not have to worship 泥胎 Idol, the Holy Spirit is ye itself-this is what he has advocated in the book "Evidence-based architecture."
What is the basis for choosing an architecture and technology? Rod Johnson believes that it should be based on practical evidence, experience from historical projects or hands-on experimentation,
Rather than any form of idolatry or sectarianism. The book talks about the problems and solutions of enterprise applications, none of which is the product of this "evidence-based approach".
In addition to giving these programs to the reader, Rod Johnson's more important message, which he hopes to convey through the book, is the "evidence-based" way of working-that should be the way programmers work.

That year I just entered a large-scale company, in a project of the technical Solution selection Discussion conference, for the end use of EJB debate endlessly.
Looking back, the dust settles and the lightweight Java EE wins, and the Spring Open source framework created by Rod Johnson replaces the EJB's location.
And the "evidence-based framework" of the idea has been deeply rooted, today we discuss technology selection has already been put down doctrine, only focus on the problem itself.

The lightweight Java EE advocates a faster, simpler programming model and better maintainability by distributing the application itself to achieve horizontal scaling.
Martin Fowler Even in his book "Enterprise Application Architecture Model" in the name of the open:

The first law of distributed object design: Do not distribute objects.

To the final conclusion of the EJB, buried in the technology of the loess, become the dust of history, and the Spring-centric model of the application of SSH-like framework to start the river and rivers.
If a programmer in the post-EJB era is missing something, then it is most likely that there is a sword (SSH) that does not have a spectrum (evidence-based approach) and is not thought of, thought of, and ignored.

SOA and micro-service

With the development of the Internet, the scale is growing, the application is more and more complex, even though the use of lightweight Java EE technology, although lightweight, but the business has become very heavy.
Single-application-hosted businesses are becoming more and more complex, and a single application poses a huge challenge to the parallel collaboration of large development teams.

The idea of a large Internet company based on SOA explores a new architectural technology path, represented by Amazon and Netflix abroad,
A new approach to application architecture is proposed, which is an implementation of SOA: micro-service.
MicroServices emphasize the single responsibility principle of service, and the principle of object design emphasized in object-oriented design,
It's a little ironic that today's distributed services are a bit like the distributed objects that EJB advocates, but microservices are slightly more granular than objects.

And from the above diagram can be seen, now distributed service Architecture, specialization division of labor to a finer granularity.
In the early years, basically from the page development to the database, are all-stack engineers, now the page is page building and JS development of the distinction,
The technology stack for the backend service is more diversified, the technology is constantly changing, and you and I will sink and swim.

Opened a new public number, in CSDN mainly send some technology-related original articles, the public number will have more other aspects of the article, interested in the code to scan subscription.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

The technological changes and ups and downs of the past years