Click to follow asynchronous books , stick to the public number
Share IT good books, technical dry goods and workplace knowledge with you every day
Participate in the topic discussion at the end of the article, and give asynchronous books every day.
- Asynchronous editor
Gong Peng is a full-stack GEEK. He started to learn Java by himself in high school, focusing on the Internet, and has knowledge in software development, art design, product planning and other fields. The founder of Artisan Technology, he has served Ogilvy Interactive, Baidu, and CYTS, and is responsible for the development of car networking design, Internet lottery, e-commerce and other systems. Author of "Microservices Distributed Architecture Development Practice".
Full stack engineer, called Full Stack Developer in English, is an increasingly popular topic in the IT industry circle. Whether it is a large company like Facebook or a start-up company that has just started, they are all beginning to recruit full stack engineers. It is said that Facebook claims: "We only recruit full-stack engineers! It refers to people who have multiple skills and can use multiple skills to independently complete products , and Gong Peng is such a full-stack GEEK.
Basically, when a customer needs a full stack engineer, what the customer needs is an almighty "God". Simply put, a full stack engineer is someone who can complete a product independently. When a client asks him to do some work outside his comfort zone, he rises up to the challenge and successfully completes the task. Today we enter Gong Peng's inner world and listen to his thoughts.
Asynchronous Community: What is it like to be a full stack GEEK?
Gong Peng: When faced with a problem, we can think more three-dimensionally from multiple dimensions . When faced with a specific problem, it is easy to reason and think of many other points associated with it.
Because I like the Internet, I want to know more about it and explore those unknowns . But as time goes by, after understanding, more unknowns will appear. It is precisely because of those unknowns that when faced with problems, I always remind myself to try to think from an objective point of view.
Asynchronous Community: What do you think of a full stack engineer?
Gong Peng: Full stack engineers should start from two perspectives: work needs and personal interests.
In a team with division of labor, or in the face of a large-scale system, it is difficult for individual strength to meet the actual needs of the project. However, in small and medium-sized systems, especially at the beginning of the project, the personal capabilities of full-stack engineers will be fully released in many aspects.
Since full-stack engineers clearly guide the work content of front-end, back-end, operation and maintenance, interaction design, art design, products, etc. in a project, they have a natural advantage in coordinating teams and improving work efficiency, so they will go to management positions in the future. Also a very good choice.
For individuals, what a full-stack engineer does is to pursue what they like and are truly happy people.
Asynchronous Community: What are the most important professional qualities of a full stack engineer?
Gong Peng: Stay curious, keep learning, and always remind yourself to step out of your comfort zone.
Asynchronous Community: What was the original intention to start Artisan Technology? What is the difference after starting a business?
Gong Peng: I have always wanted to make an Internet product of my own. When one's own ability has accumulated to a certain level, it is found that there are still many deficiencies. After careful consideration, it may come from "the butt determines the head". So I tried to think from the perspective of a non-professional person, so I signed up for Craftsman Technology. When you take the first step, it is like opening the door to a new world, and all kinds of problems that you would never think about before follow, and the pressure increases exponentially. For me personally, the biggest benefit is to clarify what I am lacking and to plan a clear learning direction for the future.
Asynchronous Community: When did you start creating "Microservices Distributed Architecture Development Practice"? Have you encountered any difficult problems in the creative process? How to solve it?
Gong Peng: "Sharing" is a very interesting thing. While sharing, it is also a review of one's own abilities. When writing this book, I have been thinking about how to allow readers to quickly build up their understanding of microservices. To solve this problem, I incorporated my own learning method into it.
Every time you learn a new domain, or solve a complex problem. I will not pay attention to the details at the beginning, but try my best to explore the boundaries of this field to establish a framework, and at the same time generate a lot of questions, and then use these questions to guide myself to continuously explore, solve and improve this framework. A clear framework and questions will keep the entire study plan and motivation under control. So when designing the catalog of this book, I hope to introduce as much content as possible around the core of microservices.
In order to minimize the reading difficulty and time of each chapter, all examples are written in the simplest possible way. Try to make the reader be able to read and gain something in a short period of time. It is best if you feel that the content is not enough or if you have new questions. Follow these questions for details.
This arrangement of contents and chapters is largely related to its own shortcomings. I have a wide range of interests, but I also have the three-minute fever problem, but I don't directly confront it. Instead, I think that three minutes is the best time to build awareness. So when I buy a book, I mainly look at the content and thickness, because I know that I can't read a book that is too thick in three minutes.
Asynchronous community: Microservice architecture continues to be hot in 2018, what do you think of this technology?
Gong Peng: The continued popularity of microservices is to be expected, because it really meets everyone's needs. In the past, because the implementation cost of microservices was slightly high, only large companies would adopt them. Now, as the ecology of microservices is getting better and better, the implementation cost is getting lower and lower, so the popularity will continue .
Asynchronous Community: Do you agree with the saying "proper architecture is one of the most important factors in software success"? Why?
Gong Peng: I agree.
"The right architecture is one of the most important factors for software success" is one of the most important factors for success, imagine a very bad software architecture. As the business grows, the system becomes more and more complex and the maintenance cost increases The higher it is, it will also be accompanied by various problems. Yes, the whole system is extremely unstable. This eventually leads to a worthless system refactoring. Refactoring means incurring unprofitable expenses for a certain period of time . If some small companies do not deal with the difficulties of refactoring, it is very likely that the entire software will fail.
Asynchronous Community: What advice do you have for newcomers to the industry?
Gong Peng: It is best to set a clear goal for yourself and keep learning all the time. In the fiercely competitive environment, only by continuously enhancing our own strength can we make progress and not be eliminated.
When setting goals, don't be too ambitious , and find a point with moderate difficulty to make a breakthrough. After all, learning should be happy, because it solves a lot of your doubts.
Learn everything that interests you, whether it's useful to you in the moment or not. When these knowledge points are accumulated to a certain extent, they must be the most useful things in the future.
Asynchronous Community: Is there any plan to publish the next work? Can you "spoiler"?
Gong Peng: If possible, I would like to focus on product development for the next work, from the initial concept to the final project launch, and describe the complete workflow , including product planning, interaction design, art design, front-end development, post-production Terminal development and operation and maintenance.
The key point is also to establish an awareness of the entire product development, to be able to clearly know where one's position is, how to transfer upstream and downstream, and so on. Of course, not only the model and methodology, but also the technology needed to independently develop a system can be obtained.
"Microservices Distributed Architecture Development Practice"
"Microservices Distributed Architecture Development Practice"
By Gong Peng
Click on the cover to buy the paper book
为了更快地实施微服务，本书基于开源且稳定的第三方工具，介绍如何构建一个庞大且复杂的分布式系统，用于满足项目中的实际需求。每一个工具库为了适应更丰富的使用场景，通常都会把部分参数以配置文件的方式暴露出来，同时提供用于开发环境的默认配置。本书基于快速使用为主线路，尽可能多地讲解配置参数的意义及之间的关系。在掌握足够多的知识点后建立起对微服务分布式架构的认知，以便为探求更深层次的知识点做好铺垫。
本书适合Java工程师、初级架构师、大中专院校相关专业师生、Java培训班学员及独立开发者与自学读者使用。
今日互动
说说你对全栈工程师的看法或者对本书的看法？截止时间5月6日17时，留言+转发本活动到朋友圈，小编将抽奖选出5名读者 赠送2本纸质书和3张e读版100元异步社区代金券一张，（留言点赞最多的自动获得一张）。
推荐阅读
长按二维码，可以关注我们哟
每天与你分享IT好文。
在“异步图书”后台回复“关注”，即可免费获得2000门在线视频课程；推荐朋友关注根据提示获取赠书链接，免费得异步e读版图书一本。赶紧来参加哦！
扫一扫上方二维码，回复“关注”参与活动！
点击阅读原文立即购买《微服务分布式构架开发实战》