-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathProblem.tsx
More file actions
59 lines (56 loc) · 1.91 KB
/
Copy pathProblem.tsx
File metadata and controls
59 lines (56 loc) · 1.91 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
import { Container, Grid, Typography, Paper } from '@mui/material';
const items = [
{
title: 'Repeated boilerplate',
description:
'Every project reimplements retry, auth, validation, and error handling differently.',
},
{
title: 'Unpredictable behavior',
description: 'Request flows vary across services, making debugging and maintenance harder.',
},
{
title: 'Lack of control',
description:
'No unified way to control retries, cancellation, response validation, and request lifecycle.',
},
];
export function Problem() {
return (
<Container maxWidth="lg" sx={{ py: { xs: 2, md: 4 } }}>
<Typography variant="h4" fontWeight={600} gutterBottom>
What problem it solves
</Typography>
<Typography color="text.secondary" sx={{ maxWidth: 720, mb: 4 }}>
In most projects, HTTP clients are rebuilt again and again — with slightly different retry
logic, error handling, response validation, and no visibility into what actually happened.
<br />
<br />
<strong>@dfsync/client</strong> provides a predictable, observable, and reusable request
lifecycle out of the box for service-to-service communication, including safer retries for
non-idempotent operations.
</Typography>
<Grid container spacing={3}>
{items.map(({ title, description }) => (
<Grid size={{ xs: 12, md: 4 }} key={title}>
<Paper
variant="outlined"
sx={{
p: 3,
borderRadius: 3,
height: '100%',
}}
>
<Typography fontWeight={600} gutterBottom>
{title}
</Typography>
<Typography variant="body2" color="text.secondary">
{description}
</Typography>
</Paper>
</Grid>
))}
</Grid>
</Container>
);
}