Cloud

Private cloud

There are two types of private clouds. Internal, you own the hardware, software, it's on your premises, typically your data center. An example would be Vmware. External, you don't own the hardware, you don't own the software, and it's remotely managed through a remotely managed location. An example would be Amazon Virtual Private Cloud.

Public cloud

While private clouds are yours so you build them and own them, public cloud are shared. Benefits of public cloud; on-demand self-service, ubiquitous network access; you can get to it from anywhere on the open internet, resource pooling enables you to share resources more efficiently, rapid elasticity; you can scale up to huge loads and only pay for the servers you use, etc.

DevOps in the cloud

We think differently. Design, development, testing, deployment, and operation, are all done at the same time. We're designing, developing, testing, deploying and operating those applications. We are not waiting for the previous step to finish. Meaning, we're not running down release cycles from design all the way to operations. We are leverage the agile methodology.

Cloud storage

Moving to enterprise-based cloud storage is something that's able to solve the problems of increase data growth and cost, and reduced IT budget. We will take large public cloud providers that are able to provide storage systems that will scale to the enterprise level needs. In other words, scale to petabytes, multi-petabytes, and the ability to provide fast disk access between the enterprises and the cloud systems out there.

Serverless computing

For most cloud computing, the first thing you need to do is to allocate a platform, either storage or computer, a database to get resources online for your applications. Serverless computing is an advantage over that paradigm because we are able to allocate the functions we need and leverage the services, servers, hardware and virtual resources we need automatically. So it's more of a natural and cost effective way.

Cloud governance

Provides guard rails to make sure we are not abusing our resources, not necessarily on purpose, but by accident. That we are in essence allowing the cloud-based system to operate effectively. For instance, we might have Google cloud, AWS cloud, etc. we need some governance tool that sits over and above these multi cloud that allows us to allocate and deal with these resources through a single abstract interface.

Advanced cloud architecture

If it's a traditional system called a pragmatic hybrid cloud. The ability to kind of use something even though it's not a paired public and private, it's still a hybrid cloud. Traditional hybrid cloud, which is a paired public and private cloud. Or a combination of public cloud one, public cloud two, private cloud, traditional system one, traditional system two. Sometimes three public clouds, maybe 100 different traditional systems, databases, cloud migration, batch-oriented migration, real-time data exchange, etc.

Cloud cybersecurity

Our ability to protect the data against outside threats. It is about dealing with the probabilities that your data will be compromised. We need to figure out what data is being stored, what kind of privacy policies, restrictions and legal issues that we have to deal with, for data that exists in the cloud. Asking questions like, will the data be handled by proposed cloud solution be protected against intrusions on privacy? We have seen in the paper before where credit card information and even healthcare information was compromised.

Cloud monitoring

We have governance; allow the systems to operate within parameters, if it falls out of those parameters, someone will to be alerted. We have performance; how quickly it runs. We have security; when people are attacking the system that performance levels are going to go down, so therefore that's a pattern we need to capture and redo. We have costWhose spending what, where, when? We have health; how things are going. And we have reporting; generated a few weeks, months, or in some cases years..

Cloud migration

This is about changing your infrastructure. This is not only about moving applications from one platform, e.g. datacenter, to another in the public cloud, but redoing your architecture and technology to allow you to accommodate change. Typical datacenter average server utilization is under 15%. Optimized cloud deployments achieve +75%. Doing a perfmon, basically to understand the capacity of a particular server in a datacenter, it is usually at 3%-5%. All that additional capacity is wasted. So, cloud computing is able to more efficiently run your infrastructure.

Cloud network

Network solutions are internal networks, networks that are within the enterprise, external networks, networks that exist perhaps in the public cloud. Or they can be other kinds of networks, such as those that exist in managed service providers. Under internal, we have both physical and software portion of the networks. Under external, we have public clouds and we have the open internet. Underneath internal and external, we have switching, routers, management, programmability, OpenFlows, virtual private networks, load balancing, DNS, etc.

Multicloud solution

Multicloud is about leveraging more than a single public cloud. This is really a unique architecture in that instead of just deploying on Amazon or Google or Microsoft, we're leveraging several types of public cloud brands. Typically within a multicloud architecture. Multicloud provides choice of cloud services. In other words, we're not limiting ourselves to one single brand of cloud, public clouds. So choose Amazon, Microsoft or Google as we just mentioned. But we're able to mix and match these services and get to a best based on what cloud services we're going to leverage.

Multicloud

Multicloud need to have security, identity management services and governance. You're going to see that on pretty much every good multicloud architecture because security and governance needs to be systemic to pretty much everything we do in a multi-cloud.

If we're going to manage these systems using identity and access management, then they have to have the capability of understanding the identity of all the greatest cloud services, the humans, the machines, everything that's participating in a multi-cloud architecture, and be able to guide them through in terms of what resources, what services, what APIs they're able to access.

So we either leverage governance to put policies around them in terms of how they're accessed. Put security around it with identity access management to basically figure out if they're going to be accessed by a particular human, machine, or other thing.

We have to do that because we're building a very complex system and security and governance is going to be complex as well. We're building applications that span more than a single public cloud. You have to keep that in mind, that in many instances, we're building applications that are going to run partly on Amazon and partly on Microsoft Azure or perhaps other clouds.