The document discusses Governance 2.0, which aims to simplify and improve enterprise governance of assets like services, APIs, and applications. It involves providing a centralized user interface, continuous lifecycles spanning products, and aggregated operations across multiple assets. This contrasts with previous individual products and processes. The approach merges SOA governance and API management and provides a unified experience through interconnected APIs.
WSo2Con US 2013 - Case Study: Reflections on Enabling Change in Healthcare wi...WSO2
This document summarizes Paul Tjapkes' experience implementing a SOA approach at Spectrum Health, an integrated healthcare system. Some key points include establishing a multi-year SOA roadmap with executive support, adhering to standards like SOAP and WSDL, following SOA principles of contracts and granular components, prioritizing functions and goals, and creating an enterprise team focused on reusable strategic services. The benefits of this approach included increased flexibility, visibility and critical skills while preparing the organization for future changes in healthcare like real-time sharing and increased security needs.
WSO2Con US 2013 - Establishing an SOA-Focused Enterprise ArchitectureWSO2
This document outlines a presentation on establishing a service-oriented enterprise architecture. The presentation introduces service-oriented architecture (SOA) and discusses how it can help address challenges with enterprise architecture. It then describes building reference architectures using common integration patterns and a business services platform. The presentation emphasizes loosely coupled services, flexibility, and governance best practices enabled by SOA and configuration-driven development. It concludes with a demonstration of a thin slice application exemplifying these principles.
WSO2Con US 2013 - Using the Carbon Architecture To Build a Fit-for-Purpose Pl...WSO2
The document discusses the WSO2 Carbon architecture, which provides a lean, modular, and enterprise-class middleware platform for building various WSO2 products. Key points:
- Carbon is built on OSGi and uses its modularization features. It provides a minimal runtime and common components like security, caching, and logging that products can use.
- Products like the application server and API manager are built as a collection of modules running on the Carbon runtime. This allows agile development and no integration challenges between products.
- The architecture provides benefits like consistency across products, reduced learning curves, and unprecedented extensibility through additional modules.
- Future releases will focus on areas like the next version Carbon 5
WSO2Con US 2013 - Weapons Free: Open Source Solutions to Programmatic and Ope...WSO2
This document provides an overview of open source solutions for defense and intelligence communities. It discusses how open source software can help address major IT challenges around legacy system integration, data integration, information sharing, certification and accreditation, and software verification. Open source is defined as commercial software and allowed under government policies. Common myths about open source being unsecure, unsupported, or not commercial are addressed. Case studies are presented on how open source can help with problems like system transformation and testing automation. Insider threats are identified as a key cybersecurity risk that open source may help mitigate.
WSO2Con US 2013 - A Case Study Using WSO2 Middleware in an Enterprise SOA Inf...WSO2
This document presents a case study of using WSO2 middleware in a US military weapon system. It discusses how WSO2 helped solve problems with the military's Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) system and Global Information Grid (GIG) by providing an Enterprise Lean Layered Architecture (ELLA) that supported Department of Defense objectives within security restrictions. The presentation aims to provide an example of how WSO2 software supports military needs.
In a DevOps environment, the DBA role is impacted and shifting. DBAs are now working on cross-functional teams that are responsible for the full software development lifecycle. They focus on areas like database provisioning for development, automating deployments, implementing monitoring and performance checks. This allows for faster code deployments and issue identification. The DBA role requires more technical skills like programming languages and automation tools to be successful in these DevOps teams and processes. Case studies show how DBAs have helped customers by automating deployments, implementing health checks and analytics to improve code quality and performance.
The document discusses the concepts of Enterprise 2.0 and Web 2.0. It notes that while 80% of large companies will try Web 2.0 technologies by 2008, only 20% will successfully adopt aspects like user-generated content. Enterprise 2.0 refers to social software used internally in businesses, encouraging emergent use before structure. Examples include wikis, blogs, RSS feeds, and social networking. Issues with adoption include content management and ensuring appropriate use of these tools.
This document discusses the concepts of Web 1.0, Web 2.0, and Enterprise 2.0. It describes how Web 2.0 enables an "architecture of participation" compared to the "architecture of partition" in Web 1.0. The document outlines some key differences between consumer-focused Web 2.0 and Enterprise 2.0, and notes areas of intersection around social computing. It also discusses the technology stacks that power Web 2.0 applications, including application containers, messaging buses, and enterprise mashups. Overall, the document examines how Web 2.0 is influencing business computing through more dynamic applications that reduce costs.
WSo2Con US 2013 - Case Study: Reflections on Enabling Change in Healthcare wi...WSO2
This document summarizes Paul Tjapkes' experience implementing a SOA approach at Spectrum Health, an integrated healthcare system. Some key points include establishing a multi-year SOA roadmap with executive support, adhering to standards like SOAP and WSDL, following SOA principles of contracts and granular components, prioritizing functions and goals, and creating an enterprise team focused on reusable strategic services. The benefits of this approach included increased flexibility, visibility and critical skills while preparing the organization for future changes in healthcare like real-time sharing and increased security needs.
WSO2Con US 2013 - Establishing an SOA-Focused Enterprise ArchitectureWSO2
This document outlines a presentation on establishing a service-oriented enterprise architecture. The presentation introduces service-oriented architecture (SOA) and discusses how it can help address challenges with enterprise architecture. It then describes building reference architectures using common integration patterns and a business services platform. The presentation emphasizes loosely coupled services, flexibility, and governance best practices enabled by SOA and configuration-driven development. It concludes with a demonstration of a thin slice application exemplifying these principles.
WSO2Con US 2013 - Using the Carbon Architecture To Build a Fit-for-Purpose Pl...WSO2
The document discusses the WSO2 Carbon architecture, which provides a lean, modular, and enterprise-class middleware platform for building various WSO2 products. Key points:
- Carbon is built on OSGi and uses its modularization features. It provides a minimal runtime and common components like security, caching, and logging that products can use.
- Products like the application server and API manager are built as a collection of modules running on the Carbon runtime. This allows agile development and no integration challenges between products.
- The architecture provides benefits like consistency across products, reduced learning curves, and unprecedented extensibility through additional modules.
- Future releases will focus on areas like the next version Carbon 5
WSO2Con US 2013 - Weapons Free: Open Source Solutions to Programmatic and Ope...WSO2
This document provides an overview of open source solutions for defense and intelligence communities. It discusses how open source software can help address major IT challenges around legacy system integration, data integration, information sharing, certification and accreditation, and software verification. Open source is defined as commercial software and allowed under government policies. Common myths about open source being unsecure, unsupported, or not commercial are addressed. Case studies are presented on how open source can help with problems like system transformation and testing automation. Insider threats are identified as a key cybersecurity risk that open source may help mitigate.
WSO2Con US 2013 - A Case Study Using WSO2 Middleware in an Enterprise SOA Inf...WSO2
This document presents a case study of using WSO2 middleware in a US military weapon system. It discusses how WSO2 helped solve problems with the military's Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) system and Global Information Grid (GIG) by providing an Enterprise Lean Layered Architecture (ELLA) that supported Department of Defense objectives within security restrictions. The presentation aims to provide an example of how WSO2 software supports military needs.
In a DevOps environment, the DBA role is impacted and shifting. DBAs are now working on cross-functional teams that are responsible for the full software development lifecycle. They focus on areas like database provisioning for development, automating deployments, implementing monitoring and performance checks. This allows for faster code deployments and issue identification. The DBA role requires more technical skills like programming languages and automation tools to be successful in these DevOps teams and processes. Case studies show how DBAs have helped customers by automating deployments, implementing health checks and analytics to improve code quality and performance.
The document discusses the concepts of Enterprise 2.0 and Web 2.0. It notes that while 80% of large companies will try Web 2.0 technologies by 2008, only 20% will successfully adopt aspects like user-generated content. Enterprise 2.0 refers to social software used internally in businesses, encouraging emergent use before structure. Examples include wikis, blogs, RSS feeds, and social networking. Issues with adoption include content management and ensuring appropriate use of these tools.
This document discusses the concepts of Web 1.0, Web 2.0, and Enterprise 2.0. It describes how Web 2.0 enables an "architecture of participation" compared to the "architecture of partition" in Web 1.0. The document outlines some key differences between consumer-focused Web 2.0 and Enterprise 2.0, and notes areas of intersection around social computing. It also discusses the technology stacks that power Web 2.0 applications, including application containers, messaging buses, and enterprise mashups. Overall, the document examines how Web 2.0 is influencing business computing through more dynamic applications that reduce costs.
The Top 7 Active Directory Admin Challenges Overcome White PaperNetIQ
Overcome Top 7 Admin Challenges of Active Directory
As Active Directory's role in the enterprise has drastically increased, so has the need to secure the data. Gain insight on creating repeatable, enforceable processes that reduces administrative overhead and enables robust, customizable reporting and auditing capabilities.
Agile DevOps is Obsidian’s approach to agile development, continuous integration, continuous testing, and continuous deliverythrough the use of automated tools, and streamlined processes. We deliver incremental development continuously to production, which reduces defects, eliminates excess cycle time, provides continuous feedback and eliminates outage windows when deploying to production.
In this white paper, we will take a deeper dive into Obsidian’s Agile DevOps approach and how leaders in the federal government can leverage this solution for faster adoption of DevOps into existing and new federal IT programs.
In ITIL V3, the Release Management process from V2 was restructured and separated into two new processes within the Service Transition stage. Transition Planning and Support focuses on developing release policies, while Release and Deployment focuses on executing individual releases according to those policies. Other Service Transition processes like Service Validation and Testing and Knowledge Management also incorporate some elements of release management. Overall, Release Management still exists in ITIL V3 but has been improved and expanded through its restructuring across multiple processes.
Essay 1Why is it important for project managers to resist chang.docxYASHU40
Essay 1:
Why is it important for project managers to resist changes to the project baseline? Under what conditions would a project manager make changes to a baseline? When would a project manager not allow changes to a baseline?
This original post must contain a minimum of 300 words. All citations should be in APA format with a reference listing at the bottom of the post in APA format (be sure to include a link to the website of your current event in the reference listing).
Essay 2:
Students are encouraged to use critical thinking.
Critical thinking is the intellectually disciplined process of actively and skillfully conceptualizing, applying, analyzing, synthesizing, and/or evaluating information gathered from, or generated by, observation, experience, reflection, reasoning, or communication, as a guide to belief and action (as defined by the critically thinking community).
Review the readings, and write your thoughts on the information you find on the following three topics:
· How is SOA different?
· Event driven Agility and Origins of events
· Governance: Agility and SOA Enterprise Transformation.
This original post must contain a minimum of 500 words. All citations should be in APA format with a reference listing at the bottom of the post in APA format (be sure to include a link to the website of your current event in the reference listing).
Readings for essay 2:
Do not copy the below, only for example:
Service Oriented Architecture (SOA) is distinct from many business processes, but it is not exactly a new concept. SOA was originally a method used in software and web development, but it is applicable to other business processes as well (Cummins, 2009).
SOA differs from typical architectures on several levels. Firstly, it is comprised of loosely-coupled services that can be combined in a variety of ways (Cummins, 2009). This feature of SOA minimizes dependency between services, allowing for service units to have minimal impacts on each other even when optimizing a process (Cummins, 2009). Secondly, SOA emphasizes how infrastructure affects process development (Cummins, 2009). The final distinguishing aspects of SOA are its speed and flexibility; or agility. SOA can develop and modify services rapidly, and also remove artificial boundaries common in earlier architectural styles (Cummins, 2009).
Event Driven Architecture (EDA) can change the degree of coupling to very tight or loose depending on system requirements. SOA and EDA are not a product but an architecture or style of creating solutions. Moreover, SOA and EDA are not opposites. In fact each component of EDA can be implemented as SOA (Cummins, 2009). This means that EDA and SOA can benefit each other in complex processes. For example, a credit card company could create a new system to record credit card purchases over $1,000 and use EDA instead of making an entire new system. SOA is based on loosely-coupled services, and EDA is based on events, not connections, so ...
The concept of Web Governance is currently attracting a lot of attention.
It seems as if its moment has finally arrived - which is encouraging because until recently few industry commentators or senior managers were interested in the details of managing a website.
The reason is that there were just too many other problems that needed fixing first – like getting the basics of usability right, implementing accessibility or improving content.
And while we must admit that work remains to be done in these areas, many of the fundamentals have been put to bed.
As a consequence attention is now switching to how such tasks – and the resources needed to support them – are managed.
The shift to Web Governance highlights a realization that if the trajectory of online experience is to be maintained, a more professional approach to operations is needed.
Indeed, disciplines like design and content are now so widely understood that they are being gradually exhausted as differentiators .
This means that the way in which they are managed is becoming progressively more important to creating & maintaining value.
This document discusses best practices for integrating Vaadin web applications with Java EE 7. It recommends using Contexts and Dependency Injection (CDI) to connect Vaadin user interfaces to Java EE backend services. The Model-View-Presenter pattern is presented as a way to structure Vaadin applications for clean, maintainable code. Instructions are provided on getting started with Vaadin and CDI, including example project references.
The document provides an overview of the technical architecture of OpenIAM, an identity and access management solution. The architecture includes key components like an enterprise service bus, business process engine, messaging, scripting, presentation tier, security architecture, and more. OpenIAM takes a service-oriented approach and exposes over 30 services through the ESB for features like user management, authorization, provisioning, and reporting.
The document discusses various change management options in Aras, including the out-of-the-box CMII, Simple, Express, and Document change processes, as well as how to build custom change processes. It provides examples of custom change workflows and forms implemented at companies like Lear, Spontech Spine, and Xerox to address their unique change management requirements beyond the standard Aras processes. Administrators can choose the appropriate change process or adapt existing ones to fit their needs, and have flexibility to build fully custom workflows when necessary.
Rundeck is an open source automation platform that allows users to define, schedule, and execute jobs across multiple servers to automate system administration tasks. It was started in 2010 and has over 100 contributors. Rundeck provides a web interface, API, and CLI to define workflows and orchestrate tasks. It supports plugins for popular DevOps tools and can integrate with other systems like ITSM tools. Rundeck Enterprise provides additional features like high availability, security controls, and support.
Web 2.0 Core Concepts, Applications, and ImplicationsTomáš Pitner
The document discusses the concepts of Web 2.0 including its core characteristics and applications. It provides examples of Web 1.0 applications and their Web 2.0 successors. It also analyzes the functionality and qualities that Web 2.0 services provide like user participation, content sharing and contextualization. The document further discusses trends in Web 2.0 including identity consolidation, universal accessibility, interoperability and the semantic web.
The document describes a blog management system developed in PHP and MySQL. It includes sections on introduction, abstract, admin and reader modules, objectives, requirements specification, use case diagram, class diagram, ER diagram, data flow diagram, implementation, system testing, project screens, and conclusion. The system was created to automate an existing manual blog management system and make it more efficient, error-free, secure and easy for users to manage blogs, content, views and other information. It has admin and reader modules, with admin able to add, edit and delete various elements and reader able to view blogs and comment.
The document discusses the future of enterprise technology and the transition from Enterprise 1.0 systems to Enterprise 2.0. It notes that Enterprise 1.0 systems like ERP do not capture tacit knowledge, while Emergent Social Software Platforms of Enterprise 2.0 allow for collaborative knowledge discovery. It outlines some differences between Enterprise 1.0 and Enterprise 2.0, such as split vs emergent knowledge and intimidating vs social approaches. The document also discusses elements of an IT operating model for Enterprise 2.0, including processes, governance, services, measurement and organization. Finally, it raises questions about an organization's readiness for Enterprise 2.0 and the potential risks around disruption and changes to culture.
Keeping Pace with Product Evolution - UI Automation Framework GuidelinesTyto Software
When applications evolve, test automation code starts failing. If tests are not fixed quickly, automation code becomes stale and the whole suite becomes unusable. Changes to applications follow specific patterns. Knowing these patterns helps create automation frameworks which can handle them easily. The talk covered examples on how web applications evolve, how they break automation code, and how we can structure the automation code such that there is minimal change required to accommodate changes.
Heroku is a platform as a service that allows developers to build, run, and operate applications entirely in the cloud. It supports a variety of programming languages and allows applications to be scaled up by increasing the number of dynos or processes. Additional services like databases, email, and logging can also be added as addons. Heroku provides logs that aggregate output from all dyno processes and services for debugging purposes.
Enterprise 2.0 involves bringing Web 2.0 principles into businesses by enhancing enterprise applications and processes with social software, user participation, and service orientation. It aims to improve user experience, harness collective intelligence, and increase flexibility through techniques like social tagging, user authorship, and signaling updates. However, fully realizing Enterprise 2.0 also requires cultural changes in management and a shift to more bottom-up, outside-in thinking.
The document discusses release management as an ITIL process that aims to protect live environments and services. It states that 80% of service desk calls result from failed changes caused by IT. Releasing changes together as tested collections can reduce failures. The key is a release management policy that defines approval roles, release naming, types and schedules, and ensures changes follow formal procedures. This can dramatically improve quality and reduce costs from preventable outages.
The document discusses developing a service-oriented architecture (SOA) strategy using a software-as-a-service (SaaS) platform. It outlines key elements of an effective SOA strategy including abstracting functionality as loosely coupled services and leveraging both internal and external legacy systems. It also discusses advantages of a web-delivered SOA platform like cost savings and shared infrastructure.
Joomla Chicago Meeting July, 2009: CMS CageMatch IIJohn Coonen
JoomlaChicago July 2009 meeting presentation led by David Steele of the Acquity Group. Comparison of four top Open Source Web Content Management Systems currently on the market for enterprise use: Alfresco, Drupal, Joomla and Magnolia.
The document outlines the sections and structure of a new programme to develop a banking solution. It describes 12 sections that will make up the programme including programme management, resource management, product backlog, sprint planning, and governance. It provides details on the programme management structure including steering committees, product owners, and squads for different functional areas. It also includes examples of the high-level product backlog and sprint planning.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
The Top 7 Active Directory Admin Challenges Overcome White PaperNetIQ
Overcome Top 7 Admin Challenges of Active Directory
As Active Directory's role in the enterprise has drastically increased, so has the need to secure the data. Gain insight on creating repeatable, enforceable processes that reduces administrative overhead and enables robust, customizable reporting and auditing capabilities.
Agile DevOps is Obsidian’s approach to agile development, continuous integration, continuous testing, and continuous deliverythrough the use of automated tools, and streamlined processes. We deliver incremental development continuously to production, which reduces defects, eliminates excess cycle time, provides continuous feedback and eliminates outage windows when deploying to production.
In this white paper, we will take a deeper dive into Obsidian’s Agile DevOps approach and how leaders in the federal government can leverage this solution for faster adoption of DevOps into existing and new federal IT programs.
In ITIL V3, the Release Management process from V2 was restructured and separated into two new processes within the Service Transition stage. Transition Planning and Support focuses on developing release policies, while Release and Deployment focuses on executing individual releases according to those policies. Other Service Transition processes like Service Validation and Testing and Knowledge Management also incorporate some elements of release management. Overall, Release Management still exists in ITIL V3 but has been improved and expanded through its restructuring across multiple processes.
Essay 1Why is it important for project managers to resist chang.docxYASHU40
Essay 1:
Why is it important for project managers to resist changes to the project baseline? Under what conditions would a project manager make changes to a baseline? When would a project manager not allow changes to a baseline?
This original post must contain a minimum of 300 words. All citations should be in APA format with a reference listing at the bottom of the post in APA format (be sure to include a link to the website of your current event in the reference listing).
Essay 2:
Students are encouraged to use critical thinking.
Critical thinking is the intellectually disciplined process of actively and skillfully conceptualizing, applying, analyzing, synthesizing, and/or evaluating information gathered from, or generated by, observation, experience, reflection, reasoning, or communication, as a guide to belief and action (as defined by the critically thinking community).
Review the readings, and write your thoughts on the information you find on the following three topics:
· How is SOA different?
· Event driven Agility and Origins of events
· Governance: Agility and SOA Enterprise Transformation.
This original post must contain a minimum of 500 words. All citations should be in APA format with a reference listing at the bottom of the post in APA format (be sure to include a link to the website of your current event in the reference listing).
Readings for essay 2:
Do not copy the below, only for example:
Service Oriented Architecture (SOA) is distinct from many business processes, but it is not exactly a new concept. SOA was originally a method used in software and web development, but it is applicable to other business processes as well (Cummins, 2009).
SOA differs from typical architectures on several levels. Firstly, it is comprised of loosely-coupled services that can be combined in a variety of ways (Cummins, 2009). This feature of SOA minimizes dependency between services, allowing for service units to have minimal impacts on each other even when optimizing a process (Cummins, 2009). Secondly, SOA emphasizes how infrastructure affects process development (Cummins, 2009). The final distinguishing aspects of SOA are its speed and flexibility; or agility. SOA can develop and modify services rapidly, and also remove artificial boundaries common in earlier architectural styles (Cummins, 2009).
Event Driven Architecture (EDA) can change the degree of coupling to very tight or loose depending on system requirements. SOA and EDA are not a product but an architecture or style of creating solutions. Moreover, SOA and EDA are not opposites. In fact each component of EDA can be implemented as SOA (Cummins, 2009). This means that EDA and SOA can benefit each other in complex processes. For example, a credit card company could create a new system to record credit card purchases over $1,000 and use EDA instead of making an entire new system. SOA is based on loosely-coupled services, and EDA is based on events, not connections, so ...
The concept of Web Governance is currently attracting a lot of attention.
It seems as if its moment has finally arrived - which is encouraging because until recently few industry commentators or senior managers were interested in the details of managing a website.
The reason is that there were just too many other problems that needed fixing first – like getting the basics of usability right, implementing accessibility or improving content.
And while we must admit that work remains to be done in these areas, many of the fundamentals have been put to bed.
As a consequence attention is now switching to how such tasks – and the resources needed to support them – are managed.
The shift to Web Governance highlights a realization that if the trajectory of online experience is to be maintained, a more professional approach to operations is needed.
Indeed, disciplines like design and content are now so widely understood that they are being gradually exhausted as differentiators .
This means that the way in which they are managed is becoming progressively more important to creating & maintaining value.
This document discusses best practices for integrating Vaadin web applications with Java EE 7. It recommends using Contexts and Dependency Injection (CDI) to connect Vaadin user interfaces to Java EE backend services. The Model-View-Presenter pattern is presented as a way to structure Vaadin applications for clean, maintainable code. Instructions are provided on getting started with Vaadin and CDI, including example project references.
The document provides an overview of the technical architecture of OpenIAM, an identity and access management solution. The architecture includes key components like an enterprise service bus, business process engine, messaging, scripting, presentation tier, security architecture, and more. OpenIAM takes a service-oriented approach and exposes over 30 services through the ESB for features like user management, authorization, provisioning, and reporting.
The document discusses various change management options in Aras, including the out-of-the-box CMII, Simple, Express, and Document change processes, as well as how to build custom change processes. It provides examples of custom change workflows and forms implemented at companies like Lear, Spontech Spine, and Xerox to address their unique change management requirements beyond the standard Aras processes. Administrators can choose the appropriate change process or adapt existing ones to fit their needs, and have flexibility to build fully custom workflows when necessary.
Rundeck is an open source automation platform that allows users to define, schedule, and execute jobs across multiple servers to automate system administration tasks. It was started in 2010 and has over 100 contributors. Rundeck provides a web interface, API, and CLI to define workflows and orchestrate tasks. It supports plugins for popular DevOps tools and can integrate with other systems like ITSM tools. Rundeck Enterprise provides additional features like high availability, security controls, and support.
Web 2.0 Core Concepts, Applications, and ImplicationsTomáš Pitner
The document discusses the concepts of Web 2.0 including its core characteristics and applications. It provides examples of Web 1.0 applications and their Web 2.0 successors. It also analyzes the functionality and qualities that Web 2.0 services provide like user participation, content sharing and contextualization. The document further discusses trends in Web 2.0 including identity consolidation, universal accessibility, interoperability and the semantic web.
The document describes a blog management system developed in PHP and MySQL. It includes sections on introduction, abstract, admin and reader modules, objectives, requirements specification, use case diagram, class diagram, ER diagram, data flow diagram, implementation, system testing, project screens, and conclusion. The system was created to automate an existing manual blog management system and make it more efficient, error-free, secure and easy for users to manage blogs, content, views and other information. It has admin and reader modules, with admin able to add, edit and delete various elements and reader able to view blogs and comment.
The document discusses the future of enterprise technology and the transition from Enterprise 1.0 systems to Enterprise 2.0. It notes that Enterprise 1.0 systems like ERP do not capture tacit knowledge, while Emergent Social Software Platforms of Enterprise 2.0 allow for collaborative knowledge discovery. It outlines some differences between Enterprise 1.0 and Enterprise 2.0, such as split vs emergent knowledge and intimidating vs social approaches. The document also discusses elements of an IT operating model for Enterprise 2.0, including processes, governance, services, measurement and organization. Finally, it raises questions about an organization's readiness for Enterprise 2.0 and the potential risks around disruption and changes to culture.
Keeping Pace with Product Evolution - UI Automation Framework GuidelinesTyto Software
When applications evolve, test automation code starts failing. If tests are not fixed quickly, automation code becomes stale and the whole suite becomes unusable. Changes to applications follow specific patterns. Knowing these patterns helps create automation frameworks which can handle them easily. The talk covered examples on how web applications evolve, how they break automation code, and how we can structure the automation code such that there is minimal change required to accommodate changes.
Heroku is a platform as a service that allows developers to build, run, and operate applications entirely in the cloud. It supports a variety of programming languages and allows applications to be scaled up by increasing the number of dynos or processes. Additional services like databases, email, and logging can also be added as addons. Heroku provides logs that aggregate output from all dyno processes and services for debugging purposes.
Enterprise 2.0 involves bringing Web 2.0 principles into businesses by enhancing enterprise applications and processes with social software, user participation, and service orientation. It aims to improve user experience, harness collective intelligence, and increase flexibility through techniques like social tagging, user authorship, and signaling updates. However, fully realizing Enterprise 2.0 also requires cultural changes in management and a shift to more bottom-up, outside-in thinking.
The document discusses release management as an ITIL process that aims to protect live environments and services. It states that 80% of service desk calls result from failed changes caused by IT. Releasing changes together as tested collections can reduce failures. The key is a release management policy that defines approval roles, release naming, types and schedules, and ensures changes follow formal procedures. This can dramatically improve quality and reduce costs from preventable outages.
The document discusses developing a service-oriented architecture (SOA) strategy using a software-as-a-service (SaaS) platform. It outlines key elements of an effective SOA strategy including abstracting functionality as loosely coupled services and leveraging both internal and external legacy systems. It also discusses advantages of a web-delivered SOA platform like cost savings and shared infrastructure.
Joomla Chicago Meeting July, 2009: CMS CageMatch IIJohn Coonen
JoomlaChicago July 2009 meeting presentation led by David Steele of the Acquity Group. Comparison of four top Open Source Web Content Management Systems currently on the market for enterprise use: Alfresco, Drupal, Joomla and Magnolia.
The document outlines the sections and structure of a new programme to develop a banking solution. It describes 12 sections that will make up the programme including programme management, resource management, product backlog, sprint planning, and governance. It provides details on the programme management structure including steering committees, product owners, and squads for different functional areas. It also includes examples of the high-level product backlog and sprint planning.
Similar to WSO2Con US 2013 - Re-Thinking Enterprise SOA & IT Governance (20)
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Less Is More: Utilizing Ballerina to Architect a Cloud Data PlatformWSO2
At its core, the challenge of managing Human Resources data is an integration challenge: estimates range from 2-3 HR systems in use at a typical SMB, up to a few dozen systems implemented amongst enterprise HR departments, and these systems seldom integrate seamlessly between themselves. Providing a multi-tenant, cloud-native solution to integrate these hundreds of HR-related systems, normalize their disparate data models and then render that consolidated information for stakeholder decision making has been a substantial undertaking, but one significantly eased by leveraging Ballerina. In this session, we’ll cover:
The overall software architecture for VHR’s Cloud Data Platform
Critical decision points leading to adoption of Ballerina for the CDP
Ballerina’s role in multiple evolutionary steps to the current architecture
Roadmap for the CDP architecture and plans for Ballerina
WSO2’s partnership in bringing continual success for the CD
The integration landscape is changing rapidly with the introduction of technologies like GraphQL, gRPC, stream processing, iPaaS, and platformless. However, not all existing applications and industries can keep up with these new technologies. Certain industries, like manufacturing, logistics, and finance, still rely on well-established EDI-based message formats. Some applications use XML or CSV with file-based communications, while others have strict on premises deployment requirements. This talk focuses on how Ballerina's built-in integration capabilities can bridge the gap between "old" and "new" technologies, modernizing enterprise applications without disrupting business operations.
Platformless Horizons for Digital AdaptabilityWSO2
In this keynote, Asanka Abeysinghe, CTO,WSO2 will explore the shift towards platformless technology ecosystems and their importance in driving digital adaptability and innovation. We will discuss strategies for leveraging decentralized architectures and integrating diverse technologies, with a focus on building resilient, flexible, and future-ready IT infrastructures. We will also highlight WSO2's roadmap, emphasizing our commitment to supporting this transformative journey with our evolving product suite.
Quantum computers are rapidly evolving and are promising significant advantages in domains like machine learning or optimization, to name but a few areas. In this keynote we sketch the underpinnings of quantum computing, show some of the inherent advantages, highlight some application areas, and show how quantum applications are built.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
"NATO Hackathon Winner: AI-Powered Drug Search", Taras KlobaFwdays
This is a session that details how PostgreSQL's features and Azure AI Services can be effectively used to significantly enhance the search functionality in any application.
In this session, we'll share insights on how we used PostgreSQL to facilitate precise searches across multiple fields in our mobile application. The techniques include using LIKE and ILIKE operators and integrating a trigram-based search to handle potential misspellings, thereby increasing the search accuracy.
We'll also discuss how the azure_ai extension on PostgreSQL databases in Azure and Azure AI Services were utilized to create vectors from user input, a feature beneficial when users wish to find specific items based on text prompts. While our application's case study involves a drug search, the techniques and principles shared in this session can be adapted to improve search functionality in a wide range of applications. Join us to learn how PostgreSQL and Azure AI can be harnessed to enhance your application's search capability.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
"What does it really mean for your system to be available, or how to define w...Fwdays
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
3. What is Governance?
•
Governance is the act of governing, which relates
to decisions that:
–
–
–
define expectations
grant power
or verify performance
Image: http://mysql-gui.googlecode.com/svn-history/r205/trunk/qt-mysql-gui/images/256/Maintenance.png
•
•
It consists of either a separate process or part of
management or leadership processes
Read: http://en.wikipedia.org/wiki/Governance
4. What is Governance 2.0?
Image: http://www.gembapantarei.com/2009/03/how_do_lean_processes_prevent_human_error.html
5. What is not Governance 2.0?
Image: http://www.gembapantarei.com/2009/03/how_do_lean_processes_prevent_human_error.html
6. What is not Governance 2.0?
• Not a new invention
7. What is not Governance 2.0?
• Not a new invention
• Not a new standard
8. What is not Governance 2.0?
• Not a new invention
• Not a new standard
• Not a new technology/capability
9. What is not Governance 2.0?
•
•
•
•
Not
Not
Not
Not
a
a
a
a
new
new
new
new
invention
standard
technology/capability
product/solution
10. What is not Governance 2.0?
•
•
•
•
•
Not
Not
Not
Not
Not
a
a
a
a
a
new invention
new standard
new technology/capability
new product/solution
RESTful replacement
11. What is not Governance 2.0?
•
•
•
•
•
•
Not
Not
Not
Not
Not
Not
a
a
a
a
a
a
new invention
new standard
new technology/capability
new product/solution
RESTful replacement
change of process/practice
12. What is not Governance 2.0?
• If so, what are we working on?
14. What is Governance 2.0?
• Simplification of Discovery of Assets
Making it easy for you to find your service across
multiple repositories and service containers
In other words, everything related to a service
(technical information, lifecycle, SLA/QoS aspects,
analytics, business aspects) will be reachable from
a central place
15. What is Governance 2.0?
• A single continuous Lifecycle
Covers all aspects of design, development and
delivery
Interconnection of one product/solution to another
with a proper predefined (but customizable) flow
First-class support for all WSO2 products where a
user has to do the least in terms of integration
Extensible APIs and plug-points to provide the
same level of experience even with third-party
products
16. What is Governance 2.0?
• Aggregation of operations across multiple
assets
One click policy enforcement/update across
multiple Web Services, ESB artifacts and Business
Processes
Lifecycle transitions for multiple assets
17. What is Governance 2.0?
• Aggregation of operations across multiple
assets
One click policy enforcement/update across
multiple Web Services, ESB artifacts and Business
Processes
Lifecycle transitions for multiple assets
• Not limited to SOA
Ability to Govern any type of asset (ex:- Gadgets,
Mobile Applications)
19. How different is Governance 2.0?
Let’s take an example of a Service Lifecycle
20. How different is Governance 2.0?
Let’s take an example of a Service Lifecycle
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
21. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
22. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
23. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
24. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
25. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
26. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
27. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
28. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
29. How different is Governance 2.0?
A set of individual Products
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
30. How different is Governance 2.0?
A series of different UIs
Images:
http://cdn6.fedobe.com/wp-content/uploads/2012/11/Lock-icon.png,
http://www.astwinds.com/images/vista/captures2/services.png,
http://simpleicon.com/wp-content/uploads/Code-Optimization-3.png,
http://www.netop.com/uploads/pics/API_Banner_gears_404x149px.png
38. How different is Governance 2.0?
Governance becomes hard to implement
39. How different is Governance 2.0?
Governance becomes hard to implement
• Design, Implementation, Deployment, Information, and
Consumption of the Asset is spread across many
products
• Discontinuation of Lifecycle at product boundaries
• Due to this, it is impossible to perform aggregate
operations involving multiple assets
• And, makes governance different from asset to asset
40. How different is Governance 2.0?
Governance becomes hard to implement
41. How different is Governance 2.0?
Governance becomes hard to implement
• For example, Service Governance and API
Management were two separate processes
in the past
42. How different is Governance 2.0?
Governance becomes hard to implement
• For example, Service Governance and API
Management were two separate processes
in the past
• There were similarities and connection
points, and some information was shared
43. How different is Governance 2.0?
Governance becomes hard to implement
• For example, Service Governance and API
Management were two separate processes
in the past
• There were similarities and connection
points, and some information was shared
• Yet, the implementations were not
integrated and there was not
interconnection
44. How different is Governance 2.0?
We have identified these issues and found solutions
• For example, Service Governance and API
Management were two separate processes
in the past
• There were similarities and connection
points, and some information was shared
• Yet, the implementations were not
integrated and there was not
interconnection
45. How different is Governance 2.0?
We have identified these issues and found solutions
• We realize that SOA Governance and API
Management are not isolated but
integrated
46. How different is Governance 2.0?
We have identified these issues and found solutions
• We realize that SOA Governance and API
Management are not isolated but
integrated
• Others feel the same too
47. How different is Governance 2.0?
We have identified these issues and found solutions
• We realize that SOA Governance and API
Management are not isolated but
integrated
• Others feel the same too
• Read: http://www.gartner.com/id=2571325
48. How different is Governance 2.0?
Merging of SOA Governance & API Management
Image: http://rvadtalk.files.wordpress.com/2010/03/merging.jpg
49. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
50. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
51. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
52. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
53. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
54. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
55. How different is Governance 2.0?
Merging of SOA Governance & API Management
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
56. Re-thinking Enterprise SOA & IT
Governance
Published APIs
Deployed Services
Deployable Service Artifacts
& Metadata
Source Code
Design
Image: http://www.clker.com/cliparts/q/W/U/s/a/1/lab-beaker-md.png
57. Re-thinking Enterprise SOA & IT
Governance
• A centralized User Interface providing and
integrated experience despite the use of
multiple products
58. Re-thinking Enterprise SOA & IT
Governance
• A centralized User Interface providing and
integrated experience despite the use of
multiple products
• A continuous lifecycle spanning across
different products in different stages of
development made possible through
interconnected APIs
59. Re-thinking Enterprise SOA & IT
Governance
• A centralized User Interface providing and
integrated experience despite the use of
multiple products
• A continuous lifecycle spanning across
different products in different stages of
development made possible through
interconnected APIs
• Aggregated operations involving multiple
assets at the same time
60. Re-thinking Enterprise SOA & IT
Governance
And, that is what we are working on
• A centralized User Interface providing and
integrated experience despite the use of
multiple products
• A continuous lifecycle spanning across
different products in different stages of
development made possible through
interconnected APIs
• Aggregated operations involving multiple
assets at the same time
61. Re-thinking Enterprise SOA & IT
Governance
And, that is what we are working on
Image: http://www.shipmymail.com/mailforward/customer/Images2/coming_soon.png
62. On the Roadmap …
Image: http://www.shipmymail.com/mailforward/customer/Images2/coming_soon.png
67. On the Roadmap …
Beyond just a store: Centralized Discovery of Asset Information
68. On the Roadmap …
First-class end-to-end implementation with a complete installation of WSO2 App Factory
69. On the Roadmap …
More options with standard connectors and extension points for third-party products
Image: http://2.bp.blogspot.com/-UnKxNaXaapA/ToTRkZ9SrqI/AAAAAAAAAJU/OaVETFpGOSg/s1600/1.jpg
70. contact: senaka at wso2.com
Image: http://3.bp.blogspot.com/-E6jPdOwX5UY/T8ddstAqpwI/AAAAAAAAAkk/b_P_UjiA2OM/s1600/iStock_000008102559XSmall%5B1%5D.jpg