Parzee uses containers

Developing a Software-as-a-service has a lot of tightly knitted components. Each component provides its own purpose and adds its unique color in the overall picture. While we could have a solid block that was just this singular service from top to bottom; we encountered multiple challenges during our initial build. Some were limitations and some were requirements. Some limitations that we faced, were for high availability and for us to be able to monitor failed tasks and processes. Some requirements were for security and to separate the back-end processes and their networks. Additionally, configurations and consistency were key items that we needed to scale with load.

The logical solution at that time was containers. But we had to solve the following questions.

  •  How do they connect as a network?

The goal was to keep separate networks so we achieved isolation. Isolation is the simplest way to impart security so we thought that we should do that first. We solved that we by scripting and connecting network elements when the containers are built or started.

  • With separate containers how do we track process and applications running in them?

Here we used Compose and Kubernetes and few solutions to solve those simple tasks.

  • How do you make the data portable?

We decided to just provide a simple mapping to the data. However to map from the data to the application was difficult as two hops separated them. The Data was to be referenced from the central repository and needed to be visible into the Hosts running the containers and then the containers eventually referenced it for their applications.

You may be wondering why do all this, why not just do simple containers and move on? But then, were is the challenge with simple things and secondly we had to rethink the way we solved the problems.  We learnt it the hard way when our development system was down due to a cyber attack. We just shelved the old one as it only had test data and got down to build this complex system.

Now it has survived both cyber attacks and changing technology gracefully.

But for now, I should say….

Hope you learnt something from our experiences.

Parzee proved a simple and easy way to deploy application servers in Private and Public clouds, by just using a browser. Do give us a try at or write to us at



Browser as the Parzee client

Doing repetitive task is good, some tasks got much better over time. My commute to work was quite a drive, those 25 miles in the 45 minutes was a routine. But with flexible hours it was more pleasant as long I planned it and avoided the traffic. Now things are a phone call away. Now that’s easy, so at Parzee first we had to be was, simple.

When Partners deploy applications and clusters in Enterprises the first steps are to decide; what tools are needed, how simple are they to use and how fast can we commission? Parzee addressed these by redefining how to execute deployments.

Now what could be the simplest tool? Common cloud providers such as Amazon AWS and Google GCP have control on their infrastructure and installation images, its easy to clone application servers to give instant availability.

So how do we solve it creatively if our applications are proprietary or custom? Also, what do wee need to do to stay on top of things and provide visibility into what is happening?

The browser was our simple tool or client and that was decided. It didn’t take us long to decide on this fundamental question.

Now was the task to solving all the other issues. We had to solve these by accommodating various scenarios differently.

  • How do we reach the hosts or the infrastructure?

Challenges such as these have a simple solution. Build your client and ship it to the user. For the applications we support a thick client can be easily used. So now we not only had to simulate specific task our service needed but also solve how to tunnel through edge devices in the network for private cloud deployments.

Here we provide a unique proposition. Browser as a client so no software to install and the service uses simple and common tunnel methods to reach the host servers.

  • How do we ship data, content or installation images?

Installation images are not provided by Parzee. Opensource images are available to download freely, some applications that we support are licensed. To perform deployments installation data, content or installation images are needed on the host server. So the user needs to provide these installation images. If the images are not already in place then we needed to provide a simple solution from the browser. We solved this by using a two hop method that shipped the data efficiently all the way to the host server from the users machine just through the browser. Its a very difficult task let me tell you, but we made it appear simple.

  • How do we provide a view into the active process?

Monitoring whats happening is very important for deployments. Most time it involved connecting physical devices or using technologies that need console mapping. While infrastructure elements provide the functionality, it is always never available to external services or agencies. Here we used monitor ports to provide a view into the progress.

Try out a deployment at to truly appreciate our simple three step process and the ease of use. Remember you can do the same thing from your Laptop, Tablet or your Smartphone.

Hope you got a better insight into Parzee.

Do give us a try at or write to us at

Blog at

Up ↑