[Oracle Autonomous JSON] How to configure and using the Oracle API for MongoDB on Oracle Autonomous JSON Database - Part 2

 Hello everyone

In my last post, I presented how you can configure the Oracle Autonomous JSON Database to use the API for MongoDB.

And today, we're going to use the API to connect into MongoDB shell, create a simple collection and use those documents in the ADJ console.

If you want to see the first post, feel free to click here. 

But always remember:

1. This step-by-step worked for me, but it may not work for you.
2. It's a basic and limited environment. The real life will be different, for sure.
3. This post is for study and testing as well, and has no concern for performance and security best practices.

I have a MongoDB Intance in OCI Compute and I'm going to connect MongoSH in my ADJ using the connection string that I created in the first post. My user is named ADMIN:

mongosh -u admin -p XXXZZZ 'mongodb://XXZZZ-IRONMAN.adb.sa-saopaulo-1.oraclecloudapps.com:27017/admin?authMechanism=PLAIN&authSource=$external&ssl=true&retryWrites=false&loadBalanced=true'

I'll create a new collection and a new document using MongoSH. After that I'll create a new document using ADJ console and at the end I'll select this data in the console and MongoSH as well.

This example was adapted from the post "SQL NESTED Clause Instead of JSON_TABLE in Oracle Database 19c" from amazing ORACLE-BASE. 

So, let's get started!!!

1) I'll connect in MongoSH using my connection string:

2) Now, I'll access the ADJ console. Click on the "Database Actions" button and select the option "JSON".

  

3) First, I'll create a new decument in the MongoSH shell.

4) The second document will be created in the ADJ console. For this, click in "New" button in the ADJ console.

Click on the "Create" button and he massage bellow should appear.

And now, I have 2 documents in my collection.

And for read operations, I have two options:

1)  Click on the "Database Actions" button and select the option "SQL".

2) I'll create my SQL queries with the same SQL statements used in relational databases.

Using NESTED and WHERE, for example.

3) Finally, I may read my documents usinf MongoDB statements, for shure!!!

It's really cool, right!!!

In the next post, I'll show you how enabling REST is easy in ADJ.

I hope this post will help you!!!

Regards

Mario

[Oracle Autonomous JSON] How to configure and using the Oracle API for MongoDB on Oracle Autonomous JSON Database - Part 1

Hello all!!!

How are you doing?

Today I'll show how you can create an Autonomous Database JSON instance on OCI Free Tier and how you can connect your MongoDB with this instance using Oracle Database API for MongoDB. 

In Part 2, I'll create new collections in the MongoDB shell and demonstrate how we can use these in the ADJ console using JSON and traditional SQL syntax.

The MongoDB is running on OCI Compute Instance :) 

But always remember:

1) This step-by-step worked for me, but it may not work for you.

2) It's a basic and limited environment. The real life will be different, for sure.

3) This post is for study and testing as well, and has no concern for performance and security best practices.

So, let's get started!!!

1) Create a VCN. I'm not show the step by step for this, but it's really easy. Google helps you!!!

2) Now, I'll create the ADJ for testing. Click on Create Autonomous Database.

This is the most important setup that you need. For access the Oracle Database Actions Launchpad, you must have set "Secure access from allowed IPs and VCNs only" and put our VCN and our IP here. It's mandatory!!!

I'll insert my IP address and click "Add access control rule" to add my VCN, as well!

To finish, click "Create Autonomous Database" and wait!

3) ADJ created, it's time to check access to MongoDB.

For this verification, we need the link for mongosh. Click on "Database actions". 

In the end of the page, click on "Oracle Database API for MongoDB".

Copy the MongoDB connection string URL.

Finally, access the MongoDB server and test the connection.

Oh my god! Error!!!! Why????

The error "Client network socket disconnected before secure TLS connection was established" is easy to solve.

We also need to put the Compute Instance Public and Private IP where we run the MongoDB on "Access control list".

