Atlas VS Flyway

> I usually have to spend an hour just removing stuff, disabling things and multiple reboots just to trim things down.

All of that is automated now. https://atlasos.net

How is this not clear?

"A modification of Windows, designed for gamers."

"Performance: By Removing unnecessary components, disabling power-saving features, and optimizing services."

"Privacy: By eliminating Microsoft's notorious tracking, pre-installed apps, and bloatware, you can feel confident when using Atlas."

Github link https://github.com/atlas-os/atlas

As a last hope you could backup your windows install and try installing Atlas OS on top, haven't tried it yet on Win11 but it should clear some process and ram for the game to run : https://atlasos.net/ MAKE SURE YOU BACKUP YOUR WINDOWS DISK FIRST. I'd recommand a software that you can launch on a USB stick instead of a program ran from Windows. I used https://www.easeus.com/backup-software/ but many others offer backups and PE USb bootable ISOs

Ok the whole story. My LLG started BSOD after doing a system restore because of a borked Handheld Companion install. So instead of using the recovery image I thought "now would be the perfect time to try out a vanilla Win 11 install and use AtlasOS” to see the difference it makes when it comes to gaming. So I download the drivers and Legion Space from Lenovo, Win 11 ISO, and AtlasOS files and I do think that it gave this beast some claws. It seems twice as fast as before without useless processes running in the background to bog things down. All the useless bloatware is gone and my LLG is running like a well oiled machine. I will run test later to compare but I think I have a winner here.

You can't, Windows >7 is a pain to have on a hard drive and will use 100% of it all the time. If you don't want to get an SSD, your best option is atlasos.net which isn't as good than getting an ssd but better than stock Windows.

AtlasOS turns Windows into a pure gaming OS. It removes all bloatware and system hog.

One modification that had a suprising effect was installing AtlasOS on top of Windows 11 using the AME wizard and Atlas playbook. https://atlasos.net/ - this produced an immediate and noticeable responsiveness improvement across the board. Before AtlasOS the mouse was still too slow even at the fastest setting in Windows. After AtlasOS everything was so much more responsive I had to slow down the mouse slightly because it was now moving so quickly and smoothly. I'm still a little dumbfounded by how good AtlasOS actually seems to be. But it's yet to be seen if whatever was gutted from Windows will cause issues down the line.

Apparently this one is optimized specifically for "AAA game" players and is frequently updated. I'm installing it now https://atlasos.net

Also RedGate, but Flyway has some reasons to recommend it over RedGate Deploy depending on your DBAs/workflows: https://flywaydb.org/

(Though I don't think it is "complete" or "perfect", either.)

EF Migrations are in a really good place now if you like/don't mind C# as a language (and you can easily embed SQL inside the C#, too, but there are benefits to being able to also run high level C# code). With today's tooling you can package your migration "runner application" as a single deployable executable for most platforms. You can build the executable once and run it in all your environments. (The same tool that updates your QA and Staging updates your Prod, testably running the same migrations.) Given the single executable deployable I might even consider using it for projects not themselves written in C#.

There is a bit of tooling needed but is already around. For Java for example I had very good experience with a combination of flyway [1] for migrations, testcontainers [2] for making integration tests as easy as unit tests and querydsl [3] for a query and mapping layer.

[1] https://github.com/flyway/flyway

[2] https://java.testcontainers.org/modules/databases/postgres/

[3] https://github.com/querydsl/querydsl

When software starts using a database, it's advisable to have version control, just as we have Github to control our source code. This is all to be sure about what was executed for that specific version. For Java and Spring boot, we have the Flyway framework that aims to resolve this situation, free of charge.

If you're looking for tools, like https://www.liquibase.com/ or https://flywaydb.org/, which are database-state-based schema migration toolkits - it might be relatively straightforward to build similar ones using Databricks SQL drivers.

Honestly I kind of wish there was a Lukas Eder database migration library. Call it whatever jooq-migration. At least I would have more insight of what is going on (<-- seriously look at the commit history).

This is a 4th option, which should play nice with ArgoCD. The following example runs flyway as a k8s job. The desired migration changes are recorded as files within the chart. This helm chart can be integrated with your application (Using hooks to determine when the migration job is run) or run manually.

By using an opinionated framework within the app/service (like Flyway, Migrate, Diesel, etc). Schema migrations happen on app/service start-up.

Depending on the language or platform there are libraries you can use to manage this, such as Prisma on node and Flyway for Java/JVM.

It's probably overkill but I've used github plus flyway at a couple places in the past which is pretty nice tool for tracking changes to a variety of db's, it's also very helpful if you ever need to replicate a db in a new region/environment.

Flyway