pleoxy

If you rent a cloud vps as an ingress you can run an overlay network and your actual hosted services can literally be anywhere. See nebula, netbird, etc. You can also ssh forward, but that doesn't scale well past a handful of services and is a bit fragile.

For new small systems I suggest you start with a cloud VPS. If traffic is low, cost of downtime is low, and system requirements are high then a cheap mini PC ($150) at the home or office can keep your bill microscopic. If your app server and database are small then you can just throw them on the VPS too.

I run light traffic stuff at home in a closet so it doesn't occupy more costly cloud RAM. Production ready saas offerings I'm trying to sell right now are all in the cloud. Hosting all my stuff in the cloud would cost me hundreds per month. My home SLA is fine for the extras. I don't need colocation at this time, but I have spoken with data centers to understand my upgrade path.

You can run a live backup server at a second location and have pretty good redundancy should the primary lose power or connectivity.

When system requirements elevate (SLA, security, etc) you probably want to move into a data center for better physical security, reliable power and network. Bigger VPS is fine if it is big enough. Can also do a colocation if you don't want to rent, and you contract directly with a data center. I wouldn't look at colocation until your actual hosting needs exceed at least $100/mo and you're ready for a year long commitment.

The weight check is the worst. Most stores I go to have it disabled and it makes the process go smoother.

Not perfect though, it occasionally flags me for some kind of miss scan and I have to wait for an employee to clear it.

Most of them are chagrined at delaying my checkout. I try not to be rude, but I often want to get on with my day.

More recently they don't give us bags anymore, and it seems like a lot of the theft detection has just gone out the window because of the current environmental push that's got all the processes messed up and need to be re calibrated.

So far I just don't remember to bring my own bags and if I have a smaller number of items I just grab the gun and scan them all in the cart because it is a hassle to pull them out and put them all back. I've never been flagged when using the gun.

That part of true. Using EC2 at AWS now and it's much more expensive than vultr, Hetzner, or akamai cloud.

Shove your state into the database. Done.

Ingress that handles SSL. nginx, or caddy. Then stand up your app server behind that on the same VM. Database can be on the same or different VM.

I try to not use anything else if I can avoid it on a new project.

Ingress gives you the ability to load balance and is threaded and will scale with network transfer and cpu. Database should scale with a bump in VM specs as well, CPU and disk IOPS.

If you keep your app server stateless you can simply multiply it for the number of copies you need for your load.

Systemd can keep your app server running, it you docker it up and use that

You get portability. Which the functions do not provide. Open source solutions have a longer career utility than proprietary offerings. I remember when NetWare certs were all the rage. Useless now. I remember msce. But if you learned open tools 35 years ago instead... You get the picture.

You can scale from 1 thread 512MB RAM, to 500 threads and 12TB of RAM (off the shelf). Which is good enough for almost everyone who isn't planet scale.

Auto scaling also comes with auto billing. Oops, your accidental infinite loop spawning functions has bankrupted your company. You don't have that risk starting with a VPS.

It's not that hard. Particularly for simple deployments, which a startup should have or they are doing it wrong.

> Seems all these shops starting out with MongoDB or the like always need to do a huge complicated migration

First thing to note, I couldn't find any reasoning for the change in the original post. This makes the speculating on it rather pointless, but clearly you are able to fill in the details quite easily somehow.

As a counter point. Last four businesses I've worked at all ran on MongoDB. More happenstance than something I've looked for.

They are all relatively small businesses and all ran fine, the biggest was ingesting 1-10GB/day of new data from their IOT fleet.

So this perspective that everything mongo is fundamentally broken and plain bad is pretty foreign to my real world experience.

These shops all liked what they were doing and there was zero talk of scaling issues or changing out the database.

Living in a home without clutter helps you deal with them because there are fewer places for them to hide. But this will not prevent spread or occupation by them.

Steaming is an effective treatment but only reasonable if there is no clutter and minimal furniture.