And now, I have succeeded!!!

In the next post, I going to create some collections and load documents into MongoDB console, and I'll work with those tables in the ADJ console using the "Traditional Select Syntax".

It's going to be cool! :) 

I hope this post helps you!

Regards

Mario

[Oracle Autonomous JSON] Create new Instance on OCI Free Tier

Hello all!!!

How are you doing?

Today I'll show how you can create an Autonomous Database JSON instance on OCI Free Tier.

I'll use the instance in future posts about JSON and Oracle.

But always remember:

1) This step-by-step worked for me, but it may not work for you.

2) It's a basic and limited environment. The real life will be different, for sure.

3) This post is for study and testing as well, and has no concern for performance and security best practices.

So, let's get started!!!

1) Select "Oracle Database" in menu

2) Click on "Autonomous JSON Database"

3) Click on "Create Autonomous Database"

4) Select the Compartment - Never use the Root compartment, put other information (Display name, Database name) and password as well.

And now, I'm waiting for the conclusion of the process.

A few minutes later, the Instance is ready for use.

That's it my friend!! Easy!!!

I hope it helps you!

Regards

Mario

[MongoDB] How the replication works in MongoDB? And how to create a Test Environment using Docker-Compose!!!

Hello all

How are you doing?

Today, I'm going to talk about replication in MongoDB and how I can create a Test Environment using Docker-Compose.

If you don't know how to install a docker-compose, click here and here.

And always remember:

1) This step-by-setp worked for me, but it might not work for you.

2) It's a basic install. As we go along, we'll get better and better.

3) This post is just for study and test, and it has no concern for Performance and Security Best Practices.

According to the manual, "The Replica Set in MongoDB is a group of mongod processes that maintain the same data set. Replica sets provide redundancy and high availability and are the basis for all production deployments. Replication provides redundancy and increases data availability. With multiple copies of data on different database servers, replication provides a level of fault tolerance against the loss of a single database server."

It's important understand that the secondaries replicas aren't open to write operation. But we can specify a read preference to send read operations to secondaries, if we want. 

If you want active nodes, you can use Sharding which are a method for distributing data across multiple machines, but this is a conversation to other article.

This is a basic schema about replication in MongoDB.

For learn more about replication, click on image above.

If you understood this, let's get started!!!

For my test, I'll create 3 containers running on AWS EC2 instance using Amazon Linux 2. The data will be persistent because I'll use the "Docker-Managed Volume" for this. 

These automation scripts were based on these original scripts here!!!

1) On compose directory, I'll create an archive call "docker-compose-replicaset.yml". 

Important: It's forbidden to use "TAB" for indentation.

version: '3.9'

services:

  mongodb01:

    container_name: mongodb01

    image: mongo:6

    volumes:

      - shared_database:/data/mongodb

      - /root/compose/scripts/rs-init.sh:/scripts/rs-init.sh

    networks:

      MongoCluster:

        ipv4_address: 172.15.0.11

    ports:

      - 27021:27017

    restart: always

    entrypoint: ["/usr/bin/mongod", "--bind_ip_all", "--replSet", "myRS"]

  mongodb02:

    container_name: mongodb02

    image: mongo:6

    volumes:

      - shared_database:/data/mongodb

    networks:

      MongoCluster:

        ipv4_address: 172.15.0.12

    ports:

      - 27022:27017

    restart: always

    entrypoint: ["/usr/bin/mongod", "--bind_ip_all", "--replSet", "myRS"]

  mongodb03:

    container_name: mongodb03

    image: mongo:6

    volumes:

      - shared_database:/data/mongodb

    networks:

      MongoCluster:

        ipv4_address: 172.15.0.13

    ports:

      - 27023:27017

    restart: always

    entrypoint: [ "/usr/bin/mongod", "--bind_ip_all", "--replSet", "myRS"]

volumes:

  shared_database:

networks:

  MongoCluster:

    driver: bridge

    ipam:

     config:

       - subnet: 172.15.0.0/16

