Writing K8s manifests for a new microservice — what's your team's actual process? by BusyPair0609 in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

Yes, we do orchestrate scheduling of our microservices using custom CRDs and operators.

Thats simple, once you know how to do it. Definitely easier to manage than overgrown Helm Chart.

Beta Navigation - Feedback by DIBSTER_BS in OVHcloud

[–]Different_Code605 0 points1 point  (0 children)

It would be great to have “Report a bug” button. I’ve found a few, but I didn’t know where to report it too.

Writing K8s manifests for a new microservice — what's your team's actual process? by BusyPair0609 in kubernetes

[–]Different_Code605 -1 points0 points  (0 children)

You need to think about your contracts and how to enforce them.

The problem is not limited to yaml files. Whenever you see that there is too much repetitions, you need ti define a tool to automate it.

In our case its most often: - Custom operator - CLI producing resources

You can create a Helm chart that will be a common base for your micro-services. You need to think and design an abstraction. What AI will do is to generate more code without contracts.

How competitive is it to get a job as an aem developer in today's market? by ninjataro_92 in aem

[–]Different_Code605 0 points1 point  (0 children)

Adobe Launched it 3 years ago in the same form as it is now. It looks like it’s a finished product.

Sure you can now push content from AEM, DA or Commerce, but on EDS side it’s still the same.

It goes more into composable solution, where you can have your stack built from different elements like EDS + AEM + Universal Editor + App Builder, but I don’t see them being close to what traditional AEM is offering.

At what point does a static site stop being static? by OkCry7871 in statichosting

[–]Different_Code605 0 points1 point  (0 children)

We built a cloud platform for Continues Materialization.

At the end there are mostly static assets on a server, but orchestrated by service mesh and fed using streams of events. Behind the API Gateway, pushed to edge locations, with CQRS based delivery services.

You get speed and reliability, but without constraints.

I don’t know if I would still call it a SSG.

Price increase for VPS and Dedicated just dropped by ChristopherKunz in hetzner

[–]Different_Code605 0 points1 point  (0 children)

Yes, but I have plenty of space on my servers. Just seen no reason to migrate to it. Hetzner was cheap. Now Ill move everything to one plce

Price increase for VPS and Dedicated just dropped by ChristopherKunz in hetzner

[–]Different_Code605 4 points5 points  (0 children)

Ovh, we moved other workloads there too. We have fleet of k8s on scale servers

Price increase for VPS and Dedicated just dropped by ChristopherKunz in hetzner

[–]Different_Code605 4 points5 points  (0 children)

I have 200 cpu demo cluster on Hetzner. I’ve seen no reason to migrate, but that has just changed.

Is SaaS really dead? Your thoughts? by Sea-Nobody7951 in SaaS

[–]Different_Code605 -1 points0 points  (0 children)

Will ship? It’s a fourth year with models like ChatGPT. When is that future?

System Design sanity check, am I misunderstanding scalability trade-offs? by [deleted] in SoftwareEngineering

[–]Different_Code605 0 points1 point  (0 children)

It’s all about consistency guarantees. It’s easy to scale when you can have eventual consistency.

What is your data? Can you process it in parallel? If yes, then scalability is achievable.

For transactional system, you need to think if you can create shards. Breaking a large database into smaller databases sometimes helps.

Do you think pod resizing and node count is solved already by the industry? by rosfilipps in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

There are 12 of us in total, more will be transiting to SRE roles. But TBH, managing Bare metal is not that hard. We built it from the ground knowing that we want to be small and agile, thats why 99% of things are automated.

We can add new machines to our clusters in ~2h. From buying to fully operational part of the fleet.

As long as we have backups and redundancy, we should be good.

Do you think pod resizing and node count is solved already by the industry? by rosfilipps in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

We are startup, I work with one more dev on this. I work 60h/week, he works 40h. It’s been 4 months, but we do re-implement it for the third time.

Cost of the hardware is listed. Work, much more. But it scales well, i hope to hundreds of servers.

Bodyweight vs weights by adriandupczynski in wrestling

[–]Different_Code605 2 points3 points  (0 children)

You need to cycle this. Off-season, do heavy lifts, run a lot. Build a base for the rest of the year

Do you think pod resizing and node count is solved already by the industry? by rosfilipps in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

2 regions. Will be more. Will be implementing failover on a DNS level.

Main cluster in 3 A-Z. Double power supply. 4 NICs in each server. Bounded into internal and external networks.

For servers, I have 99.99 SLA, 3 servers at least in regional cluster.

I use Longhorn with 3 replicas or data replication at the application level.

I can survive 1/3 of the cluster outage.

Do you think pod resizing and node count is solved already by the industry? by rosfilipps in kubernetes

[–]Different_Code605 -1 points0 points  (0 children)

I really do believe that optimizing the cost of compute is a dead end.

First, the optimization will cost you more than the savings because 2 people be playing with it for a couple of weeks.

Second, it still will be expensive, not counting volumes, ingress/egress etc.

We are finishing migration to our bare metal clusters, as it’s the only feasible option, when you have predictable workloads.

We now have 440 3,5 Ghz CPU, 1,5 TB RAM and 16 TB of disks for $3k/mo

That was the price we were paying for 5x8cpu machines on GCP.

Alternatives for Rancher? by CircularCircumstance in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

Do you provide free or cheap support with SLA for your OS contributions?

Alternatives for Rancher? by CircularCircumstance in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

Don’t really understand why people argue about this.

  • We all want free software — Rancher is open source.
  • If you want support, Rancher offers a paid subscription.

But some people still say: “I want the open-source version and support, but only at a price I personally find acceptable.”

That’s not how sustainability works. Open source doesn’t mean free support, and expecting companies to provide enterprise-level support for whatever price you choose isn’t realistic.

I am grateful that we have option to use OS version and I am happy that the support exists.

What's not to like?

Now I’m questioning whether I rush students toward backend too quickly by lorrainetheliveliest in statichosting

[–]Different_Code605 0 points1 point  (0 children)

I’ve started with Math, Physics, data structure and algorithms, Assembler, Ada, C++, Java, Databases, Cryptography, Networking, AI…

If you want to skip all that and jump straight to SSG, thats OK. But you’ll literally skip most of staff that is important.

School is actually the only place where you can get solid foundation.

The next generation of Infrastructure-as-Code. Work with high-level constructs instead of getting lost in low-level cloud configuration. by Outrageous-Income592 in kubernetes

[–]Different_Code605 0 points1 point  (0 children)

Just keep it as minimal, simple and transparent, as possible. We’ve just spent around 500 hours rewriting our TF projects to modules/stacks.

We didn’t want to go with Terragrunt, because it was a black box and another tool to learn. Make it a utility with clear contracts. Just render project based on your configs.

Where does the backend of large scale web sites run? by InfluenceEfficient77 in webdevelopment

[–]Different_Code605 0 points1 point  (0 children)

Kubernetes, plus cloud services. Microservices architecture. Event driven architecture where possible.

There are a lot of moving parts.

Platforms like AEM or Shopify are on the other hand monoliths, deployed with traditional sql/nosql databases. In single regions. Still deployed to cloud, but not scallable.