Skip to content

Commit d54493e

Browse files
committed
Beef up "why Mapepire?" docs
1 parent f8c3bb8 commit d54493e

File tree

1 file changed

+25
-2
lines changed

1 file changed

+25
-2
lines changed

src/content/docs/guides/why.md

Lines changed: 25 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,33 @@
11
---
22
title: Why Mapepire?
3-
description: A guide into why Mapepire
3+
description: The benefits of Mapepire
44
sidebar:
55
order: 0
66
---
77

8+
# Why Mapepire?
9+
810
Mapepire (pronounced 'mapəpɪə' or 'MAH-pup-ee') is a database access layer written on top of secure web sockets. It was built to make developing modern applications in .NET Core, Node.js, PHP, and the likes, easier when using Db2 for i.
911

10-
Mapepire brings an unprecedented level of simplicity for Db2 access. All communication with the server is done through a single port, and there is no need to install external drivers or other native software on the client machine. This makes it an ideal choice for deployment of cloud-native applications, running seamlessly in [Red Hat UBI](https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image) deployments, [Alpine Linux](https://alpinelinux.org/) containers, and the magnitude of cloud services available (like IBM Cloud, Vercel, AWS, or Azure).
12+
The core tenets of Mapepire's design include:
13+
- A consistent client SDK across languages
14+
- Minimal dependencies
15+
- No native dependencies (for instance, drivers) needed on the client machine
16+
- Communication to the server is done through a single port
17+
- Data is always encrypted
18+
19+
Mapepire an ideal choice for deployment of cloud-native applications, running seamlessly in [Red Hat UBI](https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image) deployments, [Alpine Linux](https://alpinelinux.org/) containers, and the magnitude of cloud services available (like IBM Cloud, [IBM WatsonX.ai](http://WatsonX.ai), Vercel, AWS, or Azure).
20+
21+
Simply put: Mapepire clients can be deployed anywhere!
22+
23+
# Mapepire vs. JDBC and ODBC
24+
25+
| | JDBC | ODBC | Mapepire |
26+
| ---------------------------------------------------------- | :--: | :--: | :------: |
27+
| Needs only a single port | | ||
28+
| Data is always encrypted | | ||
29+
| Manageable via system exit points ||||
30+
| Enhanced CCSID support || ||
31+
| Runs in [WatsonX.ai](http://WatsonX.ai) Jupyter notebooks | | ||
32+
| Runs in lightweight containers (for instance Alpine Linux) || ||
33+
| Directly supports multiple client languages | | ||

0 commit comments

Comments
 (0)