Click on the asynchronous book, the top public account
Every day to share with you IT good books technology dry goods workplace knowledge
Participate in the topic discussion at the end of the article and give asynchronous books every day.
— Asynchronous small editor
Gong Peng is a GEEK. He began to learn Java by himself when he was in high school and focuses on the Internet. He has the knowledge of software development, art design, product planning and other fields. Founder of Jangong Technology, he has worked for Ogilvy Interactive, Baidu and CyTS, responsible for the development of Internet of vehicles design, Internet lottery, e-commerce and other systems. Author of “Micro-service Distributed Architecture Development Practice”.
Full Stack engineer, or Full Stack Developer, is an increasingly hot topic in the IT industry, with both large companies like Facebook and start-up companies recruiting Full Stack engineers. Facebook reportedly said, “We only hire full-stack engineers! Someone who has multiple skills and can use them to make a product independently,
Basically, when the customer needs a full stack engineer, the customer needs a complete “god”. Simply put, a full stack engineer is someone who can complete a product independently. When a client asked him to do something outside his comfort zone, he took the bull by the horns and got it done. Today we go inside Kyopeng’s mind and listen to his thoughts.
Asynchronous communities: What’s it like to be a full-stack GEEK?
Gong Peng: When faced with a problem, I can think in a more three-dimensional way from multiple dimensions. When facing a specific problem, he can easily infer many other points associated with it.
. But as time goes on, more unknowns emerge. It is because of those unknown existence, in the face of problems also always remind myself to try to stand in the objective perspective to think.
Asynchronous community:What do you think of full stack engineers?
Gong Peng:
In a collaborative team, or in the case of a large system, it is difficult for individual efforts to meet the actual needs of the project.
Since full-stack engineers clearly guide the work contents of front-end, back-end, operation and maintenance, interaction design, art design, product and other links in a project, they have natural advantages in coordinating team and improving work efficiency, so they are also a very good choice to work in management in the future.
For individuals, what full stack engineers do is to pursue what they like, and they are truly happy people.
Asynchronous Communities: What are the most important professional qualities for full stack engineers?
Gong Peng:Be curious, keep learning, and remind yourself to step out of your comfort zone.
Asynchronous communities: What started Crafting Technology? What’s different about starting a business?
Gong Peng:
When the accumulation of their own ability to a certain extent found that there are many deficiencies, after careful thinking may come from the “butt determines the head”. So I tried to think from a non-professional point of view and signed up for Artisan Technology. When taking the first step, it is like opening the door to a new world, all kinds of problems that you didn’t even think about come along, and the pressure increases exponentially. For me, the biggest benefit is that I have identified what I lack and planned a clear learning direction for the future.
Asynchronous Communities: When did you start working on Microservices Distributed Architecture Development? Did you encounter any difficult problems during the creation process? How is it solved?
Gong Peng: “Sharing” is a very interesting thing. Sharing is also a review of one’s own ability. While writing this book, I have been thinking about how readers can quickly build up their awareness of microservices. In order to solve this problem, I integrated my own learning methods into it.
Every time you learn a new area of knowledge, or solve a complex problem. I will not focus on details at the beginning, but try my best to explore the boundaries of this field and establish a framework, while generating a lot of questions, and then these questions guide me to constantly explore, solve doubts and improve the framework. Clear framework and questions will make the whole learning plan and motivation in their own hands. Therefore, when designing the contents of this book, I hope to introduce as much as possible related content around the core of microservices.
To keep the difficulty and time of each chapter to a minimum, all examples are written in the simplest possible format. Try to make readers able to read in a short period of time to gain. If the content is not enough or new questions arise, that is best. Follow these questions for details.
This arrangement of catalogues and chapters is largely related to their own shortcomings. I have a wide range of interests, but I also have a three-minute fever problem, but I do not directly fight against it. On the contrary, I think that the three-minute period is the best time to establish cognition. So when I buy a book, I mainly look at the contents and the thickness, because I know I can’t read a book that’s too thick in three minutes.
Asynchronous communities: Microservices architecture continues to be hot in 2018. What do you think of the technology?
Gong Peng: It is not surprising that micro services continue to be popular, because it really solves everyone’s needs. In the past, microservices were only adopted by large companies due to the higher implementation cost. Now, as the ecosystem of microservices is getting better and better, the implementation cost is getting lower and lower, so the popularity will continue.
Asynchronous communities: Do you agree with the statement that “the right architecture is one of the most important factors in software success”? Why is that?
Gong Peng:
“Appropriate architecture is one of the most important factor in the success of software” is one of the most important factor in success, try to imagine a very bad software architecture in as the growth of the business, the system becomes more and more complex, the maintenance cost is higher and higher, may also be accompanied by a variety of problems, the whole system unstable. This results in worthless system refactoring.
. If some small company does not handle the difficulties of refactoring, it is likely that the entire software will fail.
Asynchronous communities: What advice do you have for those just starting out?
Gong Peng:
In the competitive environment, only by constantly enhancing their own strength can progress and not be eliminated.
Find a point of moderate difficulty to break through, after all, learning is supposed to be fun, because it solves a lot of your doubts.
When these knowledge points accumulated to a certain extent, in the future is bound to be the most useful things.
Asynchronous community:Do you have any plans to publish your next book? Can you give us a little “scoop”?
Gong Peng: If possible, my next work would like to focus on product research and development. From the initial concept to the final project launch, I would like to describe the complete workflow, including product planning, interaction design, art design, front-end development, back-end development, operation and maintenance, etc.
Not only the models and methodologies, but also the techniques needed to develop a system on your own.
Micro-service Distributed Architecture Development Practice
Micro-service Distributed Architecture Development Practice
The Gong Peng
Click on the cover to buy the paper book
In order to implement microservices more quickly, this book, based on open source and stable third-party tools, shows how to build a large and complex distributed system to meet the actual needs of a project. Each repository typically exposes some of its parameters in configuration files to accommodate richer usage scenarios, along with default configurations for the development environment. This book is based on quick use of the main line, as much as possible to explain the meaning of configuration parameters and their relationships. After mastering enough knowledge points, establish the cognition of micro-service distributed architecture, so as to pave the way for exploring deeper knowledge points.
This book is suitable for Java engineers, junior architects, teachers and students of related majors in colleges and universities, Java training students, independent developers and self-taught readers.
Tell me what you think of full Stack Engineer or the book? Deadline May 6th, 17:00, leave a message + forward this activity to the circle of friends, xiaobian will be lucky to select 5 readers
Two paper books and three E-reading copies of a 100 yuan asynchronous community voucher, (the one with the most likes will automatically get one).
Recommended reading
A list of new books for April 2018
Asynchronous books the most complete Python book list
A list of essential algorithms books for programmers
The first Python neural network programming book
Long press the QR code, you can follow us yo
I share IT articles with you every day.
If you reply “follow” in the background of “Asynchronous books”, you can get 2000 online video courses for free. Recommend friends to pay attention to according to the prompts to get the gift book link, free asynchronous E reading version of a book. Come and join us!
Micro-services Distributed Architecture Development Practice
Read the original