Post 9v9qZsgP2ABneHdMrw by sir@cmpwn.com
(DIR) More posts by sir@cmpwn.com
(DIR) Post #9v9qZsgP2ABneHdMrw by sir@cmpwn.com
2020-05-18T03:02:57Z
2 likes, 3 repeats
2014 - We must adopt #microservices to solve all problems with monoliths.2016 - We must adopt #docker to solve all problems with microservices.2018 - We must adopt #kubernetes to solve all problems with dockervia https://twitter.com/sahrizv/status/1018184792611827712What's the 2020 update?
(DIR) Post #9v9qvm0WX9adJeU688 by middlepath@mastodon.social
2020-05-18T03:06:51Z
0 likes, 0 repeats
@sir budget cuts. Hire cheap IT staff and a bunch of java devs. Move everything back to bare metal.
(DIR) Post #9v9r3tWqSBJkxYTVqK by drisc@merveilles.town
2020-05-18T03:07:15Z
0 likes, 0 repeats
@sir Probably something blockchain related. Or it all gets burnt down and the monoliths rise again.
(DIR) Post #9v9rOMuSvREHsIHnLE by dansup@mastodon.social
2020-05-18T03:11:59Z
0 likes, 0 repeats
@sir Hello Monolithshttps://thenewstack.io/this-week-in-programming-forget-microservices-monoliths-are-the-way-forward/
(DIR) Post #9v9t1Iuro5wcjkbTnM by zethra@fosstodon.org
2020-05-18T03:30:07Z
0 likes, 0 repeats
@sir run your entire service on millions of iot devices.
(DIR) Post #9v9uojM0OuGWsMQhAO by alexbuzzbee@fosstodon.org
2020-05-18T03:51:16Z
0 likes, 0 repeats
@sir We must adopt openshift to solve all problems with kubernetes
(DIR) Post #9v9vSHurph5TMXb9vc by alexbuzzbee@fosstodon.org
2020-05-18T03:58:25Z
0 likes, 0 repeats
@sir 2022 - We must adopt monoliths on giant mainframes to solve all problems
(DIR) Post #9vAD2LZjP7PWMBUZzk by lanodan@queer.hacktivis.me
2020-05-18T07:15:27.083871Z
0 likes, 0 repeats
@sir 2020 - We must adopt #plan9 to solve all our problems.(we can dream)
(DIR) Post #9vADCh0UZoghinwVCS by neauoire@merveilles.town
2020-05-18T07:16:11Z
0 likes, 0 repeats
@sir 2020 Year of the plan9 desktop
(DIR) Post #9vADMs38NKjKrj21QG by neauoire@merveilles.town
2020-05-18T07:16:21Z
0 likes, 0 repeats
@sir 2020 Year of the plan9 desktop :glenda:
(DIR) Post #9vAZKiS1I1qFVa37aa by moonglum@social.yakshed.org
2020-05-18T11:24:12Z
0 likes, 0 repeats
@sir something with Service Meshes, probably
(DIR) Post #9vAuCCb5w2A1R94kjI by architect@linuxrocks.online
2020-05-18T15:18:58Z
0 likes, 0 repeats
@sir We must turn #linux into a Unikernel to solve the issues with containers
(DIR) Post #9vAx8FeYvmTLcQVOfA by nergal@linuxrocks.online
2020-05-18T15:51:48Z
0 likes, 0 repeats
@architect @sir so reverse the design to fix one feature while breaking "userland"? How about not using containers on linux kernel? GNU Hurd could be developed for this instead?
(DIR) Post #9vAxUadjaFkj4vln9s by erkol@mastodon.social
2020-05-18T15:55:00Z
0 likes, 0 repeats
@sir I don't think containers are the issue here. They have been a thing for around 20 years. The issue is more how they are getting used now compared to how they were used then. Containers was and continue be usefull tools. But you really don't need a container to run a small webservice which some people seem to continue to think.
(DIR) Post #9vB4By5qrLE3zlzNtg by architect@linuxrocks.online
2020-05-18T17:10:57Z
0 likes, 0 repeats
@nergal @sir Unikernels are sort of "peak containment" as it's at least supposed to be an OS with only enough to tackle a specific job and contain no other code. So you can't, for example, break in as a user on a Unikernel with no need for user accounts.However, some people seem determined to try forcing Linux into places where it doesn't belong, like turning it into a Unikernel, or trying to force it to act as a Microkernel via k8s or other poorly thought out designs.
(DIR) Post #9vB4IdLOP43RfZR7xY by architect@linuxrocks.online
2020-05-18T17:12:10Z
0 likes, 0 repeats
@nergal @sir For example, these people argue that with some config tweaks, Linux is an acceptable Unikernel: https://dl.acm.org/doi/abs/10.1145/3317550.3321445