iOS platform (mobile platform) architecture issues

An awkward encounter.

I feel that layering the project is a very good idea, so I look for information about the layering of iOS projects on the web. Helpless, the network on the IOS Project architecture very little (finally proved that I went wrong in the big direction, the architecture should be independent of the platform, so "IOS" architecture information is not found), even if there are several blog, but also the wild way out of their own. (Personal thinking is more conservative, not authoritative things can not convince me, and in fact, everyone can see that the blog is an over-design problem)

Later, I tried to discuss the problem in the Code4app group, and several active group Friends of the group were "free to discuss" the architecture problem.

Then in the "with MJ End abuse iOS3.0" This group, but also by the red fruits of ridicule: MVC is enough, and what layer?

Did not deliberately talk about the group of friends, just want to take the facts for example: now quite a few developers, on the architecture and layering this thing is not enough. Then, I know the benefits of layering, although some discouraged, but not give up. Finally, Martin Fowler wrote the << Enterprise Application architecture Model >> a book, circumnavigated enlightened.

is tiering necessary for mobile devices?

I was the first to do Java, access to the project is relatively large, there will be architectural design. Then go to the mobile, you will consider whether the mobile also really need architecture design

As long as the software, there will be changes in demand, then the layering is very necessary. That is, we need to leave a "way" for our own software, to decouple it and make it extensible.

Hierarchical architecture design of low-coupling enterprise system architecture involving and mobile platform

On the big side, architecture is necessary and the key is how to execute it.

A system, the structure of what it is, what components it is, what is the relationship between the components, and what is the relationship between the environment, is a matter of design architecture (or layering) to consider.

The aim is to establish a low-coupling enterprise application system, the advantage of low-coupling system is to refine the color development, improve the development efficiency, improve the scalability

Requirements are constantly changing, causing the system to fail to meet demand changes because it is strongly coupled, between modules and modules, between classes and classes.

The benefits of low coupling are too many.

• Strong scalability
• High efficiency
• Adapting to changes in user needs

So our system maintenance work is less, is more flexible

What is an enterprise-class system

This question has been discussed in the basic concepts and evolution of my architecture-the blog park (or the concept of CSDN architecture and the most basic three-tier architecture-ios Enterprise Application Architecture design), but there is a need to mention it here:

The system is very large, involving the front end, backstage (database, middleware, actual equipment)

Today's Java. NET can build enterprise-class systems.

Attention Points of the design

Design must be considered very thoughtful, so there is a file, need to reduce the coupling degree. Layering, rational use of design patterns within each layer This is: architecture design and Design patterns

The thing between each layer must be a collection of classes and subsystems with similar functionality.

Can be divided into four levels, five layers, or even one layer, the second floor. Every kind of division must have its own truth.

such as your house, to open a window, the result is collapsed, it is not reasonable to explain the design

This article a lot of ideas and inspiration from Dongsheng Teacher's video, video in 51cto can be searched, but paid, I just learned the content of the first section of free, I feel good, but also in the attempt to seek the teacher layering irrationality, found Martin的<<企业应用架构设计>> a book, began a further exploration. Thank the teacher here.---me

iOS platform (mobile platform) architecture issues