From Excel to the micro-service

Original link: http://www.cnblogs.com/shsxt-sj/p/9359672.html

Excel is very old, the very soil Excel, Excel is not sexy; new micro-services, micro-door service is tidal, micro-serving very large. Then, Excel and micro-services What is the relationship?

  Last month saw the article, The Unbunlding of Excel. The author believes that for start-up companies (especially non "pure IT" start-up company) is, Excel arranged almost all kinds of work. I want to calculate? Please use Excel. Want lightweight CRM, available for Excel. Establish financial analysis model? Or with Excel. Simple project management? Of course Excel. Data analysis overview map? Still Excel. ETL perform simple tasks? Excel appropriate.

  Excel can be doing really so? Logically, it is true. First, many of the company's business is based on data that are operating prototype of the table, Excel "wired" form. Second, Excel provides weak enough and strong enough "programming ability", Excel in VBA, pivot tables, etc. functions for powerful programming language, perhaps not worth mentioning, but many programming languages ​​discourage people are able to these functions use was extremely skillful, playing a lot of tricks to make programmers amazing.

  More importantly, business start-ups tend to be uncertain, businesses need to be explored, business rules also require constant revision. Although Excel is not tailor-made system so perfect, but the cost is very low. For start-up companies, unless they possessor of a very powerful development team, has done enough high-quality system is flexible enough to change the face fierce side also remain stable, or even "the system" are often trapped hands and feet systems, business instead affected.

  If you think it is just Analysis "logical", I can give a more realistic example.

  Today, many companies know to have CRM (customer relationship management) system, and to deal with problems between the customer and the summary. Not to carry out business, CRM or come to buy a set of development, it has become popular mindset. However, bought or developed CRM, may not be very good to meet your business needs, and therefore countless examples stepped pit.

  Friends of the company, did not start on CRM, customer service is only required per person per day with Excel to answer questions down, designate a person summary every night, the next morning after a summary and update the latest Excel via e-mail sent under All customer service, answer questions when in this table to find the keywords with the Ctrl + F. This approach may seem tired annoying, but simple enough to be effective. Not to worry about the system die we all do not live, do not worry about setting unreasonable classification can not be entered or historical data format changes caused by cleaning costs.

  Etc. This process really ran along the stable, the company also old enough to have the time to explore the capital to have customer service management experience and curing processes into the system, CRM system development a matter of course, the line to be put into use quite natural.

  I have seen a company's appliance business, because to catch up with the outlet, business development is extremely rapid. So the company also immediately encountered a problem and founder of the Internet are born to do, to does not matter how rich experience of industrial, warehouse management became more persistent, inventory often a mess.

  How to do? Although they have a small development team, but their daily business has been busy enough, and it is a special storage area, even if not done specifically to look also know that water is very deep, not to mention the rules and warehouse operations are still ways continuous optimization, this time to make a set of easy to use storage systems, is almost nonsense. Every problem, however, many grass-roots workers will complain if there is system just fine.

  Founding team approach is to think of Excel, regardless of how the ever-changing rules warehousing, inventory management, basic, nothing more than storage, a library, the library, and several other actions, the data format is relatively fixed. So, each warehouse work was done every day, no matter how busy tired and then later, also make storage of information in accordance with the agreed Excel template back to the headquarters of the merger by hand statistics. This work is easier said than done to make people suffer a great deal, especially in some overseas distribution warehouse in the time difference, just merge these statistical data every day you have couple of days.

  Now that the boss had said this, the following people have complained about did not dare to send out, can only honestly implemented. The whole process two or three weeks, the daily operation basically no problem, when necessary to improve operational processes, but also probably know how to modify the table. So-record while improving, running for six months, and finally the process is basically the settle down. This time to arrange for product managers, project managers, programmers approach, a clear correlation between watching the daily use of Excel, data entry, data entry, unclear ask the operator also can be answered immediately. This time to arrange the development of warehouse management systems, basic knowledge of the field does not exist any problem, more like yielded thing.

  Carefully observe these two examples, you will find that they are essentially the same, that is not enough understanding of the problem domain, before the problem solution has not yet completely clear, a need for a low-cost means of certain normative same time, on the one hand constraints on existing operations, on the other hand can continue to explore the issue, improve the existing scheme. This time, they chose Excel.

  I had read this article talking about Excel is ready to talk a bit about feelings, coincidentally, and later saw a "spirit" of the article, You are not Google. The authors stress that the big companies do not blindly worship blown marvelous technology, what really matters is to understand your question. This subject, and the above article on Excel's "touted" is actually the same.

  You know GFS and Map / Reduce, but you know they are in order to solve any problem you? In order to calculate, store, index all the pages (at that time about 80 million). You know SOA, but you know what time SOA on Amazon it? At that time Amazon has 7800 employees and an annual turnover of more than $ 3 billion a. You just know that the cluster database, NoSQL, but you know what? StackExchange In 2016, faced with daily visits 200 million, only four SQLServer ......

  Well, now I want to return to the topic, talking about "micro-services" was.

  Micro service is very new, micro service is tidal, micro service very large. I interview an architect, a lot of candidates when it comes to micro-services, can be eloquent, various new term, the concept could not stop jumping out of the frame, but no method to answer a few questions: Why micro services will rise ? When should implement micro service? What should pay attention to the implementation of micro-services? Indeed, even the micro-service relationship with SOA what are confused.

  You know, the architect is not a "framework and solutions to promote the landing officer", he needs to make decisions, software development, system architecture influence decisions is often crucial, if there are problems, the consequences can be quite serious. Therefore, a qualified architect services for micro, not only need to understand the ready-made programs and concepts, but what should be the real question is, what is the basis for decision-making, then we know that his decision is reasonable.

  In my opinion, both micro SOA services also continue to update. When we talk about SOA, the talk is more of a design concept, it requires from the limitation of the software itself, from the abstract "service" point of view to think and design. Since then, come to think about how we can solve problems with software in higher and more abstract level, always and everywhere is no longer subject to the constraints of technology. However, SOA talked about for many years, have not seen specific, recognized, rational landing case.

  Many talk about SOA's book will be talked about a concept: ESB. Hope that one day, as software services can also serve as the hardware, there is a common bus, then all kinds of services need to simply access it. But this may be just a beautiful dream, really put to use ESB is actually quite small.

  Micro services rise, largely corresponds to us in exploring uncharted territory, exploring the unknown question of pace. We can not omniscient to know what part of the system, which links, at what time would be an obstacle or bottleneck, however, we must quickly identify these barriers or bottlenecks, solve them, while ensuring the stability of the entire system. The system is split into a micro-service, in order to solve this problem, it allows us to focus on specific parts and aspects, but also limits the complexity, to avoid the "pull situation as a whole" embarrassment.

  Careful consideration will find that the rise of micro-services, but also to subvert the idea of ​​ESB. ESB emphasized that "re-light communication terminal", micro-services emphasize is "re-light communication terminal", generally only data communication through a simple HTTP, the communication terminal for the bus and not particularly strong business depends. This does reduce the coupling, but also requires a higher end.

  Before we used to just write a little business logic code, generates several libraries, into a huge single system can be assured. After micro-services reform, this is the core of your business logic code only services, since the name "service", you have a fully-equipped, now called "micro-services", you have to snail shell to do temple.

  In other words, the service must be able to deploy a separate, independent maintenance, easy expansion. You have to make a trade-off between clear boundaries and technical constraints services, you have to build a complete monitoring, you have to consider high availability, you have to select the communication mechanism, you have to analyze the load pressure, you have to carefully plan the capacity of the body ...... for architects,

Single-minded consideration of the separation of blindly advocating the benefits of separation is absolutely incompetent: the separation of live of course cool, but they do not know the mundane headed expensive, it is absolutely to starve to death.

  Finally, tell a funny thing, all these years I have several good technical services to micro very deep understanding of a friend, went to start-up companies are often the first thing to do "reverse technology": a dozen people on this seven or eight guns, also toss what micro service? Fast Do not nonsense!

Reproduced in: https: //www.cnblogs.com/shsxt-sj/p/9359672.html

Guess you like

Origin blog.csdn.net/weixin_30685047/article/details/94783908