Various distributed system platform background and application in development

A distributed architecture

The architecture distributed English applications and tools for distributed computing , mature and current technologies include J2EE, CORBA and .NET (DCOM), these technologies involve a very wide range of related books are also very many.

This article does not introduce the content of these technologies, nor does it cover the details of these technologies. It is only from the background of the various distributed system platforms and their application in software development to discuss their major differences and similarities.

The distributed system is an old and broad topic. In recent years, due to the rise of the concept of "big data," it has renewed its youth and vitality.

In addition, distributed systems are also a theoretical model and engineering technique. The disciplinary content is more important than the research direction of machine learning. Students who study distributed systems often feel that “it is easy to get started and hard to learn.” Indeed, learning distributed systems requires little knowledge of mathematics.

The distributed system is a complex and broad research field. Learning one or two online courses may not cover all of its contents in one or two books.

In general, the task of a distributed system is to connect multiple machines organically, connect them and let them work together to complete a task, which can be either a computational task or a storage task.

If we must give a classification of distributed system research in recent years, I personally think that it can include three major parts:

Distributed storage system

2. Distributed computing system

3. Distributed Management System

Currently, microservices are hot. Everyone claims to use the microservice architecture. But what exactly is microservice architecture? Is the microservice architecture a trend? We all lack a clear understanding of these issues.

To solve various problems under the monolithic architecture, a microservice architecture emerged. Instead of building a bloated, untamed monster, it would be better to split the service early. The core idea of ​​microservices is service splitting and decoupling, reducing complexity.

Microservices emphasizes the rational dismantling of functions, ensuring that each service is as simple as possible, and defining its role in accordance with the Single Responsibility Principle. Each service is lightened to be flexible and reusable. It can also be deployed separately and independently for horizontal expansion based on the resource requirements of each service.

The Microservice Architecture is an architectural concept that aims to decouple solutions by decomposing functionality into discrete services. You can think of it as being at the architecture level rather than getting services

There are many SOLID principles applied to the class. Microservice architecture is an interesting concept. Its main function is to decompose functions into discrete services, thereby reducing system coupling and providing more flexible service support.

Concept: Split a large single application and service into several or even dozens of supported microservices that can extend a single component instead of the entire application stack to meet service level agreements.

Definitions: Create applications around business domain components that can be independently developed, managed, and iterated to use cloud architectures and flat-bed deployments in decentralized components, management, and service capabilities to make product delivery easier.

Essence: Use some of the functions more clearly, and the business is more refined to solve bigger and more practical problems.

In a literal sense, English in a source file refers to a file that refers to a collection of source code. The source code is a set of characters (program development code) that have special meaning and can implement specific functions.

Source code analysis is a kind of critical knowledge, mastered this kind of critical knowledge, and can remain unchanged. Source code analysis is boring and unreadable for many people.

Source code reading, I think the core of the three points: the basis of technology + strong desire for knowledge + patience.

I think it is the core driving force for reading source code. I have met most programmers. The attitude towards learning is basically these levels (very extreme):

1, only concerned about the project itself, do not understand Baidu.

2, In addition to doing a good job, you will read technical books related to the project and look at Wikipedia.

3, In addition to reading books related to the project, but also read the IT industry books, such as learning Java, but also to understand the functional language, such as LISP.

4, look for some open source projects to see, a lot of trial third-party framework, but also write and write demos.

5, Read the basic framework, J2EE specification, debug server kernel.

Most of the programs are the first one. To the fifth, not only do you need a strong interest, but you also need courage: Can I read it? Actually, you can read it

Patience is really important. Because you rarely see guides or books reading source code, no one asks or recommends reading.

You often get stuck in the process of reading, and a card owner may be stuck in a maze. At this point, what you need to do may be to temporarily interrupt it, and then look at it from the periphery: such as the API structure, the design of the framework.

Fourth, the use of tools

The importance of tools for Java programmers must be first explained. The importance of tools to Java programmers is self-evident. There are many libraries, utilities, and programs for Java developers to choose from. The tools listed below are all essential tools for programmers

Fifth, performance optimization

Whether dealing with front-end interviews or improving product experience, performance optimization is a topic that cannot be avoided.

The purpose of the optimization is to give the user a "quick" feeling. How can the user feel faster?

The loading speed is really fast, the user opens the input URL and presses Enter and immediately sees the page

The loading speed does not get faster, but the user feels your website is fast

Performance optimization depends on several factors, including garbage collection, virtual machines, and underlying operating system (OS) settings. There are multiple tools that developers can use for analysis and optimization. You can learn and use them by reading Java source code optimization and analysis.

It must be understood that no two applications can use the same optimization method, nor does it have a reference path to a perfectly optimized Java application.

Use best practices and adhere to the proper way to handle performance optimization. To achieve truly highest performance optimization, you as a Java developer need to have a correct understanding of Java's virtual machine (JVM) and underlying operating system.

Performance optimization, in a nutshell, is to make it run faster and less time to complete specific functions without affecting the correctness of the system's operation. Performance issues are always one of the eternal themes, and optimization requires more skill.