Repositories Explained: A Simple Analogy

M Ilham — Thu, 07 Nov 2024 03:43:22 +0000

Analogy

Imagine you're preparing a complex meal. You have a variety of raw ingredients: vegetables, meat, spices, and so on. To maintain organization and efficiency, you'd group these ingredients into separate containers. Each container could be likened to a small repository in the context of your kitchen.

When you start cooking, you'll take ingredients from these containers and process them according to the recipe. This process is similar to how we take code from various repositories and combine them to build an application.

Repositories in Programming: More Than Just Storage

In programming, a repository is far more than just a storage place. It's the heart of version control systems like Git, allowing us to:

Track changes: Every change we make to the code is recorded in the repository. This allows us to view the history of changes, compare different versions, and even revert the code to a previous version if errors occur.
Collaborate: Multiple developers can work simultaneously on the same project using the same repository. Features like branching allow each developer to work on different parts of the code without interfering with the work of others.
Create versions: Each significant change to the code can be labeled as a version. This allows us to release different versions of an application with different features and improvements.

Monorepo vs Multirepo

As far as I know, the repo concept comes in two forms: Multi-repo and Monorepo. Both concepts have advantages and disadvantages. Not all problems can be solved using the same concept. Some can be solved with one concept, while others with the other.

Common problems encountered include:

Lack of a solid pattern
Difficulty in maintenance
Duplicate dependencies
Lack of standardization
Rewriting the same code
etc.

So, which concept is most suitable for building a system? This depends on the available resources and our needs. As programmers, we must also be able to determine which concept to use before building a system. Because if the initial step is wrong, it will only make things more difficult for us later.

Let's delve deeper into the benefits of both multi-repo and monorepo approaches. Understanding these concepts will enhance our development strategy significantly.

Happy Coding and don’t forget to make it Coffee😍😎

The Backend Brew: A Developer’s Daily Dose

M Ilham — Mon, 28 Oct 2024 04:43:24 +0000

Hola!

Welcome to my first post. I’m a Backend Engineer. As a backend engineer, I often find myself drawn to the meticulous nature of crafting software. Much like a skilled barista meticulously prepares each cup of coffee, I take pride in crafting clean, efficient, and elegant code. From the initial spark of an idea to the final deployment, I find immense satisfaction in the entire development process.

I’m constantly exploring the ever-evolving landscape of backend technologies, from the robust foundations of Node.js and the power of TypeScript to innovative frameworks like NestJS. I’m passionate about writing code that not only functions flawlessly but also delights users with its performance and reliability.

In this blog, I’ll share my experiences, insights, and lessons learned. We’ll delve into topics ranging from architectural patterns to performance optimization, from database design to API development. Together, we’ll unravel the complexities of backend development, one function at a time.

Thankyouu!! Happy Coding and don’t forget to make it Coffee😍😎

DEV Community: M Ilham

Repositories Explained: A Simple Analogy

Analogy

Repositories in Programming: More Than Just Storage

Monorepo vs Multirepo

The Backend Brew: A Developer’s Daily Dose