Update README.md

Author: sharajava

README.md

@@ -1 +1,96 @@
-# fescar
+# FESCAR: Fast & EaSy Commit And Rollback
+
+[![License](https://img.shields.io/badge/license-Apache%202-4EB1BA.svg)](https://www.apache.org/licenses/LICENSE-2.0.html)
+
+-------
+
+## What is FESCAR?
+
+A **distributed transaction solution** with high performance and ease of use for **microservices** architecture.
+
+### Distributed Transaction Problem in Microservices
+
+Let's image a traditional monolithic application. Its business is built up with 3 modules. They use a single local data source.
+
+Naturally, data consistency will be guaranteed by local transaction.
+
+![Monolithic App](https://cdn.nlark.com/lark/0/2018/png/18862/1545296770244-4cedf37e-9dc6-4fc0-a97f-f4240b9d8640.png) 
+
+Thing changed in microservices architecture. The 3 modules mentioned are designed to be 3 services on top of 3 different data sources ([Pattern: Database per service](http://microservices.io/patterns/data/database-per-service.html)). Data consistency within every single service is naturally guaranteed by local transaction. 
+
+**But how about the whole business logic scope?**
+
+![Microservices Problem](https://cdn.nlark.com/lark/0/2018/png/18862/1545296781231-4029da9c-8803-43a4-ac2f-6c8b1e2ea448.png) 
+
+### How FESCAR do?
+
+FESCAR is just a solution for problem mentioned above. 
+
+![FESCAR solution](https://cdn.nlark.com/lark/0/2018/png/18862/1545296791074-3bce7bce-025e-45c3-9386-7b95135dade8.png)  
+
+Firstly, how to define a **Distributed Transaction**?
+
+We say, a **Distributed Transaction** is a **Global Transaction** which is made up with batch of **Branch Transation**, and normally **Branch Transation** is just **Local Transaction**.
+
+![Global & Branch](https://cdn.nlark.com/lark/0/2018/png/18862/1545015454979-a18e16f6-ed41-44f1-9c7a-bd82c4d5ff99.png) 
+
+There are 3 basic components in FESACR: 
+
+- **Transaction Coordinator(TC): **Maintain status of global and branch transactions, drive the global commit or rollback.
+- **Transaction Manager(TM): **Define the scope of global transaction: begin a global transaction, commit or rollback a global transaction.
+- **Resource Manager(RM): **Manage resources that branch transactions working on, talk to TC for registering branch transactions and reporting status of branch transactions, and drive the branch transaction commit or rollback.
+
+![Model](https://cdn.nlark.com/lark/0/2018/png/18862/1545013915286-4a90f0df-5fda-41e1-91e0-2aa3d331c035.png) 
+
+A typical lifecycle of FESCAR managed distributed transaction:
+
+1. TM asks TC to begin a new global transaction. TC generates a XID representing the global transaction.
+2. XID is propagated through microservices' invoke chain.
+3. RM register local transaction as a branch of the corresponding global transaction of XID to TC. 
+4. TM asks TC for committing or rollbacking the corresponding global transaction of  XID.
+5. TC drives all branch transactions under the corresponding global transaction of  XID to finish branch committing or rollbaking.
+
+![Typical Process](https://cdn.nlark.com/lark/0/2018/png/18862/1545296917881-26fabeb9-71fa-4f3e-8a7a-fc317d3389f4.png) 
+
+For more details about principle and design, please go to [FESCAR wiki page](https://github.com/alibaba/fescar/wiki). 
+
+### History
+
+- **TXC**: Taobao Transaction Constructor. Alibaba middleware team start this project since 2014 to meet dirstribuited transaction problem caused by application architecture change from monolithic to microservices.
+- **GTS**: Global Transaction Service. TXC as a Aliyun middleware product with new name GTS was published since 2016.
+- **FESCAR**: we start the open source project FESCAR based on TXC/GTS since 2019 to work closly with community in the future.
+
+
+## Quick Start
+
+[Quick Start](https://github.com/alibaba/fescar/wiki/Quick-Start)
+
+## Documentation
+
+You can view the full documentation from wiki: [FESCAR wiki page](https://github.com/alibaba/fescar/wiki).
+
+## Reporting bugs
+
+Please follow the [template](https://github.com/apache/incubator-dubbo/issues/new?template=dubbo-issue-report-template.md) for reporting any issues.
+
+
+## Contributing
+
+Contributors are welcomed to join FEATS project. Please check [CONTRIBUTING](./CONTRIBUTING.md) about how to contribute to this project.
+
+
+## Contact
+
+* [Gitter](https://gitter.im/alibaba/nacos): TBD. FESCAR's IM tool for community messaging, collaboration and discovery.
+* [Twitter](https://twitter.com/nacos2): TBD. Follow along for latest FESCAR news on Twitter.
+* [Weibo](https://weibo.com/u/6574374908): TBD. Follow along for latest FESCAR news on Weibo (Twitter of China version).
+* [Segmentfault](https://segmentfault.com/t/nacos): TBD. Get latest notice and prompt help from Segmentfault.
+* Email Group:
+     * TBD: FESCAR usage general discussion.
+     * TBD: FESCAR developer discussion (APIs, feature design, etc).
+     * TBD: Commits notice, very high frequency.
+
+## License
+
+FESCAR is under the Apache 2.0 license. See the [LICENSE](https://github.com/apache/incubator-dubbo/blob/master/LICENSE) file for details.
+