• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle

  • Seems like the kind of numbers you would expect. Windows is the default OS for every corporate and normie desktop everywhere, followed by the graphic designers and musicians rolling MacOS, and then the rest. The ratio never really changes, and never will unless something devastating happens to MS Office. If they included every headless server and AWS EC2 instance it would be the reverse with Windows barely featuring. With the proliferation of Android devices, Linux has become a quiet revolution with mobile but the majority of users probably don’t even know they run it.






  • I’m starting to warm up to this stuff. There is a future rapidly hurtling towards us where, if you take the time to read and think for yourself, you will become a genius. It was happening already in some stem fields where people used GUI tools without ever reading what the buttons did, and if you took the time to read the manuals and the underlying methods, you could become vastly more competent than anybody else in your team. This “AI” bullshit is just extending the lazy culture out to every piece of information on the web, where average Joe is already unable to concentrate beyond 140 characters. Those that take the time to learn the fundamentals and read deeply will have vastly superior knowledge of any subject, while the majority will be spoon fed superficial summaries filled with errors and no way of realising.







  • It’s very complex with hyper visors and virtualization technology. I don’t fully understand it myself in terms of how resources are allocated across something like aws or azure, but take a look at openshift vs openstack maybe. Openshift is for deploying containers and openstack is virtual machines. Openshift is kubernetes with some customizations for enterprise. Openstack is same for vm’s.

    Instances are virtual machines which tend to host an operating system, and a container is lighter and only hosts an application where the code and dependencies are isolated from the underlying operating system it runs on. k8 is kubernetes, which is container orchestration. I think of virtual machines for jobs that scale vertically, while containers are suited to jobs that scale horizontally. But this isn’t necessarily true as kubernetes is starting to get slurm functionality using tools like sunk.

    For integrating these things it depends on the application. You can run services in either by exposing ports and interact through API end points that point at them, eg for frontend web app serving data from a database hosted on a server or a container via fastapi. But I’m no dev ops engineer and the field is very complicated. There are many discussions around building micro services (containers) vs monolith (vm). Many decisions depend on the project. Hopefully some actual dev ops engineers will chime in and correct all of the above! xD


  • I’m interested in the same question. There isn’t a definitive text because the problem is infinitely broad. My approach is to build crud apps around the tech stack I’m interested in, currently Python with fastapi, arangodb, with some next and typescript for the front end. But you could swap out Python for Go and swagger. For security there is Keycloak. For scalability you could look at building your system as pods in open shift but that adds cost. Personally, I think unless you’re Netflix kubernetes is probably overkill. But the biggest problem is that today’s tech stack is replaced tomorrow by the next new shiny, and all of them are complex and will be entirely different for every team and every problem. A book for dev ops is almost impossible.