Cloud vs. On-Premise

Understanding key differences...

There are a number of competing priorities in enterprises these days. Every company is doing whatever they can to increase sales and shareholder value.

But how do you do that? It’s fairly simple: you need to make better business decisions and have the ability to provide more responsive customer service that scales with the growth of your organisation. The main ingredient in both of those is better communication and consolidating communications in the cloud, rather than sticking with decentralised legacy on-premises equipment is the first step in that direction.

Questions to Consider

•       Do you prefer all-inclusive subscription fees or expensive on-premises equipment, annual licensing fees, upgrade fees, and maintenance?

•       Do you want to reduce or completely eliminate capital-intensive upfront and ongoing hardware costs?

•       Do you want to lower IT support and staffing costs or free your team up to manage higher priority initiatives?

•       Do you want to eliminate costly, disruptive, and time-consuming upgrades?

•       Do you want to eliminate redundant software costs?

•       Do you want to meet the scaling demands?

•       Do you want to enable distributed workforce?

Coronavirus tests agility and scalability of your web applications: accelerate with kit-proxy

Spike in remote work due to the new coronavirus is testing agility and scalability of your applications. Even small service disruptions could significantly impede business productivity

A sudden surge in remote work due to the rapidly spreading new coronavirus is providing a real-world stress test of cloud services.

Leading cloud providers are unlikely to experience service disruptions that last beyond a single day. But now that millions of additional people are working from home, even shorter outages could hamper productivity more than usual.

"There are too many variables to say with certainty there will be no issues, cloud vendors have the capability to build things that are very resilient and very scalable, but everything has a breaking point."

Problems are already cropping up. On Wednesday, several Cisco collaboration services were unavailable or slow to load for hours in the middle of the workday, including Webex Teams and Cisco's control hub for IT admins.

Regardless of the cause, the incident was likely a bigger headache than usual for customers. Webex Teams messaging traffic is up 35% since last month and workers in the European and Asian countries most impacted by the new coronavirus (COVID-19) are registering for free Webex accounts at seven times the typical rate.

India Impact - Indian enterprises have cloud / infrastructure dependent complex strategies for their core applications and (COVID 19) remote work puts enormous stress on both core and non-core applications.

Good news is leading cloud vendors have designed their services to be able to scale quickly and with kit-proxy Indian enterprises could experience scale and agility of cloud without having to make code or infrastructure changes and do so within a day with real time fallback to origin.

Kit-proxy (deployed on AWS) can enable transformation of your consumer facing non-core web applications. AWS components that power kit-proxy: CloudFront & WAF, Lambda & Lambda@Edge, S3 and ECS.

Our goal statement of simplifying cloud / getting started with cloud, our successes with marquee Indian enterprises gives us a unique opportunity to give the best availability possible for your business and your consumers critical requirements.

about us:

