This document provides an introduction and overview of FATDB, an integrated platform for building scalable web applications. It discusses the challenges of building web-scale applications and outlines the essential components needed, including data storage, business logic hosting, and management tools. Traditional monolithic and newer microservices architectures are described as having shortcomings around scalability, latency, and integration costs. The FATDB architecture is presented as a "Mission Oriented Architecture" that offers high scalability, flexibility, and synergy across components on an integrated platform to address these issues. Key features of the FATDB platform are also summarized.

1. INTRO TO FATDB

2. AGENDA
• Challenges of building a web scale application
• Essential ingredients of any web scale application
• Shortcomings of traditional and new approaches and the
real cost of “glue”
• Mission Oriented Architecture and how an integrated platform
can offer a solution
• Wrap-up and questions

3. AN ECOMMERCE SITE

4. THE ESSENTIAL INGREDIENTS
• Store, retrieve, cache, and query object data
• Store, retrieve, and query file data
• Host synchronous business logic
• Host asynchronous batch job business logic
• High performance, scalable, consistent,
and fault tolerant plumbing
• Comprehensive management tooling
• Full SQL integration
• Portable
• Easy to use

5. AN OLD ARCHITECTURE
3-Tier Monoliths and Beefy Hardware
Typically:
• Rigid and Brittle
• Hard to Scale
• High Latency and Bottlenecks
• High Hardware and Maintenance Costs
• Low learning curve
PRESENTATION
LOGIC
Relational DB

6. THE PROBLEM

7. A MORE MODERN ARCHITECTURE
A-La-Carte SOA with Costly Glue
Typically:
•
•
•
•
•
•
•
•
•
•
More Scalable & Flexible
Lower Upfront Costs
Low Synergy
Still Hard to Scale
Still High Latency
Impedance Mismatches
High Integration Costs
Long Learning Curve
High Maintenance Costs
PaaS Better, but Lock-In
PRESENTATION
SERVICE 1
SERVICE 2
NoSQL
Message Q

8. What is NoSQL? (Not Only SQL)
NoSQL Characteristics:
• Runs on many commodity grade machines
• Divide and conquer mentality
NoSQL Strengths:
• Flexibility with evolving / complicated data
• Quicker to market
• Scale, Performance, Reliability
SQL Characteristics:
• Runs on a single powerful machine
• Centralized authority
SQL Strengths:
• Reporting and BI
• Transactional data and ACID
• Trusted technology
= HYBRID / POLYGLOT ARCHITECTURES

10. THE FATDB ARCHITECTURE
Mission Oriented Architecture (MOA) on an Integrated Platform
Typically:
•
•
•
•
•
•
High Scalability
High Flexibility
High Synergy
Low Latency
Low Impedance
Low Integration Costs
GROUP 1
CONSUMERS
• Short Learning Curve
• Low Maintenance Costs
• Portable
MISSION = BUSINESS
LOGIC + RELATED DATA
MISSION = TEMPLATE
FOR EVERY SERVER
PRESENTATION
GROUP 2
PRODUCTS
GROUP 3
ORDERS

11. THE FATDB PLATFORM
SQL
SERVER
NoSQL
FILES
WORK
QUEUE
MAP
REDUCE
MANAGEMENT
STUDIO
CACHE
APPS
+ .NET + Visual Studio + LINQ

13. SQL SERVER + FATDB
FatDB Server Cluster
SQL Server
Invoice
Invoice
Invoice
024
175
832
Invoice
Invoice
Invoice
936
492
751
Invoice
Invoice
Invoice
595
037
275
SQL Write Back
Invoice
Invoice
Invoice
275
Invoice
037
Invoice
936
Invoice
275
Invoice
037
Invoice
936
Invoice
275
037
936
One button push
No need to “change
religion”
Take SQL Server into
the 21st Century
Invoice
Invoice
Invoice
832
Invoice
492
Invoice
024
Invoice
832
Invoice
492
Invoice
024
Invoice
832
492
024
Invoice
Invoice
Invoice
751
Invoice
175
Invoice
595
Invoice
751
Invoice
175
Invoice
595
Invoice
751
175
595
DISTRIBUTED LINQ QUERY
Invoice
751
1.
2.
3.
4.
Automatically Populate FatDB cluster/cloud
Automatic FatDB mirroring for fault tolerance
LINQ as common query mechanism
SQL Server write back for easy synch of data

14. THANK YOU
Justin Weiler, CTO
justin@fatcloud.com
@fatcloudllc