System as a service, how to improve the system global control and design capabilities?

To a relay, talk about their own views, swim, abandoned brick jade, look forward to more small partners to share.

System as a service

Large to the traditional logistics system, small to a departmental wiki system, in the final analysis, people need to use, people use the purpose is to meet a certain demand, the system for the needs of users and services.

Imagine a service-free IT system, even if the code algorithm write a great, programming language use the world's best language PHP, the database has the most powerful Oracle in the universe, storage is the best EMC equipment in the galaxy, not to provide users with reliable and stable security services, It's just a bunch of expensive, worthless crap.

The direction of service is to improve the price/performance of user and service support.

Whether it is QQ or, abstract to the user Service level are the most cost-effective solution to meet the needs of the user's physiology above (after all, not directly as food to eat), such as security, communication, attribution, showing off, loading force and other needs, as well as a money from users (such as games, such as various drills, such as various members) It or business systems that take users to make money, such as various ads, are also providing services to users or customers directly or indirectly to realize their value.

The so-called system global Control and design, the individual think is large to the entire business system, small to a single service system, how to be more cost-effective (low cost), more flexible (easy to respond to change), more reliable (high-availability continuous service) to serve users, in short, is a system at the beginning of the design to consider what factors These factors must be considered in addition to functionality.

system-to-service

The process of system-to-service is the process of system operation and maintenance, service management or technology operation. System design should consider the late delivery of the characteristics of the service requirements, such as the manufacture of cars to take into account the convenience of tyre replacement, the reliability of bad weather, in the design of the business system should consider a system of the operational dimension, whether the support of modular scale-out, whether support high availability, support cluster management, Whether there is good fault tolerance and debugging ability, support the stability of extreme network or complex situation, whether the system service is graded (easy to manage and trade-offs) support gray-level off some of the minor features, business and operational logs are detailed and easy to troubleshoot problems and so on.

System global control and design, we need to stand in the height of the planning city to move bricks.

For various reasons, developers often do not consider how the code they write will affect the online operating environment. After the developer has modified the configuration or environment, the operating environment is not communicated to the operator in a timely manner. Development is driven by functional requirements (often directly related to business requirements). Operations are driven by non-functional requirements such as availability, reliability, performance, and so on. The greater the size of the change, the greater the risk, because the more areas involved. As operators try to avoid changes, the speed at which new functionality flows into the production environment is slowed down, slowing the speed at which developers will pay the user a special * * *. Operators may have a lack of understanding within the application, making it difficult to choose the runtime environment and the publishing process correctly. Developers may have a lack of understanding of the runtime environment, which makes it difficult to adjust the code correctly.

Move brick height to move brick finally is a pair of bricks, build building height to build building finally is a lot of rotten tail building, planning the height of the city to move bricks, although still moving bricks may one day maybe a city. Now it may be that we are developing a small system without a few users, if only to meet the needs of the product to do, then pray that the product does not fire, fire may also be due to the poor service experience early death, imagine if every day collapse exit, payment is unsuccessful, or can not pay the account, No more good products can not withstand the bad service experience toss it.

A business system is divided into pre-and post-operational phases throughout the development process, and these two phases, while clearly divided, are in fact related, and are part of the DevOps philosophy. Prior to operation, we need to focus on efficient and responsive software development and management methodologies, such as agile development, versioning, quality assurance, security, high availability and load balancing, problem and event management, and user experience feedback to facilitate pre-operational iterations.

Service and Management

To improve the system's overall control and design capabilities of the premise, need to understand what needs to be controlled, what needs to be designed?

Here, from an operational perspective, in the pre-operation stage of development, in addition to meet the product requirements, we need to pay attention to what? There is no doubt that these are also the operational processes that must be concerned.

Service is the most important thing, stable, stable, stable, important things to say three times.

How can we ensure that the service is stable and usable? The factors that affect stability are various changes, function changes, configuration changes, changes in the environment (the network is bad, the disk is full, the server hangs), some things active change, some are passive changes, to deal with so many changes, should have a system to ensure the stability of the service available.

Of course, all this is not my summary, in fact already Daniel to us summed up, all business systems are services, IT service management is the most well-known theory of ITSM,ITSM is based on ITIL, a set from planning, research and development, implementation to operational dimension of the standard method.

The core idea of ITSM is that it organizations, whether internal or external, are IT service providers whose main job is to provide low-cost, high-quality IT services. The quality and cost of IT services needs to be judged from the IT service's customers (buying IT services) and the users (using IT services). ITSM is also a service-centric IT management process-centric process that combs core processes from complex IT management activities, such as incident management, problem management, and configuration management, standardizing and standardizing these processes, clearly defining the objectives and scope of each process, cost and benefit, operational steps, Key success factors and performance indicators, the intrestes of the people involved, and the relationships between the various processes.

From what we can see, ITSM has three goals:

User-centric services (the user is God, the user experience complaints to be sensitive, timely tracking);

Provide high-quality, low-cost services (with the fewest machines, write the fewest code, with the worst servers, the most service users);

The services provided are measurable (business visibility, logs, logs, logs, important things to say three times).

The three core of ITSM: technology, process, personnel, and ultimately service to the business.

IT services need to focus on the entire operational process:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/71/7F/wKiom1XSFbXBX02QAAMuiW_tIpE251.jpg "title=" Itil3.png "alt=" Wkiom1xsfbxbx02qaamuiw_tipe251.jpg "/>

From the perspective of operations, it is inevitable to generalize, ITSM said that the business is the core, the process is the key, the overall structure is simple and clear, as to what technology to achieve is also very important, as to when the expansion, when the split, when the cache, which is the specific technical implementation, ITSM is not the case, Hope that the development of students can be more from the perspective of development to talk about this topic.

Kneel down and beg.

Learning and Promotion

Multi-brush to know, less brush Weibo

Pay more attention to the industry cattle, less bite the dog.

A person is useless, the team is reliable.

Don't waste your energy on what the tool can do.

To have a girlfriend, so physical and mental health, to devote themselves to work.

Understand pyramid thinking (corresponding to linear thinking) and systematic thinking (corresponding to a single point of thinking).

System as a service, how to improve the system global control and design capabilities?