• A new initiative, spearheaded by 11 major IT companies, aims to establish industry-wide standards that enable zero outage and the continuous operation of IT systems.
• To succeed this initiative must include the wider industry, and should address the interaction between technology, people and processes as a source of IT systems failure.
On November 4th, a group of 11 major IT firms announced the formation of the “Zero Outage Industry Standard” association. Established in London by founding members Brocade (now being acquired by Broadcom), Cisco, Dell EMC, Fortinet, Hitachi Data Systems, HPE, Jupiter Networks, NetApp, SAP, SUSE and T-Systems, the association aims to kick-start discussions that it hopes will lead to new industry-wide standards that enable the continuous operation of IT systems. Continue reading “Establishing a Zero Outage Standard is About Technology, People and Processes”→
• SPIFs enable pre-integration of standalone third-party security products, eventually enabling enterprises to construct a customized, more effective enterprise security solution architecture.
• SPIFs are nascent, but they will have a growing impact on security product purchasing decisions. Leading-edge enterprises should begin researching SPIF ecosystems.
Enterprises have long been frustrated with the lack of interoperability among their enterprise security point products. The average large enterprise uses dozens of unique commercial security products and services, with few if any of them designed to work together.
Security product integration frameworks (SPIF) have the potential to change the game. SPIFs facilitate the sharing of security-related metadata, help standalone security products and services to interoperate effectively, and ultimately improve the efficacy of enterprises’ unique security architectures.
So what is a SPIF and how can it possibly deliver on such lofty ambitions? At its core, a SPIF is a fancy message bus system, typically augmented with authentication and access control, message encryption, subscription management and limited message store. Its centralized interconnection and messaging architecture enables security products to distribute data to other products and services and receive data from them. Third-party vendors add a SPIF’s pre-built messaging client code into their own products, customizing it as needed, and voila: enterprises using a SPIF can integrate products supporting that SPIF, often in a matter of minutes. Continue reading “Security Product Integration Frameworks: A Gamechanger for Enterprise Security”→
SOA supports the idea of reusing application development resources and functions, while a microservices architecture allows the same at a much more granular level.
Microservices plus automation addresses CI/CD via distributed service components.
During the next 12 months, we’ll see a flood of structured DevOps architectures emerge to support the growing microservices trend, which in turn fosters continuous deployment.
The emerging trend around microservices enhances traditional Java EE multitier/n-tier architectures with distributed service components and greater use of automation to support continuous integration, continuous deployment (CI/CD). Note that Java EE is considered the dominant standard for building next-generation, business-critical, distributed apps. By breaking an app down into smaller components, developers can target specific units of the app with more frequent updates. This enables more frequent deployments, which is where CI/CD comes into play. Continue reading “How Lightweight Middleware and SOA Are Evolving into Fine-Grained Microservices”→
Current Analysis’s recently updated reports on global enterprise mobility services providers show relatively static portfolios.
There were some notable exceptions, with some providers focused on new business tariffs, network upgrades, and security enhancements, along with portfolio restructuring to add simplicity.
In October, Current Analysis updated its profiles on the leading global enterprise mobility services providers, including both operator-led or operator-affiliated companies (AT&T, Verizon, Vodafone, DT/T-Systems, BT, Orange Business Services, and Telefonica) and IT service providers (IBM, CSC, HPE, and Accenture). While some aspects of these providers’ portfolios have been stagnant (or stable, depending on one’s interpretation) over the last six months, two things stand out. First, while portfolios may not have not changed dramatically, this does not imply that service providers believe there are limited growth opportunities in the market; and, second, for those companies that did add new services or restructured their portfolios, differentiation is important. As a result, pricing or service elements may need recrafting to meet customer needs more effectively and competitively. Continue reading “What Enterprises Can Expect from Enterprise Mobility Services Providers”→
• The benefits of PaaS are being realized through a consistent deployment format, easing DevOps processes
• New microservices architectures and containers will usher in advanced technologies including serverless architectures
PaaS is evolving to address growing DevOps concerns through open technologies; these, in turn, support new architectures, new forms of deployment through containers, and necessary features including orchestration, management, monitoring, and push services. PaaS services have evolved beyond providing basic app hosting to address modern DevOps’ needs, including the ability to leverage hybrid cloud and multi-cloud portability to ensure continuous integration and continuous deployment (CICD). Platform services provide containerization with particular importance now being placed on the ability to deploy and orchestrate containers, with policy, in order to modernize and port legacy and new apps onto any cloud infrastructure. Continue reading “The New PaaS Looks a Lot Like CaaS, with Orchestration”→