Ditto Basics

as an edge sync platform, ditto seamlessly shuttles data from points a to b in peer ‑ to ‑ peer, client server, and hybrid environments with ditto, you get to choose the architecture that best meets your unique goals and use cases this ditto basics guide provides a high level overview of fundamental concepts that, once understood, will empower you to get the most benefits of the ditto platform building resilient apps the ditto platform is a complex ecosystem consisting of many components that together form ditto’s highly available decentralized data management solution ditto shuttles data from points a to b without the need for a centralized authority, such as a central server to validate and merge data changes if data inconsistencies occur as a result of concurrent edits ; as in, simultaneous offline edits made to the same data items stored in different locations, those conflicts eventually merge as a single value the following video narration provides a quick overview of how ditto ensures data delivery from points a to b regardless of challenging network conditions integrating ditto and managing data ditto is an sdk library integrated with your app once integrated, each peer retains a single system database known as a ditto store that operates locally within the end user’s environment; for example, a physical device like an iphone the local ditto store securely stores and processes transactional data as independent copies of the data, referred to as replicas by maintaining multiple replicas of the same data across distributed peers, if one peer experiences connectivity issues or becomes unresponsive, your app remains fault tolerant and optimized, ensuring a consistently smooth end user experience once internet connection is restored or a secure network becomes available, any offline changes automatically sync with the optional cloud deployment, referred to as the big peer , and even back to your centralized server — enterprise cloud, datacenter, legacy database, or business intelligence tool (see /#big peer a powerful component ) small peer your app integrated with ditto a small peer is an abstract term used in ditto to refer to your app logic integrated with the ditto sdk running in the end user environment, such as a web, mobile, desktop, or linux‑enabled server system the defining attributes of small peers include storage, ram, and cpu resources are generally static and unchangeable for example, a small peer could be an apple iphone 13 with a fixed storage capacity of 256 gb form an intelligent peer‑to peer mesh network by automatically connecting with nearby peers through available transport protocols like bluetooth low energy (le) entirely managed by ditto, the mesh network that small peers establish enables the platform’s advanced peer‑to‑peer architectural configuration and seamless offline‑first capabilities for more information, see any of the following docid\ hfwwxtojepjkcxqkp4pvr docid\ byukq4ekkuevjbx feuog platform manual > docid 5oc2w0zdefoy9vu8ma6qd big peer a powerful component the big peer is a cloud database deployment within the decentralized peer‑to‑peer network that is, despite its role as a centralized node in the kubernetes cluster, it seamlessly integrates with the network like any other connected peer, albeit with elevated access permissions as the peer to peer network's cloud database deployment, the big peer is the platform component that enables client‑server and hybrid architectural environments, if you choose the key features of the big peer include handling large amounts of data through horizontal scaling, ensuring continuous uptime operation and availability, fostering data and network security, and automatically managing critical scaling decisions after undergoing rigorous performance testing to confirm its efficiency, scalability, and ability to handle a high volume of transactions, the big peer is proven to handle up to 40,000 transactions per second this includes 25,000 write transactions and 15,000 read transactions for more information, see any of the following platform manual > docid 405tcamz2gnt9e8xitd6m docid\ tqwdcet3fi3m5vgayqlaf docid\ aumh3xrjtkq8r8uog0r x