Win a copy of TDD for a Shopping Website LiveProject this week in the Testing forum!

Deepak Vohra

+ Follow
since Jun 12, 2012
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Deepak Vohra

An Enterprise server such as WildFly could take up a lot of CPU and RAM, and what would a framework like Kubernetes be suitable for if not have a fix for the CPU/RAM intensive server. One of the benefits of using Kubernetes is that it is loosely coupled, which implies that the replication controller is independent of service. Multiple user-interfacing services could be linked or routed to the same replica set  or other replication controller.
The WildFly image on Docker hub could be used as template. Creating a Docker image for WildFly is no different from creating any other Docker image.
- A Docker image is needed to run any containerized application.
- Kubernetes is a container orchestration platform.
- AWS EKS is a managed service for Kubernetes.
AWS EKS and Google GKE definitely provide several integrated services that could be used.  
Seems like AWS ECS is being confused with EKS. ECS is for Docker and EKS is for Kubernetes. Use EKS, not ECS, for WildFly 10 on Kubernetes. Wildfly 10 kubernetes cluster could definitely be created on AWS EKS. WildFly Operator for Kubernetes could be used.

Some references:
Assuming familiarity with AWS EKS when a managed node group is launched, On the Set compute configuration page, set Disk size – the disk size (in GiB) to use for your worker node root volume to a higher value if more disk space is needed.
Haven't used Kubernetes on-prem to be able to comment. But have used Kubernetes on AWS EKS, Google GKE, and IBM Kubernetes service.
For enterprise production use if data center infrastructure is already available on-prem is a suitable option, but if not the infrastructure and related services such as load balancers, storage, DNS, Logging and monitoring would need to be installed.  
Fargate's role with Kubernetes is the same as with any other application. A blog is more comprehensive than what could be listed.
I have discussed precisely the same question in a blog; it would be easier to just provide a link.
While Bare-metal does offer some performance and other benefits and its use has risen, not so with Kubernetes. To quote from a recent survey "While Kubernetes is widely adopted in the enterprise today, the percentage of workloads running on Kubernetes remains comparatively light. Even fewer of those workloads are running on bare-metal servers versus virtual machines. "

Some of the limitations of bare-metal are absence of integrated services such as load balancers that cloud environments provide. But that does not imply bare-metal doesn't have any advantages, which it does as noted at
The role of networking is enhanced by cloud computing, not diminished. The emphasis of networking has changed but it is still very important. As a reference
Fargate is a serverless platform, an alternative to the server based EC2. The benefits and limitations of Fargate are discussed in detail in the book and the documentation.
Docker Service Stacks are based on Docker Cloud Stack file, which has syntax of Docker Compose. Kubernetes does not support Docker Service Stacks natively.
A tool (Kompose) to convert a Compose file to Kubernetes files is available, but is not the same as Docker service stacks.
4 years ago