Skip to content

Commit f12e066

Browse files
authored
Update TECHNOLOGY.md
BaseX removed Signed-off-by: Sander Jansen <[email protected]>
1 parent 0b9609d commit f12e066

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

TECHNOLOGY.md

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -32,22 +32,13 @@ Microservices are deployed as Linux based Docker container. Advantages of deploy
3232

3333

3434
## Database - BaseX
35-
For the database BaseX](https://basex.org/) is chosen on following arguments:
35+
For the database PostgreSQL is chosen on following arguments:
3636

3737
**Pros**
38-
- Native XML database
39-
- Fully Open Source
40-
- BSD license
41-
- Easy to setup using available Docker image
42-
- Cross-platform available
43-
- Active community
44-
- Multiple API's, like REST(ful) and HTTP
45-
- [ACID guarantees](https://docs.basex.org/wiki/Transaction_Management)
46-
- Many [usage examples](https://docs.basex.org/wiki/Clients) available in different programming languages
38+
- Flexible and supported by many cloud providers
4739

4840
**Cons**
49-
- No clear use cases using BaseX
50-
- Versioning is not out-of-the-box available. Need to use a second database to create 'versioning', which creates an archive database and a current database. And by using RESTXQ is relatively easy to create a versioning mechanism. BaseX gave [SirixDB](https://sirix.io/) as a good alternative in case we want a NoSQL database with versioning mechanism.
41+
- Not a native XML database
5142

5243
## XML Processing
5344
### XML Validation

0 commit comments

Comments
 (0)