The main information about this script are:

mongodb01 = Name of service

container_name = Container (machine) name

image = Docker image. I'll use the MongoDB official image 

volumes = Persistent volumes that will be shared in all nodes

networks = Network using to the cluster 

ports = Service ports and port range 

entrypoint = Override the default entrypoint. Setting entrypoint both overrides any default entrypoint set on the service’s image with the ENTRYPOINT Dockerfile instruction.

volumes:

  shared_database = Using a "Docker-Managed Volume" for share a Docker-managed volume between containers.

2) Create directory scripts in compose directory.

     mkdir -p /root/compose/scripts

3) Create script "rs-init.sh" in directory scripts

#!/bin/bash

DELAY=25

mongosh <<EOF

var config = {

    "_id": "myRS",

    "version": 1,

    "members": [

        {

            "_id": 1,

            "host": "mongodb01:27017",

            "priority": 2

        },

        {

            "_id": 2,

            "host": "mongodb02:27017",

            "priority": 1

        },

        {

            "_id": 3,

            "host": "mongodb03:27017",

            "priority": 1

        }

    ]

};

rs.initiate(config, { force: true });

EOF

echo "****** Waiting for ${DELAY} seconds for replicaset configuration to be applied ******"

sleep $DELAY

echo "****** Environment ready to use ******"

4) Create the script "startRS.sh" on compose directory.

#!/bin/bash

DELAY=10

## Cleanup older creations

docker-compose --file docker-compose-replicaset.yml down

docker rm -f $(docker ps -a -q)

docker volume rm $(docker volume ls -q)

## Start Docker-compose using my configs

docker-compose --file docker-compose-replicaset.yml up -d

echo "****** Waiting for ${DELAY} seconds for containers to go up ******"

sleep $DELAY

## Start Replica Set just on the first execution. After that, a warning will be displayed.

docker exec mongodb01 /scripts/rs-init.sh

## Check

docker ps

docker exec -it mongodb01 /bin/hostname -i

docker exec -it mongodb02 /bin/hostname -i

docker exec -it mongodb03 /bin/hostname -i

docker exec -it mongodb01 mongosh --eval "rs.status()"

4) Run chmod to to the scripts executable

chmod +x starRS.sh

chmod +x scripts/rs-init.sh

If you want to download these scripts, click here.

Finally, we just run the startRS.sh

And now, if you want test the replica set, you can use this:

On Primary (mongodb01):

docker exec -it mongo01 mongosh

rs.stepDown()

On Secondary (mongodb02):

docker exec -it mongo02 mongosh

I used the sources bellow for this blog: 

https://blog.devgenius.io/how-to-deploy-a-mongodb-replicaset-using-docker-compose-a538100db471

https://docs.docker.com/compose/compose-file/

https://www.mongodb.com/compatibility/deploying-a-mongodb-cluster-with-docker

https://docker-unleashed.readthedocs.io/aula2.html

https://yadax.com.br/category/mongodb/

That's all folks!!!

I hope that this blog helps you!!!

Regards

Mario

[Mongo DB] Introduction to the Document Model

Hello all

One more step on Mongo DB University.

Today, I'm learning about MongoDB and the Document Model.

The main points of this module are: 

Overall, we can say that Mongo DB:

    - It's a General-Purpose Document Database.

    - By default, Mongo DB supports a flexible schema model and a polymorphic data. 

    - This allows us to store documents with different structures in the same collection.

The main advantages to use Mongo DB: 

    1) Documents offer a flexible and developer-friendly way to work with data.

    2) Easier and faster to plan how application data will correspond to data store in the database.

    3) Modal data of any shape or structure.

    4) Documents can model everything:

            Key-values pairs

    Text

    Geospatial indexes

    Time series

    Graph data

    and more

    5) Use one format for any application.

    6) Easy connect - Provide drivers in all major programming languages.

