LastBackend

Lightweight Kubernetes replacement

LastBackend is a whole ecosystem of products and it allows, not only to manage containers similarly to Kubernetes but also collect their images on github/bitbucket/gitlab from the source code. It also contains a whole complex of infrastructural services designed to speed up developing, testing and deploying releases.

Around the web

Reviews

Alexander Kaloshin
Dmitry Maslennikov
Dima Che
 +7 reviews

Discussion

MakersThere are no makers yet
You need to become a Contributor to join the discussion.
Marcin Chmiel
Marcin Chmiel@marcin_chmiel · Automation is the key to success!
The UI is pretty sleek, but then again, is there any point in using it? Let's assume there is. Is there any real reason to abandon Kubernetes in favor of LB? I really feel that this should be just a dashboard component that you can deploy to your Kubernetes cluster. Maybe even a paid one with you providing support - but is there any reason to reinvent the wheel (other components? For me, the UI alone does not mandate abandoning the robustness of Kubernetes (which frankly isn't all that scary).
Dmitry Maslennikov
Dmitry MaslennikovHunter@dmitry_maslennikov
@marcin_chmiel Thank you for your question, it's a good one! LB is not just container orchestration, but rather a full cycle system that covers everything from setup to deployment and subsequent monitoring. When using Kubernetes all infrastructural services need to be connected by hand, and then it needs to be set up and supported. In our case, we just replaced Kubernetes container orchestration with our own while retaining the same functionality. LB has two interactions scenarios: it is possible to take the easy path and use our preset cluster and registry for which we are responsible or set up our open source orchestration system and open source registry on your side and then connect it to our management system. Thank you for noticing the UI, we really tried to make it user-friendly.
Marcin Chmiel
Marcin Chmiel@marcin_chmiel · Automation is the key to success!
@dmitry_maslennikov I see. Although integrated CD is the only benefit I'm seeing. If you're trying to differentiate yourself and market as "the better Kubernetes" I'd prepare a bullet point list with specific use cases that your system covers that k8s doesn't. It would definitely help potential users understand your offering.
Alexander Kaloshin
Alexander Kaloshin@undassa · CEO, Last.Backend
@dmitry_maslennikov @marcin_chmiel Hi Marcin! that's make sense, big thanks for that. What do you think about that: our open-source orchestration systems can replace k8s, and easier in deploy and manage than k8s, so how we can differentiate it?
Dmitry Maslennikov
Dmitry MaslennikovHunter@dmitry_maslennikov
@marcin_chmiel I consider that you have necessary experience with k8s. I would like to to know, could you help us with determining the cases which are not aplicable with k8s. We need to know it for avoidance such cases in our product.
Marcin Chmiel
Marcin Chmiel@marcin_chmiel · Automation is the key to success!
@dmitry_maslennikov I'm no k8s expert by no means, but feel free to hit me up.