Skip to content

Commit

Permalink
feat(readme): update readme
Browse files Browse the repository at this point in the history
  • Loading branch information
caiocampoos authored Sep 8, 2024
1 parent b270079 commit b3ed9fb
Showing 1 changed file with 10 additions and 18 deletions.
28 changes: 10 additions & 18 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,26 +1,18 @@
### Mapinguatech Design System
This is one part of my own tech stack for personal projects, this tech stech is composed of:

I maintain my own tech stach for personal projects, the idea is to avoid rewriting every key part of a web project every time
i start something new.
Usually every project will end up using one or many items of this stack:
### Design System
Design system Maintain cohesion of design/ui through my projects and redy to use components to use in any projects. Any new component that is needed will also be added to the design system for tuture use.

- Design system
Maintain cohesion of design/ui through my projects and redy to use components to use in any projects.
Any new component that is needed will also be added to the design system for tuture use.
### Server
Server Basic integration of a server without business rules and processes, mostly sync processing and db integration. It will handle basic auth and observability
out of the box, i am assuming every project will need at least that. If i see the need along the way the improvements will be implemented in the core server if it is not
a business rule, that way i can guarantee it is evolving but not holding complexity based on product, remaining a core implementation for generic use.

- Server
Basic integration of a server without business rules and processes, mostly sync processing and db integration.
It will handle basic auth and observability out of the box, i am assuming every project will need at least that.
If i see the need along the way the improvements will be implemented in the core server if it is not a business rule, that way i can guarantee it
is evolving but not holding complexity based on product, remaining a core implementation for generic use.

- Worker/Consumer

Simple implemention of a worker/consumer that will be used to process assincronous tasks, usually tasks that take more resources and can be deferred to a worker.
It will have basic security and observability implementations out of the box.
It will use rabbitmq as message broker.
Will be improved over time from the same concept of core service.
### Worker/Consumer

Simple implemention of a worker/consumer that will be used to process assincronous tasks, usually tasks that take more resources and can be deferred to a worker.
It will have basic security and observability implementations out of the box. It will use rabbitmq as message broker. Will be improved over time from the same concept of core service.


### Useful Commands for this repo
Expand Down

0 comments on commit b3ed9fb

Please sign in to comment.