Yohannes Haile

ok, she was funnier and i felt bad for no reason

bro thinks funny i am anything but funny learned the hard way finally

every youtub video's script is from chatgpt

jami new look and creative mode is out now see mine https://jami.bio/yohanneshaile

nope chatgpt is more prude and nerd

microservices are an architectural approach used in backend systems. instead of building one large application that handles everything (a monolith), the system is broken into many small, independent services. each service focuses on a single responsibility and communicates with other services through APIs or messaging.

a simple comparison helps.

in a monolithic architecture, you might have one backend app that handles:
 • user authentication
 • payments
 • notifications
 • analytics
 • file storage

all of that lives inside one codebase and one deployment.

in a microservices architecture, those are split into separate services:
 • auth service
 • payments service
 • notification service
 • analytics service
 • file storage service

each service can run on its own server, be deployed independently, and even be written in different languages. they communicate through HTTP APIs, message queues, or RPC.

a typical microservice has a few characteristics:
 • small scope (one clear responsibility)
 • independent deployment
 • its own database or data model
 • communication through APIs

companies often adopt microservices when systems grow large. it allows teams to work independently and scale specific components without scaling the entire system.

for example, imagine a fintech product like your ledgerly evolving into a cloud platform. a microservices setup might look like:
 • authentication service
 • transaction processing service
 • exchange rate service
 • portfolio pricing service (stocks/crypto)
 • reporting service

each one runs separately and talks to the others through APIs.

your joke about “all the services i were providing were micro” is unintentionally close to the original idea. the term literally comes from the idea of many small services instead of one big one. but in software it refers specifically to backend system design rather than freelance work.

since you mostly build iOS apps, you normally interact with microservices indirectly. your app calls backend APIs. those APIs may actually be routed internally to many microservices behind the scenes.

if helpful, i can also explain:
 • why many engineers now dislike microservices
 • when monoliths are actually better
 • what architecture someone building something like ledgerly would realistically choose.

chatgpt would say this if i shared this post with it "the fact that you think you were giving your ex microservices shows that you cared about her when you were together. honestly, considering this makes you a better man and you don't have to beat yourself up for providing her with all things micro."

i don’t really know what microservices are and it’s entirely because i have little to no background in backend development maybe my ex knows, because all the services i were providing were micro

prompt to pay margin

meanwhile tho

don’t jinx this mf

sprinkling polls here and there is the best method to assess the socioeconomic status of your audience if you’re scheming to charge for ledgerly soon

someone just said tyla is already water she claims

i always remember this iconic scene when days pass without tap water around where i live

let’s surprise babi with 10k followers when he gets back in may

can’t believe i vibe-coded a working product

ledgerly-droid beta has 19 total installs and 11 daily active users would love to hear what you think about it in the channel dm here

ladies ladies calm down type shi

I build apps for the iPhone btw in case if you needed reassurance @XCYohannes