This document discusses the evolution of software architecture and the rise of web-oriented architecture (WOA). It notes that as software became more networked and integrated, traditional SOA approaches struggled to keep up. WOA leverages open web standards like HTTP, URIs, and web APIs to build globally accessible networked applications and platforms in a way that has surpassed traditional internal enterprise SOAs. By exposing functionality and data via web services, WOA allows organizations to harness network effects and create compelling platforms for others to build upon.
To view recording of this webinar please use below URL:
http://wso2.com/library/webinars/2015/09/web-oriented-architecture/
Is SOA the answer to everything? Perhaps not. Web oriented architecture (WOA) or SOA + WWW + REST, takes you several steps further by filling the blanks of SOA and helping you build an end-to-end complete web application. In addition to APIs, WOA identifies user interfaces and application state as first-class components of an architecture. Most of what we build today is actually WOA, though the abbreviation might not be that popular.
This session will discuss
The original definition of WOA by Gartner in 2006
The changes to WOA over the last 10 years
Today’s trends
WOA-Stack
WSO2Con ASIA 2016: Moulding Your Enterprise with Resource Oriented ArchitectureWSO2
An enterprise environment is typically heterogeneous, often spanning across organizational boundaries. Building such systems require tools that promote intrinsic interoperability and provide ease of integrating over boundaries. It also needs to use technology that promotes simplicity and is easy to handle. Resource oriented architecture (ROA) supports this by focusing on entities and interactions for effective enterprise integration.
This session will first give an overview of resource oriented computing and the advent of ROA. It will then focus on what it means to have a ROA in your organization – both externally and internally. It will finally discuss how WSO2 technology can help you built your enterprise system in a resource oriented manner.
To view recording of this webinar please use below URL:
http://wso2.com/library/webinars/2015/09/web-oriented-architecture/
Is SOA the answer to everything? Perhaps not. Web oriented architecture (WOA) or SOA + WWW + REST, takes you several steps further by filling the blanks of SOA and helping you build an end-to-end complete web application. In addition to APIs, WOA identifies user interfaces and application state as first-class components of an architecture. Most of what we build today is actually WOA, though the abbreviation might not be that popular.
This session will discuss
The original definition of WOA by Gartner in 2006
The changes to WOA over the last 10 years
Today’s trends
WOA-Stack
WSO2Con ASIA 2016: Moulding Your Enterprise with Resource Oriented ArchitectureWSO2
An enterprise environment is typically heterogeneous, often spanning across organizational boundaries. Building such systems require tools that promote intrinsic interoperability and provide ease of integrating over boundaries. It also needs to use technology that promotes simplicity and is easy to handle. Resource oriented architecture (ROA) supports this by focusing on entities and interactions for effective enterprise integration.
This session will first give an overview of resource oriented computing and the advent of ROA. It will then focus on what it means to have a ROA in your organization – both externally and internally. It will finally discuss how WSO2 technology can help you built your enterprise system in a resource oriented manner.
WSO2Con ASIA 2016: Building Web Apps Using Web-Oriented ArchitectureWSO2
Web-oriented architecture (WOA) or SOA + WWW + REST takes you several steps further by filling the blanks of SOA and helping you build an end-to-end complete web application. In addition to APIs, WOA identifies user interfaces and application states as first-class components of an architecture. Most of what we build today is actually WOA, though the abbreviation might not be that popular. This session will discuss the changes to WOA over the years, today’s trends, and how you can leverage WOA to build web apps.
Microservices in the Enterprise: A Research Study and Reference ArchitectureJesus Rodriguez
This document presents a research about microservices architectures in the enterprise. The document explores some of the key patterns and technologies relevant to implement microservices solutions in enterprise environments.
Microservices = Death of the Enterprise Service Bus (ESB)?Kai Wähner
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. Continuous Integration and Continuous Delivery control deployments. This way you get shorter time to results and increased flexibility.
Microservices have to be independent regarding build, deployment, data management and business domains. A solid Microservices design requires single responsibility, loose coupling and a decentralized architecture. A Microservice can to be closed or open to partners and public via APIs.
This session discusses the requirements, best practices and challenges for creating a good Microservices architecture, and if this spells the end of the Enterprise Service Bus (ESB).
Key messages of the talk:
• Microservices = SOA done right
• Integration is key for success – the product name does not matter
• Real time event correlation is the game changer
How iPaaS Overcomes the Challenges of Cloud IntegrationFlowgear
As enterprise IT infrastructure continues to move to the cloud, the need to safely and reliably integrate a wide range of on-premises and cloud systems becomes increasingly critical. However, traditional integration tools are inadequate for handling the complex integration challenges enterprise IT managers face when trying to manage cloud/ground data flow and link cloud-based services with on-premises legacy systems.
Discover how integration-platform-as-a-service (iPaaS) technology offers the most flexible, secure, and reliable way to easily integrate crucial on-premises systems with newer, cloud-based applications and services.
WSO2Con USA 2017: The Role of Enterprise Integration in Digital TransformationWSO2
Enterprise integration has been evolving for several decades and has been going through drastic changes. In this session, we focus on the future trends in enterprise integration and how WSO2 integration addresses these needs.
Overview of enterprise integration: past, present and the future
Integration Service: Is it an anti pattern in future enterprise architecture?
Importance of integration in modern enterprises
Integration beyond the ESB: integrating services, systems, data and identities
The role of integration in microservices, Internet of Things (IoT) and APIs
Redefining scaling and performance
Developer experience: visual modeling, debugging and tracing
Hybrid integration: on-premise, integration Platform as a Service (iPaaS) and iSaaS
Business need of IT systems to get integrated. Why legacy systems are feeling modern technologies like SOA can help them to keep alive by providing the integration solution.
Catalog Management in the Cloud: Two Years Intrail001
Presentation given at the Catalog Management Interest Group, ALA Annual Conference, June 25, 2016 by Stacie Traill and Betsy Friesen (University of Minnesota)
The libraries of the University of Minnesota system were early adopters of Ex Libris's Alma system, migrating in late 2013. In the two and a half years since migration, systems and metadata staff have learned much about the differences between managing a cloud-based, multi-tenant ILS and a locally-hosted server-based ILS. Presenters will discuss some of these differences, along with issues they faced in adopting a new system early in its development cycle. In addition, they will provide an overview of the highlights, challenges, and ongoing evolution of Alma's catalog management tools and functionality (such as authority control and batch processing capabilities).
WSO2Con USA 2017: Implement an Effective Digital Platform Using WSO2 IntegrationWSO2
The WSO2 integration platform offers a high performance, lean, enterprise-ready solution to solve integration and innovation challenges faced by connected businesses. This platform offers modern integration technologies that empower enterprises to build a digital business by seamlessly connecting mobile apps, services, multiple data repositories, social media, and cloud and on-premise systems. This is all done to enhance your customers’ experience and increase internal productivity.
One of the primary focuses in modern integration is to think in terms of the network-effect in terms of reliability in resilience, scalability, affordability, and adaptability. The session will focus on
Under the hood: Integration server architecture
Mediation catalog
Architectural styles for integration
Enhancing
Hybrid integration with WSO2
Debugging and troubleshooting your integration
Deployment
Performance tuning
Production hardening
WSO2Con ASIA 2016: Iterative Architecture: Your Path to On-Time DeliveryWSO2
Enterprises today operate in complex and competitive markets. They are constantly trying to optimize business functions, introduce new business capabilities and tap into new markets quickly and efficiently. For the business to be agile, software systems that are used to provide business capability need to be agile. The ability to build and integrate new capability in a short time becomes valuable. At the same time, enterprise software systems should help with evolutionary as well as revolutionary changes that will affect core business functions.
In this session we will discuss iterative architecture, which is about taking an iterative approach when introducing architectural changes to support business and technical requirements. We’ll also look at real world examples of implementing architectures in iterations.
Original interactive slides here: http://slides.com/yunzhilin/microservices-and-friends#/
A tongue-in-cheek presentation to TrunkPlatform interns 2015.
WSO2Con ASIA 2016: Understanding Microservice ArchitectureWSO2
Today many organizations are leveraging microservice architecture (MSA), which is becoming increasingly popular because of its many potential advantages. MSA itself is divided into two areas – inner and outer architectures – which require separate attention. Moreover, MSA requires a certain level of developer and devops experience too. This talk will be an awareness session about MSA and will also discuss WSO2′s strategic initiatives in both the platform level and WSO2 MSF4J framework level.
Governance in the ever-changing PowerBI world for the organization
Best practices
deployment recommendations
Security settings
Reporting on the reports and optimizations
*According to all the new features and capabilities as by March 2019, will probably change again very soon.
This is a must-read for all engineers interested in developing a Micro services architecture. Turn your monolithic server into a prolific and multiple instance solution! Includes well-known example such as Netflix. Please contact me for more details.
I Love APIs 2015: Building Predictive Apps with Lamda and MicroServices Apigee | Google Cloud
I Love APIs 2015
Machine learning, big data, and API technologies have drastically reduced the complexity of building predictive apps. But all these advances also mean that these apps require a new approach to system architecture. This talk discusses the lamda architecture and microservices, and best practices on decomposing your app into batch, near-realtime, an real-time services. Learn how Apigee uses both new architectures to implement predictive apps using Hadoop, Node.js, Cassandra, and ElasticSearch.
Every enterprise has a multitude of existing systems - including on-premise as well as cloud solutions - that perform critical functions. Integrating data and services across these systems is critical for an enterprise to successfully implement its digital transformation efforts. Therefore, most often than not, enterprise integration is at the heart of any organization’s digital transformation strategy.
WSO2Con USA 2017: Implementing a Modern API Management Solution that Benefits...WSO2
A few years ago, Brigham Young University (BYU) started a massive effort to replace the existing API management systems with a more modern, standard, and efficient solution. WSO2 products such as WSO2 API Manager and WSO2 Identity Server are at the core of this new solution. They expected to improve consumer experience and minimize the impact on existing development work. Along the way, they hit a few roadblocks including problems such as integrating with legacy systems, improving API discoverability changing authentication mechanisms, and re-designing API development and deployment processes.
This session will explore how they overcame these roadblocks by using the WSO2 products will discuss how they
Integrated new the API management solution with legacy systems via API mediation
Standardized API documentation across the organization
Improved API search and discoverability for consumers
Made API consumption simple by following industry standards
Web- and Mobile-Oriented Architectures with Oracle Fusion Middleware (OOW 2014)Lucas Jellema
Mobile applications as well as a large class of modern HTML5 web applications are built on top of an architecture with special provisions, such as RESTful services; the personal cloud, to provide a cross-device experience; push; cache; localization; scalability; and secure interaction with the enterprise back end. Gartner refers to this as the web-oriented architecture. Oracle Fusion Middleware offers key products (Oracle SOA Suite, Oracle Identity Management, and Oracle API Gateway) to implement this architecture, possibly in combination with cloud services such as Oracle Mobile Cloud Service, Oracle Messaging Cloud Service, and Oracle Storage Cloud Service. This session discusses the architecture itself and what it entails.
WSO2Con ASIA 2016: Building Web Apps Using Web-Oriented ArchitectureWSO2
Web-oriented architecture (WOA) or SOA + WWW + REST takes you several steps further by filling the blanks of SOA and helping you build an end-to-end complete web application. In addition to APIs, WOA identifies user interfaces and application states as first-class components of an architecture. Most of what we build today is actually WOA, though the abbreviation might not be that popular. This session will discuss the changes to WOA over the years, today’s trends, and how you can leverage WOA to build web apps.
Microservices in the Enterprise: A Research Study and Reference ArchitectureJesus Rodriguez
This document presents a research about microservices architectures in the enterprise. The document explores some of the key patterns and technologies relevant to implement microservices solutions in enterprise environments.
Microservices = Death of the Enterprise Service Bus (ESB)?Kai Wähner
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. Continuous Integration and Continuous Delivery control deployments. This way you get shorter time to results and increased flexibility.
Microservices have to be independent regarding build, deployment, data management and business domains. A solid Microservices design requires single responsibility, loose coupling and a decentralized architecture. A Microservice can to be closed or open to partners and public via APIs.
This session discusses the requirements, best practices and challenges for creating a good Microservices architecture, and if this spells the end of the Enterprise Service Bus (ESB).
Key messages of the talk:
• Microservices = SOA done right
• Integration is key for success – the product name does not matter
• Real time event correlation is the game changer
How iPaaS Overcomes the Challenges of Cloud IntegrationFlowgear
As enterprise IT infrastructure continues to move to the cloud, the need to safely and reliably integrate a wide range of on-premises and cloud systems becomes increasingly critical. However, traditional integration tools are inadequate for handling the complex integration challenges enterprise IT managers face when trying to manage cloud/ground data flow and link cloud-based services with on-premises legacy systems.
Discover how integration-platform-as-a-service (iPaaS) technology offers the most flexible, secure, and reliable way to easily integrate crucial on-premises systems with newer, cloud-based applications and services.
WSO2Con USA 2017: The Role of Enterprise Integration in Digital TransformationWSO2
Enterprise integration has been evolving for several decades and has been going through drastic changes. In this session, we focus on the future trends in enterprise integration and how WSO2 integration addresses these needs.
Overview of enterprise integration: past, present and the future
Integration Service: Is it an anti pattern in future enterprise architecture?
Importance of integration in modern enterprises
Integration beyond the ESB: integrating services, systems, data and identities
The role of integration in microservices, Internet of Things (IoT) and APIs
Redefining scaling and performance
Developer experience: visual modeling, debugging and tracing
Hybrid integration: on-premise, integration Platform as a Service (iPaaS) and iSaaS
Business need of IT systems to get integrated. Why legacy systems are feeling modern technologies like SOA can help them to keep alive by providing the integration solution.
Catalog Management in the Cloud: Two Years Intrail001
Presentation given at the Catalog Management Interest Group, ALA Annual Conference, June 25, 2016 by Stacie Traill and Betsy Friesen (University of Minnesota)
The libraries of the University of Minnesota system were early adopters of Ex Libris's Alma system, migrating in late 2013. In the two and a half years since migration, systems and metadata staff have learned much about the differences between managing a cloud-based, multi-tenant ILS and a locally-hosted server-based ILS. Presenters will discuss some of these differences, along with issues they faced in adopting a new system early in its development cycle. In addition, they will provide an overview of the highlights, challenges, and ongoing evolution of Alma's catalog management tools and functionality (such as authority control and batch processing capabilities).
WSO2Con USA 2017: Implement an Effective Digital Platform Using WSO2 IntegrationWSO2
The WSO2 integration platform offers a high performance, lean, enterprise-ready solution to solve integration and innovation challenges faced by connected businesses. This platform offers modern integration technologies that empower enterprises to build a digital business by seamlessly connecting mobile apps, services, multiple data repositories, social media, and cloud and on-premise systems. This is all done to enhance your customers’ experience and increase internal productivity.
One of the primary focuses in modern integration is to think in terms of the network-effect in terms of reliability in resilience, scalability, affordability, and adaptability. The session will focus on
Under the hood: Integration server architecture
Mediation catalog
Architectural styles for integration
Enhancing
Hybrid integration with WSO2
Debugging and troubleshooting your integration
Deployment
Performance tuning
Production hardening
WSO2Con ASIA 2016: Iterative Architecture: Your Path to On-Time DeliveryWSO2
Enterprises today operate in complex and competitive markets. They are constantly trying to optimize business functions, introduce new business capabilities and tap into new markets quickly and efficiently. For the business to be agile, software systems that are used to provide business capability need to be agile. The ability to build and integrate new capability in a short time becomes valuable. At the same time, enterprise software systems should help with evolutionary as well as revolutionary changes that will affect core business functions.
In this session we will discuss iterative architecture, which is about taking an iterative approach when introducing architectural changes to support business and technical requirements. We’ll also look at real world examples of implementing architectures in iterations.
Original interactive slides here: http://slides.com/yunzhilin/microservices-and-friends#/
A tongue-in-cheek presentation to TrunkPlatform interns 2015.
WSO2Con ASIA 2016: Understanding Microservice ArchitectureWSO2
Today many organizations are leveraging microservice architecture (MSA), which is becoming increasingly popular because of its many potential advantages. MSA itself is divided into two areas – inner and outer architectures – which require separate attention. Moreover, MSA requires a certain level of developer and devops experience too. This talk will be an awareness session about MSA and will also discuss WSO2′s strategic initiatives in both the platform level and WSO2 MSF4J framework level.
Governance in the ever-changing PowerBI world for the organization
Best practices
deployment recommendations
Security settings
Reporting on the reports and optimizations
*According to all the new features and capabilities as by March 2019, will probably change again very soon.
This is a must-read for all engineers interested in developing a Micro services architecture. Turn your monolithic server into a prolific and multiple instance solution! Includes well-known example such as Netflix. Please contact me for more details.
I Love APIs 2015: Building Predictive Apps with Lamda and MicroServices Apigee | Google Cloud
I Love APIs 2015
Machine learning, big data, and API technologies have drastically reduced the complexity of building predictive apps. But all these advances also mean that these apps require a new approach to system architecture. This talk discusses the lamda architecture and microservices, and best practices on decomposing your app into batch, near-realtime, an real-time services. Learn how Apigee uses both new architectures to implement predictive apps using Hadoop, Node.js, Cassandra, and ElasticSearch.
Every enterprise has a multitude of existing systems - including on-premise as well as cloud solutions - that perform critical functions. Integrating data and services across these systems is critical for an enterprise to successfully implement its digital transformation efforts. Therefore, most often than not, enterprise integration is at the heart of any organization’s digital transformation strategy.
WSO2Con USA 2017: Implementing a Modern API Management Solution that Benefits...WSO2
A few years ago, Brigham Young University (BYU) started a massive effort to replace the existing API management systems with a more modern, standard, and efficient solution. WSO2 products such as WSO2 API Manager and WSO2 Identity Server are at the core of this new solution. They expected to improve consumer experience and minimize the impact on existing development work. Along the way, they hit a few roadblocks including problems such as integrating with legacy systems, improving API discoverability changing authentication mechanisms, and re-designing API development and deployment processes.
This session will explore how they overcame these roadblocks by using the WSO2 products will discuss how they
Integrated new the API management solution with legacy systems via API mediation
Standardized API documentation across the organization
Improved API search and discoverability for consumers
Made API consumption simple by following industry standards
Web- and Mobile-Oriented Architectures with Oracle Fusion Middleware (OOW 2014)Lucas Jellema
Mobile applications as well as a large class of modern HTML5 web applications are built on top of an architecture with special provisions, such as RESTful services; the personal cloud, to provide a cross-device experience; push; cache; localization; scalability; and secure interaction with the enterprise back end. Gartner refers to this as the web-oriented architecture. Oracle Fusion Middleware offers key products (Oracle SOA Suite, Oracle Identity Management, and Oracle API Gateway) to implement this architecture, possibly in combination with cloud services such as Oracle Mobile Cloud Service, Oracle Messaging Cloud Service, and Oracle Storage Cloud Service. This session discusses the architecture itself and what it entails.
Riak Search is a distributed data indexing and search platform built on top of Riak. The talk will introduce Riak Search, covering overall goals, architecture, and core functionality, with specific focus on how Erlang is used to manage and execute an ever-changing population of ad hoc query processes.
ElasticSearch - index server used as a document databaseRobert Lujo
Presentation held on 5.10.2014 on http://2014.webcampzg.org/talks/.
Although ElasticSearch (ES) primary purpose is to be used as index/search server, in its featureset ES overlaps with common NoSql database; better to say, document database.
Why this could be interesting and how this could be used effectively?
Talk overview:
- ES - history, background, philosophy, featureset overview, focus on indexing/search features
- short presentation on how to get started - installation, indexing and search/retrieving
- Database should provide following functions: store, search, retrieve -> differences between relational, document and search databases
- it is not unusual to use ES additionally as an document database (store and retrieve)
- an use-case will be presented where ES can be used as a single database in the system (benefits and drawbacks)
- what if a relational database is introduced in previosly demonstrated system (benefits and drawbacks)
ES is a nice and in reality ready-to-use example that can change perspective of development of some type of software systems.
Complex Legacy System Archiving/Data Retention with MongoDB and XqueryDATAVERSITY
Many organizations today, due to regulatory compliance or other needs, are finding it necessary to archive large volumes of data into long-term storage. Learn how MongoDB provides a flexible, efficient, scalable, long-term document storage that can adapt to your organization's changing needs over time. A case study from US federal government agency with 130 legacy applications that needed to be archived and integrated into a federated view of archive and real-time operational data. Regulations in many industries (eg HIPAA, SOX, Basel 3, FATCA etc) are driving the need for data retention and the need for query processing across archives and operational data.
Your smartphone needs a spring cleaning, too. There's a lot of important stuff on your phone, but there are probably a few things you can get rid of as well. Between apps you haven't opened since you downloaded them to photos that are better off in the cloud, here's a roundup of our favorite ways to clear the digital clutter.
Scalable XQuery Processing with Zorba on top of MongoDBWilliam Candillon
Since a couple of years, the NoSQL movement has developed a variety of open-source document stores. Most of them focus on high availability, horizontal scalability, and are designed to run on commodity hardware. These products have gained great traction in the industry to store large amounts of flexible data (mostly JSON). In the meantime, XQuery has evolved to a standardized, full-fledged programming language for XML with native support for complex queries, indexes, updates, full-text search, and scripting. Moreover, JSON has recently been added as a first-level datatype into the language. As of today, it is without doubt the most robust and productive technology to process flexible data.
The aim of this talk is to showcase the benefits that can be achieved by integrating the Zorba XQuery Processor with MongoDB. We will introduce the 28msec platform that seamlessly stores, indexes, and manages flexible data entirely in XQuery. The data itself is stored in MongoDB. The platform leverages MongoDB’s indexes, sharding, and consistency guarantees to scale-out horizontally. The talk will conclude by showing a benchmark of the platform and discuss perspectives of the outlined approach.
Cloud computing has been on the rise, and it is going to be increasingly explosive in the next few years. If you are considering adopting cloud computing as one of your business strategies, don't forget to analyze its pros and cons to make the right decision.
Presented by Wes Caldwell, Chief Architect, ISS, Inc.
The customers in the Intelligence Community and Department of Defense that ISS services have a big data challenge. The sheer volume of data being produced and ultimately consumed by large enterprise systems has grown exponentially in a short amount of time. Providing analysts the ability to interpret meaning, and act on time-critical information is a top priority for ISS. In this session, we will explore our journey into building a search and discovery system for our customers that combines Solr, OpenNLP, and other open source technologies to enable analysts to "Shrink the Haystack" into actionable information.
Scaling Gilt: from Monolithic Ruby Application to Distributed Scala Micro-Ser...C4Media
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/10fVilQ.
Yoni Goldberg describes some of the technological innovations that have helped Gilt to reach its current size, and highlight some of the core challenges that the company's engineering team continues to face. He also discusses what every tech team needs to consider and address before heading down the path of building a first-class micro-services architecture. Filmed at qconnewyork.com.
Since joining Gilt at 2010 as a platform engineer, Yoni Goldberg has been leading a variety of personalization efforts and other customer-facing initiatives--including the Gilt Insider loyalty program, the post-purchase experience, and SEO/optimization efforts. Prior to joining Gilt, Yoni worked at Google, where he wrote his master's thesis on Fusion Tables.
Transforming Software Architecture for the 21st Century (September 2009)Dion Hinchcliffe
Evolving an important theme I've been working on and presenting all year, this new deck summarizes how enterprise architecture and large scale technology-based business solutions must transform to be more effective in the 21st century.
Contains material on a hypothesis for what's wrong with today's EA as well as potential solutions of merit such as emergent architecture, WOA, enterprise REST, open supply chains (APIs), mashups, and other models.
Presented this week in Oslo Norway to Bouvet's enterprise architecture council.
Reto 2.0 Webcast: The Emerging Technical And Business Models Of Web 2.0guest1f8bd34
This is the deck for the Reto 2.0 Webcast today and includes a whole overview of Web 2.0 as well as next-generation distribution models such as Open APIs, widgets, mashups, etc.
The third generation of the World Wide Web is referred as Web 3.0 or Web3. It is a concept for a decentralised, open, and more useful Web that is still under development. The key ideas of decentralisation, openness, and increased user utility are the foundations around which Web 3.0 development is based. Check it out for more info!
Consumer to Data: Next-Generation Middleware and Cloud Platform for your Ente...WSO2
To view recording of this webinar please use the below URL:
http://wso2.com/library/webinars/2015/08/consumer-to-data-next-generation-middleware-and-cloud-platform-for-your-enterprise/
One of WSO2's biggest strengths is its 100% open source, unified, modular platform for middleware. In this webinar, Asanka Abeysinghe, vice president of solutions architecture at WSO2, will explain the motivation, design, and capability of this platform. Asanka will also look at customer examples and address how the platform is used in real life.
He will discuss
An evolution of the platform (Platform 3.0)
Capabilities of the platform (system of systems)
Why a unified platform leads to a faster and more cost-effective implementation (data to consumer)
How other organizations have benefited from the WSO2 platform (reference architectures)
The session is aimed at CxOs and enterprise architects interested in integration, rapid application development, APIs, identity, analytics and the Cloud.
In this SOA workshop in Colombo, Sri Lanka (September 17, 2009), Paul Fremantle, CTO and Co-Founder, WSO2 presented about SOA and discussed why SOA is the basis of all modern Enterprise Architecture.
Driving Enterprise Architecture Redesign: Cloud-Native Platforms, APIs, and D...WSO2
Chris Haddad examines,
Why you should consider Cloud-Native architecture components in your Enterprise Architecture.
What is DevOps impact on App and API design guidelines.
How API-centric focus revises Enterprise Architecture.
Driving Enterprise Architecture Redesign: Cloud-Native Platforms, APIs, and D...Chris Haddad
High performance architecture is rapidly changing due to three fundamental drivers:
Cloud-Native Platforms - change the way we think about operational infrastructure
DevOps - changes application lifecycle practices
APIs - change how we integrate and evolve infrastructure and applications, especially Mobile apps
In this session, Chris will illustrate:
Why you should consider Cloud-Native architecture components in your Enterprise Architecture
What is DevOps impact on App and API design guidelines
How API-centric focus revises Enterprise Architecture
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
4. An issue of complexity
• Developers have resolved most
architectural issues historically by:
– Choosing the right data structures;
– Identifying or creating algorithms, and;
– By applying the concept of separation of
concerns.
5. The network
began to
further
complicate
the issue
6. Integration has become a
dominant, top-level activity
• “Research has shown that more than
30 percent of IT spending is on
integration” – Bitpipe
• “Integration consumes more than 40%
of IT resources” – Aberdeen Group
report
• “Software integration is up to 60% of
enterprise software projects.” - Oracle
7. SOA Definition
• SOA is a modular software architecture, and
the modules are services designed to interact
with each other.
– Important Note: SOA also contains higher order
constructs such as composite applications,
orchestration, coordination, and more exist.
• SOAs are usually based on open standards to
encourage automatic interoperability of
services designed separately.
8. A Central Goal of SOA:
Turning Applications Into Open
Platforms
• Openly exposing the features of software and data to customers,
end-users, partners, and suppliers for reuse and remixing
• This strategy requires documenting, encouraging, and actively
supporting the application as a platform
– Has serious governance implications
• Provide legal, technical, and business reasons to enable this :
– Fair licensing, pricing, & support models
– A vast array of services that provide data that uses need
– A way to apply these services to business problems rapidly and
inexpensively.
9. But existing SOA models
have been challenged
• Most SOA initiatives are delivering low ROI to the
business
• The reasons are many but boil down to:
– SOA technologies have proven to have challenges compared to
more successful models.
– Top-down enterprise architecture moves slower than the
environment changes.
– Important avenues of SOA consumption and production points
were often excluded from participation.
• SOA is still, however, the dominant organizing model for enterprise
architecture.
10. Key trends on the Web today
• The growth of networked services
with highly valuable open and
“portable” data .
• Users by the tens of millions putting
modular Web parts on their blogs
and user profiles to host the pieces
of the Web that they want to share.
• Businesses connecting to each other
over the Internet via Web services by
the hundreds of thousands.
• The increasing realization that there
is limited business value in single
applications…
11. The Openness of 2.0 Apps
• Building open platforms instead of stand-alone
applications
• Forming self-distributing ecosystems
• Spreading products far beyond the boundaries of a site
• APIs, widgets, badges, syndication -> mashups
• In other words: Being everywhere else on the network
• Building on the shoulder of giants
• Offering and consuming widgets, libraries, and APIs
• The automated mass servicing of markets of low
demand content and functionality (The Long Tail)
• Which represents the bulk of the demand
12. The Global SOA has surpassed our
enterprise SOAs
• Some businesses have
hundreds of thousands of
users of their SOA
• Most are using WOA models
for this
• Hundreds of companies
have opened their SOA to
the Web
– Mostly startups or established
Internet companies that
understand the Web
– But larger companies are
beginning to understand this.
13. Examples
• Amazon and their highly successful Web Services Division
(with hundreds of thousands of business consumers of their
global SOA)
– Over $300 million in revenue last year
• Google and its numerous and varied open Web APIs from
Google Maps to Open Social
• eBay and billions of dollars in listings it generates through its
public SOA
• Applications like Twitter.com
– Gets 10 times the use through its APIs than from its user interface.
– A new generation of applications that are primarily used via their Global SOA presence.
• Netflixprize.com, Gold Corp, and many others
14. WOA is for enterprises too
• Classical SOA is holding it’s own but is
not growing
• SOAP is in decline, with 54% planned use
last year to 42% planned use this year
• Reported enterprise use of REST grew
from 14% last year to 24% over the same
timeframe.
• Source: 2009 Information Week study.
18. The motive force of 2.0:
Harnessing the intrinsic power of networks
• “Networked applications that explicitly
leverage network effects.” – Tim O’Reilly
• A network effect is when a good or service
has more value the more than other people
have it too.
• Two-way participation is the classic litmus
test of a Web 2.0 system.
19. Demand for Widespread
Cross-Organization Integration
• “48 percent of the
CIOs we surveyed
said that they plan
to implement
service-oriented
architectures for
integration with
external trading
partners this year.”
– McKinsey & Co.
20. And we now have real-world
experience with traditional SOA
• Classical SOA was an
excellent first try but
has a long list of
challenges for the
outcomes we desire
today.
• The model of the Web
has continued to
teach us about how to
structure information
and services.
21.
22. Strange Attractors: Similarities
between Web 2.0 and SOA
• Web 2.0 • SOA
– Software as a service – Software as services
– Interoperability based on – Interoperability based on
Web principles heavyweight standards
– Applications as platforms – Applications as platforms
– Encourages unintended uses – Permits unintended uses
– Mashups – Composite Apps
– Little user interface
– Rich user interfaces guidance
– Architecture of Participation – Little prescription of
network participation
24. Enabling New
Consumption Scenarios
• Cut-and-Paste
deployment anywhere
on the Intranet
• Consumption of the
SOA in any
application that can
use a URL
• Discovery of data via
search
• Integration moves out
of the spreadsheet
25. Next Generation Enterprises
Are Leveraging Web 2.0
• A change in the way the Web is being used
• Innovative new customer interactions that
shifts most control to users (partners,
suppliers)
– Control over software, data, structure, and
processes
• Pervasive, viral, social and technical activities
that embrace the intrinsic power of networks
• Driven by a move from push to pull-based
systems
29. Example: Amazon
• 1st Gen. Product: E-commerce store
– No differentiation
– Scaling of a single site
– Single site
• 2nd Gen. Product: E-commerce platform
– 55,000 partners using their e-commerce APIs live
– Scaling of the Web S3
• 3rd Gen. Product: A series of Web platforms
– Simple Storage Service (S3) EC2
– Elastic Compute Cloud (EC2)
– Mechanical Turk (Mturk)
– Many others
– 300K businesses build on top of what they’ve produced
• 2nd and 3rd generation platforms generate large net revenue
30. The New Philosophy of
Product Distribution
• Jakob's Law states that "users
spend most of their time using
other people’s sites."
• You must design your products
and services to leverage this fact
deeply in the core of their design.
32. The Structure of the Web
• HTTP is the foundational protocol
• When HTTP is used to transport
hypertext, it can use links to refer to
other parts of the Web
• These links are defined, like HTTP, by a
standard and are known formally as
URIs:
– http://tools.ietf.org/html/rfc3986
33. URIs according to w3.org
• Uniform Resource Identifiers (URIs, aka URLs)
are short strings that identify resources in the
Web:
– documents, images, downloadable files, services,
electronic mailboxes, and other resources.
• They make resources available under a variety
of naming schemes and access methods such
as HTTP, FTP, and Internet mail addressable in
the same simple way. They reduce the tedium
of "log in to this server, then issue this magic
command ..." down to a single click.
35. The use of HTTP has evolved
extensively…
• There is no limit to the kind of data that can be
transferred via HTTP
– HTTP was originally used for transferring Web pages, images,
and other simple resources
– But now it’s used to transfer pages, data, programs, video
streams, and virtually everything else
• There is no limit to the amount of data that can be
transferred via HTTP
– Server-side push of HTTP data is now possible by technique
• Has proven to be highly secure and scale to global use
41. WSDL
• Web Service Description Language
• Lists operations, services, data types so
that other platforms can learn how to
interact with the service
– Like an interface in Java, but cross platform
• Data types are described by XML
Schemas (XSD)
• Forms the service “contract”
43. More on WSDL
• Can be complex (even huge)
– WSDL is obtuse
• WS-* specifications are far from
pervasive thus services are often not
actually interoperable
48. RESTful Services
• Representation State Transfer
– Roy Fielding coined the term for his thesis
which sought to provide the architectural
basis for HTTP
• But what is REST exactly?
49. It’s all about resources
• In REST, everything on the network is a
resource
– Resources are addressable via URIs
– Resources are self descriptive
– Typically through content types (“application/
xml”) and sometimes the resource body (i.e. an
XML QName)
• Resources are stateless
• Resources are manipulated via HTTP verbs
and the uniform interface
50.
51. Hypertext and linking
• We don’t want “keys”, we want links!
• Resources are hypertext
– Hypertext is just data with links to other resources
• Data model refers to other application states via
links
• This is possible because of the uniform interface.
• Key Point: There is no need to know different ways
to get different types of entities!
• Client can simply navigate to different resources
• The uniform interface allowing different types
greatly lowers the barrier to consumption.
52. Getting a network resource
• GET is safe
– If original GET fails, just try, try again
• Note that not all HTTP resources follow
this rule properly
– The rule: Be liberal in what you accept and
strict in what you transmit
53.
54.
55. HTTP is scalable
• Just look at the size of WWW today
• HTTP has built in mechanisms for caching
resources
– All communication is stateless
– Session state is kept on the Client
• Client is responsible for transitioning to
new states
• States are represented by URIs
56. Basic Guidelines
• Information is stored as resources (like a Web page)
instead of a traditional RPC Web service.
• Every resource can be located via a globally unique
address known as a Universal Resource Identifier.
• Resources are manipulated by HTTP verbs (GET, PUT,
POST, DELETE)
• Manipulation of network resources is performed solely
by components on the network (essentially browsers
and other Web servers).
• Access to resources must be layered and not require
more than local knowledge of the network.
• Full details at: http://hinchcliffe.org/archive/
2008/02/27/16617.aspx
57. Advantages to REST
• Linkability: Everything is accessible and addressable via
a simple URL
– Countless benefits from discoverability to consumption to
analytics and link ecosystems
• Simplicity (easy to provide/consume)
• Uniform interface
• Testable via a browser
• No WSDL or traditional service contracts
– Allows minimal surface area contract checking (more on
this)
• Is easily consumed by dynamic languages such as
Javascript or Ruby
• High performance: Works well with caches
59. Is WOA just REST?
• REST is the foundational network protocol for WOA
• WOA also includes a set of consumption models including
such things as mashups and Web widgets (explored here
later)
• WOA also includes a set of widely-used standards and
technologies for data representation, data exchange and
portability that REST itself does not encompass, but is
necessary for a proper and complete architectural
definition.
– http://dataportability.com is a partial list of the “other” WOA
standards. It is not canonical given that WOA is emergent
and not defined by a vendor or standards body.
• Identity, security, Web applications model, new distribution
models are not accounted for by REST alone either.
61. Is WOA also SOA?
• Yes, it follows all the
basic tenets of SOA
including the 8
principles
• So good SOA, and
perhaps the best SOA,
can be implemented
with WOA
62. Differences with traditional SOA #1
• SOAs tend to have a small and well-
defined set of endpoints through which
many types of data and data instances
can pass.
• WOAs tend to have a very large and open-
ended number of endpoints; one for each
individual resource. Not an endpoint for
each type of resource, but a URI-identified
endpoint for each and every resource
instance.
63. Differences with traditional SOA #2
• Traditional SOA builds a messaging
layer above HTTP using SOAP and WS-
* that provides unique and sometimes
prohibitive constraints to the Web
developer.
• WOA finds HTTP and related transfer
mechanisms to be the ideal layer of
abstraction for most applications.
64. Differences with traditional SOA #3
• SOA was designed from the top-down
by vendors to be tool friendly
• WOA was emerged from the bottom up
from the Web developer community
naturally. It has the best support in
simple procedural code and an XML
parser and is widely support by modern
Web stacks.
65. Differences with traditional SOA #4
• SOA uses WS-Security and other
sophisticated standards for security,
while WOA tends to just use HTTPS,
OAuth, and HMAC-SHA-1.
66. Differences with traditional SOA #4
• SOA uses WS-Security and other
sophisticated standards for security,
while WOA tends to just use HTTPS,
OAuth, and HMAC-SHA-1.
68. State Representation
• XML is most common
• JSON is becoming very popular
• YAML - http://yaml.org
• Fast Infoset - http://java.sun.com/
developer/technicalArticles/xml/
fastinfoset/
• http://jsonml.org/
69. What is a “mashup”?
• “A mashup is a Web site or Web application
that seamlessly combines content from more
than one source into an integrated
experience.” - Wikipedia
• Content used in mashups is usually sourced
from a 3rd party via a public interface (API)
• Other methods of sourcing content for
mashups include Web feeds (e.g. RSS or
Atom), and JavaScript/Flash “widgets”
73. The Focus:
Rapid Business Solutions
• Full resources of the
Web and the Intranet
• Enterprise context
around management,
security, privacy, etc.
• Gives everyone in the
organization the ability
to leverage the SOA.
• Lightweight, simple
model using WOA.
74. Why is Web-Oriented Architecture
Important for Mashups?
• The most commonly used Web service
approaches “in the wild” turn out to be the ones
based on the “grain” of the Web:
– Representation State Transfer, or REST.
• Created by Roy Fielding, the co-creator of HTTP, the
fundamental protocol of the Web.
• Designed to fit naturally into Internet architecture
• Extremely simple, not a standard, just a style of using HTTP
• Fully embraces the workings of HTTP and uses its verbs
(GET, PUT, POST, DELETE) on top of a granular, sensical
URL structure to indicate what is to happen.
– RSS and ATOM
• ATOM is REST
75. What does an organization
with WOA “look” like?
• A rich web of REST resources.
• Simple tools to weave the Web of
resources into new applications.
• Highly consumable and reusable WOA
“parts” including widgets, gadgets, and
embedded social apps.
Open Web APIs exposed on the Internet to
ad hoc partners.
76. Major Opportunities in 2009
• Strategically move IT
infrastructure to the cloud.
• Embrace new low-cost
economic models for SOA.
• Reduce application
development and
integration time/
expenditures with new
platforms and techniques.
• Open your supply chain to
partners on the Web.
77. WOA Conclusions
• WOA is already the dominant model for networked
applications today
• But it has largely emerged under the radar (no big
vendors behind it)
• WOA can enable the richest possible outcomes on
the network
– And it’s probably the shortest route to get there.
– When in doubt, ask “What would the Web do?”
• Transition of tools, techniques, and architectural
styles is required by most practitioners.
78. Wrap-up:
Questions?
For Slides:
dion@hinchcliffeandco.com