Basically, you can use Mongo DB in any application:

    E-commerce

    Content management

    IoT and time series data

    Trading and payments

    Gaming

    Mobile Apps

    Real-time analytics and AI

Your main features are:

    Scalability

    Resilience

    Speed of development

    High levels of data privacy

    Security

And finally, we have 3 Key term:

    Document - The basic unit of data on Mongo DB.

    

    Collection - A group of those documents. Documents in a collection are tipically similar they don't have the exact same structure, because Mongo DB has a flexible schema model.

    Database - A container for our collections. 

The Document model.

We can say many things about The Document Model, but this is the summary:

    - On Mongo DB, data is organized into documents, collections, and databases.

    - Mongo DB stores data in structures known as documents

    - Mongo DB structures data in documents, which are similar to JSON Objects

    - Documents are stored in BSON, which supports a large range of data types, including all JSON data types, dates, numbers, and ObjectIds.

    - Mongo DB displayed the data documents in JSON format, but they're stored in the database in a format called BSON (Binary JSON).

    - BSON is an extension of JSON and providing additional features 

    - BSON add support for additional data types unavailable in Standard JSON 

    - Every document requires an "_id" field, which acts as a primary key. 

    - The "_id" is a required field in every MongoDB document, but it's not a data type. If an inserted document does not include an "_id" field, MongoDB will automatically create the "_id" field and populate it with a value of type ObjectId.

    - Documents can contain different fields and fields may contains different data types.

    - If you want to have more control over the structure and content, we can add optional schema validation rules to set constraints on the structure of documents. 

Some Datatypes that you have on Mongo DB:

    All the JSON datatypes

        String

Object

Array

Boolean

Null

Dates

Numbers

ObjectIDs - It's a special data type used in Mongo DB to create unique identified.

    If you want moder information, click here.

Finally, an example to the syntax for a MongoDB document:

Syntax:

{

"key": value,

"key": value,

"key": value

}

Example:

    db.createCollection("blog") 

    { 

     "codigo": 2, 

     "trilogy": "Harry Potter", 

     "sequence": "Harry Potter and the Chamber of Secrets", 

     "year": "2002",

     "points": ["The first movie of trilogy", "I watched the movie at the cinema"]

    }

So that's it for today, folks.

I hope this helps you!

Regards

Mario

[Mongo DB] - Basic update and delete operations (or "U" & "D" from CRUD)

Hello all

In the last post (here), I have talked about read and list operations, or the "R" from CRUD.

Today, I'm going to talk about update and delete operations in Mongo DB, the "U" and the "D" in CRUD. 

But remember, I'm talking about basic operations. As we know, the Mongo DB world is much bigger than this post.  

Let's get started!!!

The references are here and here.

We started with update operation.

We often use the operator "set" to execute the update.

-- Update a single data where codigo=14

db.movies.updateOne({ codigo: 14 },{ $set: { year: "2020" } })

-- Update using operator - We are updating the year on documents where codigo >= 97

db.movies.updateMany( { codigo: { $gte: 97 } } ,{ $set: { year: 2025 } })

-- Update the document where codigo=97, using the exclusive operator to increment the original value

db.movies.updateOne( { codigo: 97 } , { $inc: { codigo: -10 } } )

-- We can create a new "column" call "watched" and update all documents on collection with true, as well. The famous "Update without where" 🥶. 

db.movies.updateMany({ }, { $set: { watched: true } })

Ok, the basic update operations are easy!!!

And, what about the delete operations? 

They're very easy too!!!

-- Delete one document where codigo=98

db.movies.deleteOne ( { codigo: 98 } )

-- Delete many documents where trilogy = "Procurando Nemo"

db.movies.deleteMany({  trilogy: 'Procurando Nemo' })

Owwwwwww yes, it's easier than update, right...

With this post, I'm finished the posts with CRUD operations on Mongo DB.

I hope that it helps you to start on with Mongo DB.

The next post will talk about Index. 

See you!!!

Regards

Mario