How to create a mass. NET application: Fatdb Introduction to distributed computing platform

Challenge

Creating a modern, large-scale application is a daunting task. Customers expect high performance and fast response, and "access to" their data anytime. The operations team wants applications to be easy to configure, maintain, migrate, and diagnose problems. The development team wants to use a similar technology paradigm, with a simple API with easy-to-use tools and the ability to take advantage of existing people and legacy code. Finally, business people require applications to have a competitive advantage: they want the application to be affordable, fast to market, and able to respond quickly to changing business policies. In the past, we can basically determine that the enterprise will have to give up a large part of the demand, in order to release the application as soon as possible. Even now, it is often seen that different technologies have been blended to create a large project of Byzantine architecture (large scale). Such projects are often structurally fragile, slow and overly complex. Today, the proliferation of cloud technologies, platforms, services (PaaS) and NoSQL are just enough to deal with this part of the process, and their emergence is no coincidence. The reality is that it is not easy to "work in the right way" while meeting the needs of stakeholders, and it requires us to discard obsolete patterns and adopt new ways of thinking.

FATDB Solutions

About 6 years ago, Fatcloud's sister company, Wilshire Media, provided the largest streaming web service for companies such as CBS Radio, AOL and Yahoo. The development processes of these projects are similar in nature, and the challenges are almost the same. We find ourselves constantly doing repetitive things, but never simplifying the development of these projects. We urgently need a complete solution that can do the following:

Communication between multiple nodes in a flexible and fault-tolerant manner.

Store, retrieve, and query data and files.

Cache data.

To achieve maximum load capacity, parallel and eliminate network latency as much as possible.

Provides two ways to work with synchronous and asynchronous multithreading for frequently changing business logic.

Minimize downtime when expanding or reconfiguring a cluster.

Automate configuration, monitoring and maintenance of large clusters.

If the product on the market time is very important, you can strictly control the development time.

We immediately realized that we could make full use of the experience of our previous work, in this process to meet stakeholder requirements and reduce business sacrifices. The key to solving these problems is a simple concept: abstract the key features of enterprise applications into a proven, reusable, high-performance, fault-tolerant, highly integrated, and distributed platform. The fulcrum for this approach is what we now call task-oriented architecture (Mission oriented architecture) or MOA. This universal framework has now evolved into what we know as the Fatdb platform technology. About two years ago, fatdb the first major test of the technology, when Cricket Wireless, the US company, launched a mobile music service, Muve, which now has more than 1 million subscribers. Muve's background is built almost entirely on the Fatdb platform, which runs on hundreds of servers. From then on, we set up the Fatcloud company around this technology. The number of application types that can be created based on the FATDB platform is unlimited, and the scope of FATDB applications spans multiple vertical industries. Our mission is to provide this technology to the Microsoft Development Community to simplify the complexity of enterprise development and reduce costs. We want to help our clients avoid the mistakes we've made. By providing customers with a series of powerful and sophisticated building blocks, they can help them radically improve the way they create large-scale web applications and overcome each challenge.

So what are the building blocks that the Fatdb platform contains? Its core products can be divided into nine parts altogether:

Core Basics – This section provides basic functionality for all components of the FATDB platform.

fatdb/cache– is one of the finest NoSQL databases and memory caching services.

fatfms– A Distributed File Management service.

fatwq– a queue and processing service for an asynchronous bulk task.

fatapps– a software Development kit (SDK) and a set of schemas that support a WCF service based on synchronization.

fatprocessors– an SDK as well as a set of architectures that provide asynchronous bulk task processing routing and are integrated with FATWQ.

Fatdb Management Studio (FATDBMS)-A graphical user interface that allows users to configure, check, monitor, query, publish, and maintain their servers, data, and business logic in their various development environments (development environment, test environment, production environment, and so on).

A subset of features with SQL Integrated –fatdb, FATWQ, FATFMS, and Fatdbms that allow users to take advantage of the power of the FATDB core Services in a series of ways, and retain and even increase their usage in SQL Server.

Map/reduce analysis-A subset of functions in Fatdb, FATWQ, FATFMS, and Fatdbms that allows users to perform data mining or online analytical processing (OLAP) analysis to extract large amounts of raw data. Provides a reference for business metrics as the next step in development.