Design your own application Development Framework One (intro)

This series of articles is intended for those who are prepared or have developed a custom development framework. As a result of the work relationship, plan a week or two to write an article for each person who is interested in design or library development to provide criticism and discussion. Given the variety of frameworks under Java, this Code section is used. NET to say things. Of course, this article can be used as a place for criticism and discussion by other language programmers without looking at the code section. Because of my limited level, only the simplest code to explain the simplest application, I hope to let you in a simple application to obtain a not simple inspiration.

The directory is as follows:

Design your own application Development Framework One (intro)

Design your own application Development Framework II (architecture)

Design your own application Development Framework III (data manipulation and business entities)

Design your own application Development Framework four (business class library and business logic)

Design your own application Development Framework five (plugin authoring and user interface)

Design your own application Development Framework VI (exceptions and logs)

Design your own application Development Framework VII (internationalization)

Design your own application Development Framework VIII (plug-in)

Come to the point

As the summary says, if you or your company is not a single application, or is not just for a short period of time application software. Or would it be cool to extend your Internet product to Facebook so easily? So the title, you need a rapid application development of the custom framework.

What kind of framework.

is always able to help you complete a lot of work, not rigidly adhere to only one development of Dongdong. This definition sounds more like a large class library. Of course, it also has to assume the role of supporting the entire software skeleton, not only to provide a lot of robust. NET Framework or JVM not common functions, but also to the entire development process to achieve effective control.

How fast.

You or your company is good at the development direction of what you must be better than I know, good is usually the most commonly used. Different projects always use the same technology and code snippets, so why not summarize them and make a common development module?

Why it's easy to expand.

Why is it that the blade server is selling so much fire. Because blades can say goodbye to more cables and do not have to degrade performance to reduce energy consumption. So does our software development have to say goodbye to more coupling and less efficient program execution to add new modules? In a tiered model of application development, small software does not cause obvious coupling and layering, but once the future size of the software is large and may even add new modules at any time, have you ever thought about using a development model to limit it. If it's just a hard rule, would it be more appropriate to write this development pattern into a framework for application? What's more, with the introduction of SaaS throughout the world, the more problems you face in your daily development process are the result of expansion and change.

whether plug-in development ?

Looking at the text above, I firmly believe that you already want your system to achieve a scalable development model. But that's when we usually face another problem, and that is whether we use the form of plug-in development to organize our code. When you're sure you want to use Plug-ins to structure your own system, then how do you choose the architecture that works best for you? In the last installment of this series, I'll explain a little bit of my idea of plug-in development.

So good, in order to let us no longer repeat the work, the layering clearer, the code coupling is lower, is easier to expand, to follow the rule, the development is more agile, develops a suit own custom development framework, ^o^