Fix formatting of backend questions (#8014)

src/data/question-groups/backend/backend.md

@@ -1,9 +1,9 @@
 ---
 order: 4
 briefTitle: 'Backend'
-briefDescription: 'Test, rate and improve your Backend knowledge with these questions.'
+briefDescription: 'Test, Rate and Improve your Backend knowledge with these questions.'
 title: '50 Popular Backend Developer Interview Questions and Answers'
-description: 'Test, rate and improve your Backend knowledge with these questions.'
+description: 'Test, Rate and Improve your Backend knowledge with these questions.'
 authorId: 'fernando'
 isNew: false
 date: 2024-05-24
@@ -82,7 +82,7 @@ questions:
     answer: maintainable-code.md
     topics:
       - 'Beginner'
-  - question: Describe how you would implement a full-text search in a database
+  - question: Describe how you would implement a full-text search in a database.
     answer: fulltext-search.md
     topics:
       - 'Intermediate'
@@ -122,11 +122,11 @@ questions:
     answer: gdpr-compliance.md
     topics:
       - 'Intermediate'
-  - question: Explain how you would deal with long-running processes in web requests
+  - question: Explain how you would deal with long-running processes in web requests.
     answer: long-running.md
     topics:
       - 'Intermediate'
-  - question: Discuss the implementation of rate limiting to protect APIs from abuse
+  - question: Discuss the implementation of rate limiting to protect APIs from abuse.
     answer: rate-limiting.md
     topics:
       - 'Intermediate'
@@ -142,7 +142,7 @@ questions:
     answer: api-dependencies.md
     topics:
       - 'Intermediate'
-  - question: Describe the concept of eventual consistency and its implications in backend systems
+  - question: Describe the concept of eventual consistency and its implications in backend systems.
     answer: eventual-consistency.md
     topics:
       - 'Intermediate'
@@ -186,7 +186,7 @@ questions:
     answer: realtime-data-sync.md
     topics:
       - 'Advanced'
-  - question: Discuss the benefits and drawbacks of microservice architectures in backend systems
+  - question: Discuss the benefits and drawbacks of microservice architectures in backend systems.
     answer: benefits-drawbacks-microservices.md
     topics:
       - 'Advanced'
@@ -194,7 +194,7 @@ questions:
     answer: load-testing-api.md
     topics:
       - 'Advanced'
-  - question: Describe how you would implement a server-side cache eviction strategy
+  - question: Describe how you would implement a server-side cache eviction strategy.
     answer: cache-eviction.md
     topics:
       - 'Advanced'
@@ -218,7 +218,7 @@ questions:
     answer: anomaly-detection.md
     topics:
       - 'Advanced'
-  - question: Describe the process of creating a global, high-availability data storage solution for a multinational application
+  - question: Describe the process of creating a global, high-availability data storage solution for a multinational application.
     answer: high-available-storage.md
     topics:
       - 'Advanced'
@@ -230,17 +230,16 @@ Getting ready for a software developer interview is never easy, especially if yo
 
 In this article, we’ll go over 50 popular backend interview questions ordered by experience level.
 
-For each question, we’ll provide some explanations, but feel free to further research each topic in detail, or go to the [Backend Roadmap](/backend) if you’re looking for a place to get started in your learning journey.
+For each question, we’ll provide some explanations, but feel free to further research each topic in detail, or go to the [Backend Roadmap](https://roadmap.sh/backend) if you’re looking for a place to get started in your learning journey.
 
 ## Preparing for your Backend interview
 
 Before we get started, it’s important to remember the following points when getting ready for your backend technical interview:
 
 - Cover the basics of backend development. If you’re going for a web dev role, make sure you understand how client-server communication works. If you’re going for a dev tool development, understand the best practices around CLI development, etc.
-- Practice coding, either by developing [your own mini-projects](/backend/developer-tools) or by using sites such as [LeetCode](https://leetcode.com), [HackerRank](https://hackerrank.com), and others.
+- Practice coding, either by completing [projects](https://roadmap.sh/backend/projects) or by using sites such as [LeetCode](https://leetcode.com), [HackerRank](https://hackerrank.com), and others.
 - Consider reading up on software architecture; even if your role won’t be that of an architect, you’ll show understanding on a higher level by being able to discuss these topics.
-- Make sure you have, at least, a basic understanding of most of the foundational layer of tools and practices for your role, such as version management (i.e. using Git), testing (as in unit testing at least), DevOps (including CI/CD pipeline, etc.), and anything else related to your role and the company.
+- Make sure you have, at least, a basic understanding of most of the foundational layer of tools and practices for your role, such as version management (i.e. using Git), testing (as in unit testing at least), [DevOps](https://roadmap.sh/devops) (including CI/CD pipelines, etc.), and anything else related to your role and the company.
 - On a more general note, remember to read up on the company to be able to show interest and understanding of their business/product and also come prepared with a couple of questions of your own, showing you care about the role and the company.
 
 With that said, let’s now focus on the list of backend interview questions that you may be asked when applying for a backend development role!
-

src/data/question-groups/backend/content/distributed-caching.md

@@ -4,5 +4,3 @@ In this scenario, you have to consider the following points:
   Implement a **data sharding** process to evenly distribute the data amongst all cache servers and make sure it uses a consistent hashing algorithm to minimize cache reorganization when a server joins or leaves the cluster.
 - Add **cache replication** to have redundancy of your data in case of a failure, that way, your distributed cache is fault-tolerant as well.
 - **Cache invalidation** is a must on any caching solution, as your data will become stale if you don’t update it often.
-
-

src/data/question-groups/backend/content/sql-vs-nosql.md

@@ -1,3 +1,3 @@
-[SQL databases](/sql) (or relational databases as they’re also known) rely on a predefined schema (or structure) for their data. Whenever you describe a record, or table inside the database, you do so through its format (name and fields).
+[SQL databases](https://roadmap.sh/sql) (or relational databases as they’re also known) rely on a predefined schema (or structure) for their data. Whenever you describe a record, or table inside the database, you do so through its format (name and fields).
 
-In the case of a NoSQL database, there is no schema, so there is no predefined structure to the data. You usually have collections of records that are not obligated to have the same structure, even if they represent conceptually the same thing.
+In [NoSQL](https://roadmap.sh/mongodb) databases, there is no schema, so there is no predefined structure to the data. You usually have collections of records that are not obligated to have the same structure, even if they represent conceptually the same thing.