The popular myth that cloud environments are not secure has an opposing view which is almost as strong. Proponents of this view claim that mature cloud providers due to the economies of scale have the ability to offer the best in class security. If vendors were unable to provide secure solutions their reputation and hence their entire business would be at stake. So there is no need for cloud consumer to worry or invest in cloud security. The answer in fact lies somewhere in the middle. According to a recent Gartner article 1 through 2020, 95 percent of cloud security failures will be the consumer's fault. It is imperative for any organization embarking on the cloud journey to realize that cloud security is a shared responsibility between the cloud provider and cloud consumer, and that majority of the burden is actually on the consumer to secure their cloud applications. This article will try...
The SOA Design Patterns Catalog has been extended with the newly authored Microservice pattern. This pattern formalizes the Microservice deployment model and specifies its distinct characteristics, as well as its impacts and application, as they pertain to service-orientation and SOA. The pattern explains the vital relationship between its deployment model and the resulting support it provides for the application of the Service Autonomy principle. It further highlights the important performance and reliability benefits that can be gained through the separation and isolation of microservices from monolithic hosting environments.
In the business world most of the enterprise are governed by internet based intranet based or product based software entity for smooth functioning of their logistics (For example healthcare, transportation, retail, banking, manufacturing etc.). Even though every enterprise falls in to a common logistic, everyone bring forth own IT enabled system for their business. Still we know that there is a huge gap in small and medium sized enterprises (SMEs) business and well defined cost effective IT services.
We know that most of these enterprises are functioning on similar logistics like retail, finance, manufacturing, agriculture, hospitality, banking etc. with varying inputs. At any time, in information technology also, most of the systems developed falls into these similar categories up to certain extend. Similar logistics are being automated for different enterprises by differed inputs and layouts.
Here we can look for a major business opportunity. We can think of a scenario (...
This is the second part of a two-part article series. The first part is published at Integration – The Blockchain 'Killer Usecase' – Part I.
Here is the problem: standards are an issue, because they would need to be followed. The Bitcoin protocol – ironically enough, because it is a decentralization approach – has an extreme point of view, when it comes to standardizing and centralizing the language necessary to execute transactions and eventually store data. There is just nothing else then Bitcoin Blockchain. The wallets are 'mere slaves', who have no other local Data Store and no other way to talk about Bitcoin than how the Blockchain commands them. That works for some use cases like finance and potentially legal, but is this a scenario that could resonate with the enterprise application landscape? Certainly not, there is an abundance of Applications out there all with different ways of describing concepts and...