Kubernetes or Cloud Foundry : Cloud-Native App Deployment

Rahul Kumar — Tue, 17 May 2022 23:58:18 +0000

What should you choose : Cloud Foundry or Kubernetes?

When building a microservices-based program from the bottom up, selecting an application deployment platform is critical. It will be your first step in establishing the process for updating and deploying your application code, whether you want to construct your platform on bare metal servers, IaaS or a comprehensive PaaS solution.
Choosing the correct platform allows your application developers to spend more time developing new application features rather than packaging and deploying code each time a feature or bug fix is released.

1. As App Deployment platform

Cloud Foundry :
Cloud Foundry is a higher-level abstraction of cloud-native application deployment that shares capabilities with Kubernetes. As the platform's founders put it,
"You give it the software, and it takes care of the rest."
It recognizes application requirements, creates the container, deploys it, scales it, links it to the network, and directs traffic to it. As a result, the developer may concentrate solely on the application code. As a result, Cloud Foundry claims that the application is the platform's primary currency.

Kubernetes :
How does it compare favorably against Kubernetes? Because the container is Kubernetes' fundamental unit of currency, it adds to the complexity of developers' job by requiring them to construct the container for the app and give other deployment requirements, whereas Cloud Foundry does not. In other words, Kubernetes conceals nothing from developers, allowing both developers and operators to engage with it in the same way, but Cloud Foundry differentiates between cloud operators and cloud developers, simplifying the latter's interface.

2.The ability to run the platform from anywhere

The second significant distinction is that, whereas Kubernetes may be difficult to deploy on your infrastructure, Cloud Foundry is designed to host workloads on any hardware, including on-premise, public cloud, and basic VMs! It also enables operators to move tasks between all available solutions in a matter of minutes, without having to modify the software.

To summarize, Cloud Foundry works at a high degree of abstraction, providing a better level of efficiency to its users, particularly application developers, but with significant limits in terms of runtime customization. It's an excellent solution for new cloud-native apps and smaller teams who need to deploy often.
Kubernetes, on the other hand, is a lower-level abstraction that can be used to develop your own customized deployment platform, giving you more options. However, it adds to your teams' workload, which might lead to a loss in production.

Kubernetes, Cloud Foundry or Both?

With that in mind, why not combine the advantages of both systems? Because Kubernetes is designed to accommodate any workload, we can use it to run Cloud Foundry!

There are two open-source projects (KubeCF and cf-for-k8s) that enable Cloud Foundry to execute workloads on the same K8s cluster as the Cloud Foundry platform.

Using a combination of BOSH and Kubernetes, the Cloud Foundry Container Runtime is then utilized to deliver workloads. It combines Kubernetes' customization capabilities with the CF platform's deployment and administration capabilities. It's all because to the great Project Eirini, which is still one of the Cloud Foundry Foundation's ongoing initiatives.

As you can see, when it comes to cloud-native application deployment platforms, there is no one optimal choice. You may choose from a variety of ways depending on the complexity of your project, the size of your team, and other criteria.
Kubernetes is one of the most widely used systems in the world, and it can be utilized for almost any task. Cloud Foundry, on the other hand, is the ideal route to go if you have more generic needs and want to focus on your developers producing business value rather than worrying about deployment setup.

You may also mix the benefits of both worlds by using Cloud Foundry installed directly on Kubernetes.

Reference [to know more...] :

The above blog is submitted as part of 'Devtron Blogathon 2022' - https://devtron.ai/
Check out Devtron's GitHub repo - https://github.com/devtron-labs/devtron/ and give a ⭐ to show your love & support.
Follow Devtron on LinkedIn - https://www.linkedin.com/company/devtron-labs/ and Twitter - https://twitter.com/DevtronL/, to keep yourself updated on this Open Source project.

Error 404 : Page not Found

Rahul Kumar — Wed, 14 Jul 2021 21:16:57 +0000

When you click on a link, but instead of arriving to the site you want, an error message appears, stating that the page you requested is unavailable. It should be something along the lines of '404 Not Found.'

A 404 error is an HTTP status code that indicates that the website's server does not have the page you were searching for.

When website content is deleted or relocated to another URL, an error 404 message is commonly shown.

The 404 status code is the most common HTTP status code.

What are HTTP status codes?

A server answer to a browser's request is an HTTP status code. When you visit a website, your browser makes a request to the server, which the server responds to with a three-digit code called the HTTP status code.

These status codes represent a communication between your browser and the server over the Internet. They convey if things are fine😊, touch-and-go👍, or if something is wrong😕 between them.

Common HTTP status code classes:

Each three-digit status code starts with one of five integers, ranging from 1 to 5, and is written as 1xx or 5xx to signify status codes in that range. For example, 200, 301, 404, 500, and so on...

100–199 - Informational responses: The server is thinking through the request.
200–299  - Successful responses: The request was successfully completed and the server gave the browser the expected response.
300–399  - Redirection: You got redirected somewhere else.
400–499  - Client errors: Page not found. The site or page couldn’t be reached. 
500–599  - Server errors:  A valid request was made by the client but the server failed to complete the request.

HTTP Status Code 200 - OK
The 200 (OK) status code indicates that the request has succeeded. This is your ideal status code for your normal, everyday, properly functioning page.

HTTP Status Code 301 - Permanent Redirect
A 301 redirect should be utilized any time one URL needs to be redirected to another permanently.
Visitors and bots who come on that page will be sent to the new URL through a 301 redirect.

HTTP Status Code 500 - Internal Server Error
This status code indicates a server fault rather than a problem with pages missing or not found. A 500 error is a common server issue that will prevent visitors from accessing your website.

HTTP 404 errors can decreases a website’s ranking and reputation.
Once the crawlers have determined that 404 codes are being returned for a large number of queries, they will proceed to the next step. This might result in a significant drop in the number of visitors to the website.

👉Read more here (RFC 7231)

Getting bored😑
Try this once :https://http.cat/[status_code]
For example :
https://http.cat/404
https://http.cat/450
https://http.cat/500

DEV Community: Rahul Kumar