add backend docs

[jeremy-babylonlabs]

No description provided.

[jrwbabylonlab]

If I were a reader of this documentation trying to set up the Babylon backend system, I would find it very confusing.

For example, the section is titled deployment-overview, but it doesn’t actually explain how to deploy the backend services.

I understand that this is a copy of the Phase 1 documentation from Babylon Docs, but let’s take some time to improve it in this PR.

What I have in mind:

1. Overview of the Babylon Backend Services

• This should include the current deployment-overview content, specifically the diagram and descriptions of each component.
• We should clarify that users do not necessarily need to host certain services, such as the unbonding pipeline and covenant signer. Right now, it’s unclear which components are required to be hosted.

2. Prerequisites (each should have detailed setup instructions, which can be completed in a separate PR in collaboration with DevOps)

• MongoDB
• RabbitMQ
• Babylon Node
• Bitcoin Node
• Clearly state that Phase 1 services should be turned off if the user had them running.
• DB Snapshot: This refers to the database snapshot taken by DevOps to speed up syncing. Check with DevOps for details—there should be a dedicated page for this.

3. Hosting the Services

• This section should provide instructions on how to host each individual service or guide users on using a single script (if available) to deploy all services at once.
• The current services directory (which contains setup instructions for each service) is fine, but there are areas for improvement:
  • Provide a Docker option: Consult with DevOps on this. Since we have a public Docker Hub, hosting services via Docker is significantly easier. A docker-compose setup would allow users to start all services with a single command in the future.
  • Enforce service startup order: The order should be strictly followed—Indexer first, followed by Expiry Checker, then API.
  • Health check endpoints: Each service already has a health check endpoint. Instead of instructing users to check logs manually, we should guide them to use these endpoints to verify if a service is running.
  • Resource requirements: The Indexer and Expiry Checker require a minimum of 8GB RAM. Let’s document this clearly.

Thoughts? @kirugan @vitsalis @jeremy-babylonlabs

[kirugan]

LGTM