Stop.

We don't talk about Bruno.

/S

Sorry, couldn't resist. :)

Agreed, burns so much time messing around with arm and the limited IO suite.

The Dell wyse 5070 idles close to 3-5 watts. A bit more than the pi, but pretty close. It's older now, can be picked up cheaper than a pi off eBay. DDR 4, sata m.2, on board emmc flash. M.2 a-key for WiFi. Max 16GB ram.

When you throw in m.2, lots of ram, all that IO eats power. So the minimum idle power creeps up. Arm boards too.

> AWS has some complicated features that they don't really explain well.

Yeah... Complicated...

What do you do for disk IOPS? Seems like they make you sip through a straw unless you pay them big bucks.

Dedicated vCPU requires a "enable dedicated vCPU" service that is $2/hr (per region). It starts billing you as soon as you enable a dedicated vCPU. I had no idea this existed till I saw the charges.

Max IOPS without paying for provisioned IOPS is 3000 (gp3 stock setting). Much lower than other providers and will cap your database performance. That's combined too, 1500 read and 1500 write. Throughput is 125mb/s.

Hetzner gives you 45k if memory serves, vultr gives you a ton, akamai cloud gives you at least 40k and some instances give you 125k. With throughput in the >3GB/s range.

Provisioned IOPS cost thousands per month to reach these levels via io2 volume. Io2 is capped at 45k if memory serves unless you have a bare metal instance. Which is a whole new pricing tier I didn't investigate.

I believe it is cheaper per IOP to go wide with gp3, complete with additional compute, than to provision io2. Which really kills the whole "go tall not wide" architecture strategy.

Big price bump with dedicated vCPU encourages wide rather than tall also. You can buy a ton of compute for that $2/hr fee.

Moral of the story. Don't try to go tall on Amazon.

> similarly-specced EC2 will easily be 10x that cost.

I actually tried this, it's closer to 200-300x. The number of premium add on fees that appear as you build a higher performing EC2 server is just stupid.

It's not so bad if you scale out horizontally instead of vertically. But that complicates the architecture when other providers don't charge crazy pricing for vertical scaling.

Can't carry much in a Bugatti.

It's a real problem if you build on a VPS as your base. I was asked to prep such a system for scale on AWS and choked on the pricing. So we settled for what they offer at reasonable pricing and if further growth is needed, will need to hit eject on AWS and just go elsewhere.

I recommend starting elsewhere and save the migration of you just use EC2.

Most places will let you scale a VPS quite well and there is a logical handoff to your own hardware where you can scale to a system with 512 vCPU and TBs of ram for less than Amazon is charging for step two.

Not sure about arm, different ISA is a pain.

But the base configuration, for the money, is pretty sad compared to what you get else where. Scaling up is horrendously expensive compared to other providers.

Why would you bother with AWS for this I don't even know. There is no draw to AWS if you are only using EC2. You couple your architecture to their specialized services and go all in and eat the platform risk, and long term cost.

Or... don't even bother with AWS. It makes no sense to use just EC2.

Which takes then off the list of providers you can do this with. They could have reasonable prices but they don't.

You couple to AWS with your whole system architecture or you stay away.

Simple, sure, but AWS still charges insane rates.

I can get 60k IOPS on a nanode at $5/mo rate. You actually get a random amount between 20k-60k depending on the type of machine they provision your nanode on.

You want 60k IOPS on AWS? Be prepared to pay like 4-5k/mo. Want multiple systems with it so you can cluster a reasonably performance database? Pay for each and you need to special request the ability to go past 100k IOPS in a region.

Want the privilege of a dedicated vCPU? It's $1500/mo per region just to turn on the feature.

I tried to use AWS just as you mention here and the cost was 100-1000x what it would cost me at akamai cloud or Hetzner. All these fees I was unfamiliar with popped out and the cost was crazy high.

