Akamai Cloud Computing (formerly Linode) include scalable and accessible Linux cloud solutions and services. These products and services support developers and enterprises as they build, deploy, secure, and scale applications.
$5
per month
Jenkins
Score 8.4 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
Kubernetes
Score 9.1 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
Akamai Cloud Computing
Jenkins
Kubernetes
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Akamai Cloud Computing
Jenkins
Kubernetes
Free Trial
Yes
No
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
CPU, transfer, storage, and RAM are bundled into one price. Storage capacity can be increased with additional Block Storage or S3-compatible Object Storage. Instant Backups can be added with complete independence to the stack. Linode NodeBalancers ensure applications are available.
We have used Kubernetes as a single cluster. It works really well, and it is very good for dev, test, and preproduction environments. With minor DevOps it can be easily prepared for production. In short, it reduced time from development to production.
The thing that caught my eye was the price to start with. I move to Digital Ocean because they had better options for virtual network isolation, but I came back as soon as Linode fixed the issue. There support is great and things just work.
We've used larger solutions, including AWS, Azure, Google Cloud, and Oracle Cloud. In each case, the pricing was confusing and, with all of the add-ons needed for even a simple infrastructure, ended up being several times the cost of a similar Linode solution. On the flip side, …
I have used Spinnaker as a CD tool. Though it's a very powerful CD tool we still needed Jenkins for CI, so to save some hassle for us we opt Jenkins solely.
The big difference between Jenkins and other alternative tools is that Jenkins is open source and it’s free. Jenkins is very much about simple functionality. It’s a general CI tool that offers basic automation. It’s the most common CI tool on the market with a large community …
When looking for alternatives for Jenkins we found CircleCI and TeamCity are good too. Jenkins was considered for reasons like it has a wide variety of plugins which integrate well with any kind of system. And its ease of use.
One of the other greater advantage is it is open …
Jenkins immense flexibility and its large and impressive selection of available community-driven plugins makes it ideal choice for solving non-traditional problems.
However, for CI/CD - consider the benefit of modern tools that enforce reusable, infrastructure as code design …
Docker Swarm is not as advanced as Kubernetes and there are no out of the box solutions for auto scaling and deployment strategies. Docker swarm doesnot have much experience with production deployments at scale. Swarm has a smaller community, and less frequent releases as …
We already had an enterprise Kubernetes 8 set up, so once we got our namespace it took me about 2 weeks to go from not knowing anything to having a self-contained jar in a container, running on Kubernetes 8. In comparison, it took me two weeks to install Java on a blank server …
Akamai Connected Cloud Linode would be a good service to host a content delivery network (CDN) because of its edge network but I'd prefer not to use Akamai Connected Cloud Linode for tasks that need GPU power such as Machine Learning or Artificial Intelligence (AI) because Akamai Connected Cloud Linode lacks deep GPU compute compared to AWS or Google Cloud or Microsoft Azure
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
I've been with them a long time. They provide me with the capabilities I need coupled with knowledgeable support that's not pay-for-extra. However, if I move to a non-Linux OS, the level of support by necessity will drop off. I can still ask questions about the infrastructure but I my ability to ask about OS features will decrease.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
Simple and clear, no BS interface. From a design perspective it's no Apple or Stripe, but it does what it needs without making me want to stick a fork in my eyes, like when being forced to use Azure, AWS or GCP.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
There is very little planned downtime. Whenever planned downtime is necessary I'm always given lots of advanced notice and an explanation that I can pass along to my users that they'll understand. I really appreciate that Linode appreciates my commitment to reliable service to my users. It shows that they believe they've been successful when I'm successful.
Servers are well dimensioned and price performant. Of course one always wants more, so if they were to upgrade their hardware for the same price I'd consider moving more workloads. Networking - never had an issue. Hardware speeds - disks are fast and can grow to great size.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Support was excellent and fast. The documentation is extensive and helpful. I learned many things from their online documentation. I did not contact them by phone, but email took a day or less. Complex problems would probably need a service contract. I liked the friendly and polite tone of the support.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
We got kick started with an initial walkthrough along with some free credits. The initial walkthrough helped us to understand Linode's ecosystem and start our hands on with Linode. We tried out some apps from Marketplace initially with the free credits, which not only helped us understand Linode better, but also those apps. We had implemented many such apps to our customers with Linode
We're a small organization. The implementation of our Linode solution was trivial. Once I justified a cloud server to my bosses over a co-location -- the co-lo wasn't as fast as our linode server in load tests -- it was a matter of moving one Linux implementation to another. Trivial.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
We switched to Linode from Namecheap due to poor uptime, and never had any issues with stability ever again after switching. We also cut our costs in half by switching. We compared Linode to DigitalOcean and Vultr, with the primary factor that caused us to go with Linode initially being their documentation. After using Linode for 3 years, their amazing support is another reason why we wouldn't consider anyone else at this point.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
Although I use only a fraction of their product offerings, the total set makes scalability an easy goal to shoot for. As I said, I have a few customers that use the services my Linode provides...and I like it that way. However, should I need to scale up, I can...without incurring any more cost than I need to.
