Trial and Error

The challenge we often face in our lives is that we are required to make decisions as individuals and choose the right things and the wrong things. To make decisions has the potential to change the education, spiritual, physical and psychological atmosphere. The ability to make a decision is expression, choice, desire, and the human quality of confidence. The decision making process occurs in one of two ways: theory and logic, or trial and error. Both have proven to be successful, but one is more exciting than the other.

In TED's lecture on trial and error theme, Tim Harford pointed out that all very complicated systems are the result of trial and error. But you must strictly follow the rules, carefully record the results and check each failure to guide the next attempt. In 2005, Blockbuster dominated the video lease. By 2010, the company applied for bankruptcy, its business model was interrupted by Netflix streaming video and Redbox rental kiosk. Other real stores have also declined and their revenues are compromised by Amazon, e-Bay, and other virtual markets that offer quick response services and convenience.

New business is restricted by growth law. In the early stages of validation of the business model, the requirement is relatively simple, it is a viable strategy to do trial and error by repeatedly publishing it. However, older trading platforms have specific limitations and constraints that can not meet the high-speed access requirements of new services, such as simplified ordering process or independent launch. The old extension mechanism for business logic is a Java SPI (Service Provider Interface) method with over 500 SPIs for business expansion on the trading platform. However, because the specific implementation requirements of these SPIs are not organized and isolated according to the dimensions of the business, the custom logic of the business is scattered throughout the platform code. Every time a new requirement occurs, business parties can only change the platform logic based code to customize the business logic.

After several years of trial and error, a new paradigm of independent expression, business logic, a three-tier architecture with a data layer was born. The data tier is still an RDBMS server, but the database connection pool, distributed transaction coordination, and remote object technology are executed at the business logic layer. The presentation layer will be a web server using HTML and JavaScript. These layers represent the actual hardware components, servers, and network devices that support the software layer defined by the logical type being executed on them. The presentation layer contains user interface logic such as input validation, control focus, etc. and guides the user through application input stream, data representation, and data binding. The business logic layer defines the API for other systems that interact with the presentation or application. Ultimately, the layer becomes stateless and can be expanded horizontally using a network load balancer.