The system I tried to provision was functionally similar to the bottom end dedicated akamai cloud offering and it was going to cost 15-20k/mo instead of $72. Over 200x. And that was just the hourly provisioned rate, not including egress and other bits...

> You can also find plenty people online saying vaccines include 5G microchips, the british royal family are lizard people, the world is flat, and that fossils are a ruse to shift the world's attention away from the existence of falling angels.

Straw man...

So you can't find any truth online because someone has told a bad fish tale somewhere?

So you can just lump anything you don't like into a crap bucket and stop thinking. Nuance, evidences, reason and logic are all just irrelevant because, well, there is this giant crap bucket!!

Back on topic...

Go to any front line medical personnel. Nurses, doctors, doesn't matter. Tell them you know someone who claims to have been vaccine injured by the COVID vaccines and is worried about the booster and ask them what they think.

How many encourage the person to report their condition and get it investigated?

How many dismiss the concern because vaccines are safe?

If they were interested in truth and safety, potential side effects would be treated with concern and care. To at least look at it, acknowledge the possibility. You know, get answers to questions that every researcher or scientist should want.

Or... If they are more interested in the narrative, it will look more like the later dismissal. No questions allowed.

It's an exercise anyone can do. And it will tell you quite plainly if we are getting honest reporting on potential issues from the vaccines.

Because... You can't find what you filter out of your data set.

> No. There is no evidence that people are at an increased risk of cardiac arrest in the days or weeks following the Covid-19 vaccine.

Plenty of people online say otherwise. Including right here on this story. Numerous young and previously healthy people with heart problems post vaccine. Personal accounts abound.

When they bring it up to the experts who are suppose to be tracking this stuff, instead of listening to them and being concerned they are ignored, or gaslit.

Apparently you don't have to enter it into evidence and tell people about it if you just ignore it.

Confidence in medical science: extremely low.

So you hang onto your allocated strings in a record array and wonder why you run out of memory?

You should be saving the strings to the database so the GC has something to reclaim. It doesn't work when you keep fields 5, 7, 8 around in your records array.

Bulk insert should probably be used and bulk write should be called periodically. You should pause processing while it saves so you keep total active allocations nice and compact.

Otherwise the process will slow to a crawl when you get near your memory limit and all the time is spent in the GC trying to find ways to reclaim memory that you are still hanging onto.

You see massive swings in processing time by chunking the data because you are handing memory very poorly.

This should be bounded by database writes, not your language. Sigh.

Until the shadow IT that is unmanaged cloud freedom results in the finance and/or policy dept instituting the governance controls again.

Why down vote? I've had instances yanked. It sucks. No fraud, willing to pay, not abusing services.

I've read about lots of other users who have as well. Can't exactly poll their users.

Other providers have been fine for me.

Can confirm hearing similar reports various places. OCI has a similar rep.

Really rough when you get rug pulled by your provider.

The demise of NoSQL is greatly exaggerated. It's past it's hype cycle, and that's fine.

Many of us use it quietly, to do good work, and there is no need to crow to the world about what is happening under the hood.

> Economic growth is stagnant because energy production and energy import are stagnant. This has little to do with policy.

I can't think of an area of the economy anywhere that is more policy based than energy.

The biggest problem is that map, filter make copies of the structure. That's an allocation, that means GC calls.

You can make a similar function that changes the data in place and will be faster. But that comes with side effects which is not functional style.

That conversation should happen at the beginning of treatment. Which doesn't happen at a hospital.

This is taking about actual birthing.

There is little, if any, individualization at hospitals. It's a pretty horrible place to have a baby. Invasive care, constant interruptions, questioning decisions, sometimes IGNORING decisions entirely to do whatever the heck they want. Threatening to cease care if you don't comply, yep.

Honestly, I'm surprised the numbers are this low. Most people probably just comply with everything, that's the smoothest path through.

Adding friction to the use of information about your product seems like a disservice to the users/customers.

By not having that information in the system at all will only degrade the answers. Not change who is asking.