kitsune (

kitsune is a cloud-native framework which enables developers to create full stack serverless web applications without having to worry about architecture, scalability and maintenance. kitsune also provides a HTML based language for developers making it the simplest way to build serverless web apps.

Introduction to CI/CD pipeline

Continuous integration/continuous delivery is responsible for pushing out a set of “isolated changes” to an existing application.

Enable your engineering team to deliver bug-free code at high velocity. A fast and reliable CI/CD pipeline is crucial for doing that sustainably over time…

A CI/CD pipeline may sound like overhead but is it?. It’s essentially a runnable specification of the steps that need to be performed in order to deliver a new version. In the absence of an automated pipeline, engineers would still need to perform these steps manually, and hence far less productively.

What is a CI/CD pipeline?

CI/CD pipeline helps you automate steps in your software delivery process, such as initiating code builds, running automated tests, and deploying to a staging or production environment. Automated pipelines remove manual errors, provide standardised development feedback loops and enable fast product iterations.

What do CI and CD mean?

CI, short for Continuous Integration, is a software development practice in which all developers merge code changes in a central repository multiple times a day. CD stands for Continuous Delivery, which on top of Continuous Integration adds the practice of automating the entire software release process.

With CI, each change in code triggers an automated build-and-test sequence for the given project, providing feedback to the developer(s) who made the change.

Continuous Delivery includes infrastructure provisioning and deployment, which may be manual and consist of multiple stages. What’s important is that all these processes are fully automated, with each run fully logged and visible to the entire team.

Benefits of CI/CD pipeline

CI/CD pipeline has more positive effects than simply making what was previously done a little bit more efficient:

  • Developers can stay focused on writing code and monitoring behaviour of the system in production.

  • QA and product stakeholders have easy access to the latest version of the system.

  • Product updates are not stressful.

  • Logs of all code changes, test and deployments are available for inspection at any time.

  • Rolling back to a previous version in the event of a problem is a routine action.

  • A fast feedback loop helps build an organisational culture of learning and responsibility.

about us:

kitsune (

kitsune is a cloud-native framework which enables developers to create full stack serverless web applications without having to worry about architecture, scalability and maintenance. kitsune also provides a HTML based language for developers making it the simplest way to build serverless web apps.

Scaling with microservices

Independent scalability is a major benefit of microservices, a challenging thing to implement. Scale microservices with a focus on users' priorities.

IT teams can face several challenges when scaling micro services based applications.

With a monolithic application, IT teams can carry out straightforward, well-established tactics to scale both vertically and horizontally. A load balancer can allocate traffic across various resources as needed. If there is too much of a load on the application, teams can even spin up new instances of the application to create more room for workloads.

A monolithic application is deployed as a single unit behind the load balancer. All you need to do is add more resources as transaction volume increases. However, the components of this monolith often scale inter-independently, so you might need to deploy more resources for the entire application even if you only experience demand for one individual component.

On the other hand, a micro services based application comprises a collection of loosely coupled services built to run on a mix of platforms. Because of the distributed nature of a micro services based architecture, IT teams must scale traffic differently than they would with a monolithic application. They must devise scalability strategies that protect micro services based applications from unexpected outages and help maintain fault-tolerance.

Scaling concepts

Teams must have a grasp on scalability and the reasons for it.

The scale cube, established in The Art of Scalability by Martin L. Abbott and Michael T. Fisher of AKF Partners, is a three-dimensional scaling model that illustrates three approaches to application scaling. The scale cube's X, Y and Z axes represent the three different scaling approaches. The traditional monolithic scaling method that replicates application copies falls along the X axis. Micro services based application scaling or types of scaling that break monolithic code fall along the Y axis. Lastly, Z-axis scaling involves the strategy of splitting servers based on geography or customer base in order to strengthen fault isolation.

Ways to monitor and optimise performance

End-user performance is the most important aspect of a micro services based application. Users notice slow and unintuitive application performance immediately. Even if a team uses the best technologies and tools to build a micro services based application, that IT strategy doesn't pay off if there is no improvement in user experience.

Teams should prioritise application performance and the end user's perspective to efficiently address micro services scaling issues. To prevent performance problems in a micro services based application, take advantage of an application delivery controller providing Layer 7 load balancers that adeptly facilitate scaling automation. Choose systems that are designed to handle micro services applications. Use them to monitor and optimise the performance of services in real time.

To scale a micro services based application effectively, teams must also track performance and efficiency goals. An effective monitoring system alongside a scaling strategy can help maintain optimal performance for a micro services based application.

Tracing the problems

All software application teams should take advantage of logging; however, tracing is difficult to carry out in a micro services based application. A micro services architecture comprises several services and service instances, likely spread across multiple systems.

Every service instance has the capability to write log data, such as errors and load balancing issues. The application support staff must aggregate the logs, and search and analyse them when needed.

Allocate resources appropriately

IT teams should remember that resource availability and allocation play a vital role in scaling a micro services application. Resource allocation specifically presents several challenges. The first layer, or the hardware layer, must be appropriate for the micro services ecosystem. Prioritise particular micro services for CPU, RAM and disk storage allocation.

Teams must understand scalability problems, set achievable goals with qualitative and quantitative consideration, and then apply resource-appropriate measures with a view toward performance and the end user's perspective.

about us:

kitsune (

kitsune is a cloud-native framework which enables developers to create full stack serverless web applications without having to worry about architecture, scalability and maintenance. kitsune also provides a HTML based language for developers making it the simplest way to build serverless web apps.

CIO's must digitise internal IT processes to keep pace with change

Be more adaptable than ever before to help businesses keep in step with the pace of innovation

The pace of change is faster than ever, which means CIOs need to think differently about the role of IT in the enterprise.

Traditionally, the effort of the IT department complemented the goals of business. The IT function developed the systems and software to support new business processes. Projects used to be run top-down with the executive management’s strategy for the business executed through the use of software-powered business processes. Projects took a waterfall approach, ran over several years and usually involved the deployment of major pieces of enterprise software infrastructure.

But the risks associated with major implementations failing, or the business changing before the systems were fully deployed, has seen a rise in different approaches to IT, where new functionality is delivered at a faster rate.

This pace of change is being driven by the way the web has evolved. Gartner believes the worldwide web is entering its third phase: in the 1990s, for the majority of users, the web was read-only; at the start of the 21st century, social media gave users a writeable web, allowing people to share comments, videos, pictures and “likes” with anyone who wanted to follow them; and now we are “on the cusp of Web 3.0, where the web becomes executable”.

IT needs to evolve into a connected intelligent architecture.

Digital transformation redefined

Rather than thinking of the IT that supports business as a fixed set of software and hardware, the software is part of a continuous development and continuous integration process, while hardware is swapped in and out and workloads shift between on-premise data-centres and the public cloud, based on business requirements.

Some would argue that this is what a digital transformation means for the IT department – instead of delivering IT projects, its role becomes about delivering capabilities on a continual basis, which enable the business to adapt and take advantage of new innovations.

To be successful, organisations need to be able to fail fast and work in an iterative and innovative way.

The CIO needs an entirely new strategy, where change is the only constant.

about us:

kitsune (

kitsune is a cloud-native framework which enables developers to create full stack serverless web applications without having to worry about architecture, scalability and maintenance. kitsune also provides a HTML based language for developers making it the simplest way to build serverless web apps.

Loading more posts…