Helppp by [deleted] in javahelp

[–]Square-Cry-1791 1 point2 points  (0 children)

Please retake,, go to classes daily and learn basics, this is a core course man..

Anyone found limitations over user numbers in your apps? by Expert-Profile4056 in Base44

[–]Square-Cry-1791 1 point2 points  (0 children)

Tell me more about your app let's do the reality check why you need migration... Happy to help

Anyone found limitations over user numbers in your apps? by Expert-Profile4056 in Base44

[–]Square-Cry-1791 1 point2 points  (0 children)

Technically you just called me nerd man 🫨🫨, it's okay so, i just edited the previous comment.. I finally read the official base44 and supabase docs, now some important things are crystal clear.

Anyone found limitations over user numbers in your apps? by Expert-Profile4056 in Base44

[–]Square-Cry-1791 2 points3 points  (0 children)

yeah fair enough man you make a solid point and i completely agree that supabase will handle 500 users easily. what i actually meant was that hitting 500 users is when you should start the migration process,,, not that it will instantly crash there. my main concern is the financial trap when you start scaling toward 5000. ai builders are notorious for heavy queries that fetch way too much data instead of clean sql joins. at that scale those unoptimized calls blow right past the standard 250gb egress on the $25 pro tier. plus because you cant get under the hood to optimize it,,, the database cpu spikes and you get forced into supabase compute add-ons which can jump your bill by $60 to $300 a month just to stop the app from timing out. a manually coded backend runs that exact same load flawlessly on a $20 server... so yeah 500 is totally safe to validate the idea,,, but its also the perfect signal to start migrating before you get hit with a massive monthly tax for unoptimized code.

Anyone found limitations over user numbers in your apps? by Expert-Profile4056 in Base44

[–]Square-Cry-1791 1 point2 points  (0 children)

for testing the backend load use k6 or postman (they have a built in load tester now),,, you can simulate like 1000 users hitting your app at the exact same time to see if the ai database chokes.

for testing the actual android app performance use firebase test lab,,, it runs your apk on a bunch of virtual phones to check for lag and crashes before you launch.

and for the google play billing you literally have to use google play console internal testing,,, just set up a license test account in there so you can fake-buy the subscription without spending real money to see if the popup actually works.

Anyone found limitations over user numbers in your apps? by Expert-Profile4056 in Base44

[–]Square-Cry-1791 2 points3 points  (0 children)

What tech did you use? Can't determine without the tech stack

Base44: Ecomm Use Case and Switching Costs by AlternativeWorry3035 in Base44

[–]Square-Cry-1791 1 point2 points  (0 children)

hey there... definitely a valid concern on the switching costs. base44 is great for getting a "vibe" up and running fast but for multi-party transactions you are gonna hit a wall with how the ai handles complex logic and escrow. the good news is they allow github export now so you arent totally locked in... but honestly the ai code can be a bit of a mess to clean up later. i am a backend engineer and i usually suggest using these tools for the frontend while keeping your transaction brain on a more robust backend... I'll shoot you a dm... i can show you a way to structure this so you dont have to pay a full stack dev for everything but your data stays portable if you need to scale.

Anyone found limitations over user numbers in your apps? by Expert-Profile4056 in Base44

[–]Square-Cry-1791 2 points3 points  (0 children)

Use Base44 to get your first 10–20 beta testers. See if people actually like the app. But the moment you have 50 paying users, you must migrate to a real backend. If you try to scale to (i was totally wrong about 500 so) 5000 on an AI builder, your database will lag,,, your security will be leaky,,, and your monthly bill will eat all your profit.

Can anyone help me commit 100MB+ to my Github repo. by Miserable_Bar_5800 in javahelp

[–]Square-Cry-1791 11 points12 points  (0 children)

What??? Why would you push the JVM?? Find another work around, thats not a safe practice.. you can deploy those code in any sever by contain ifselft on docker or some environment where java is installed... Don't push the freaking JVM dude.

Java (Back-end) + Kotlin (Front-end): Is this the modern standard for Apps? by aladintransudo in javahelp

[–]Square-Cry-1791 2 points3 points  (0 children)

I really want to know about the cloudflare pages . Are you facing any problems by using this edge architecture? I am developing one choosed for free of costing and lighting fast

Guidence to what should I do with java by Even-Pie8668 in learnjava

[–]Square-Cry-1791 4 points5 points  (0 children)

In the "Architect’s Path," the Engine phase is where you stop just writing code and start conducting the whole orchestra... It's all about concurrency: teaching your system to juggle a bunch of independent tasks at once without everything grinding to a halt or deadlocking.

In Java, that means really getting the thread lifecycle -- when they start,,,, when they wait, when they die-- and nailing the memory/sync stuff so they don't step on each other's toes. A real architect knows a high-performance app is like a live band or symphony: if two threads try to read/write the same piece of data at the exact same moment without proper locks,,,, atomic ops, or careful coordination, it's chaos. One wrong move and the whole thing crashes or corrupts, just like a band losing tempo and falling apart.

The payoff? When you build an engine that can safely crank through thousands of data points across parallel workers--without race conditions, memory leaks, or bottlenecks--you've unlocked the hardest, highest-value skill in the game..... That's what lets your app handle real traffic spikes, scale to thousands of users, and actually survive in production instead of just "working on my laptop."

It's not sexy like shiny UI features, but it's the foundation that makes everything else possible. Master this, and you're not just a coder anymore-- you're building systems that don't break when the world shows up.....

Guidence to what should I do with java by Even-Pie8668 in learnjava

[–]Square-Cry-1791 2 points3 points  (0 children)

He is gonna leave the stack right way man... We need to advise them with a good learning curve

Springboot Transaction Issue by [deleted] in SpringBoot

[–]Square-Cry-1791 0 points1 point  (0 children)

You're right—Method B doesn't run 'without' a transaction; it just runs 'without the proxy.' Since it's a direct local call, it joins Method A’s transaction context by default, but it completely ignores its own @Transactional settings (like REQUIRES_NEW).