The document discusses microservices and API management. It defines microservices as small, independent processes communicating via APIs to compose complex applications. Benefits include improved modularity, scalability, and fault isolation. API management provides tools to publish, secure, monitor, and analyze APIs. It allows enterprises to expose APIs internally or externally in a controlled manner. The document outlines considerations around microservices and features of API management systems.
[WSO2Con EU 2017] Resilience Patterns with BallerinaWSO2
Today almost all systems are distributed and have complex interactions between each other to provide useful functionality. In a software system, resilience is the ability to recover to a working condition after being affected by a serious incident. Ballerina has inbuilt functionality to make programs resilient for network failures. This slide deck explores how to build resilience patterns with Ballerina.
Often business stakeholders are confused about choosing the right Open source Portal and CMS. Not only that the confusion prevails on the actual understanding of a Portal and CMS. Liferay and Drupal are one of the most popular Portal and CMS platforms. This presentation helps business stakeholders choose the right Portal and CMS platform.
Modern Microservices Architecture with DockerEran Stiller
Microservices are all the rage these days. Docker is a tool which makes managing Microservices a whole lot easier. But what do Microservices really mean? What are the best practices of composing your application with Microservices? How can you leverage Docker and the public cloud to help you build a more agile DevOps process? How does the Azure Container Service fit in? Join us to find out the answer.
[WSO2Con EU 2017] Resilience Patterns with BallerinaWSO2
Today almost all systems are distributed and have complex interactions between each other to provide useful functionality. In a software system, resilience is the ability to recover to a working condition after being affected by a serious incident. Ballerina has inbuilt functionality to make programs resilient for network failures. This slide deck explores how to build resilience patterns with Ballerina.
Often business stakeholders are confused about choosing the right Open source Portal and CMS. Not only that the confusion prevails on the actual understanding of a Portal and CMS. Liferay and Drupal are one of the most popular Portal and CMS platforms. This presentation helps business stakeholders choose the right Portal and CMS platform.
Modern Microservices Architecture with DockerEran Stiller
Microservices are all the rage these days. Docker is a tool which makes managing Microservices a whole lot easier. But what do Microservices really mean? What are the best practices of composing your application with Microservices? How can you leverage Docker and the public cloud to help you build a more agile DevOps process? How does the Azure Container Service fit in? Join us to find out the answer.
The Liferay 7 meetup organized by Azilen Technologies on 21st May, 2016 was undeniably a successful Meetup. Brief Overview given by Ravi Gupta & Hetal Prajapati on Liferay 7 Technology. Find here Presentation.
Document gives overview of Microservices and how Websphere commerce can be leveraged as microservices. It gives pros and cons of various approaches and challanges.
WebSphere Message Broker In Shared Runtime EnvironmentsMårten Gustafson
WebSphere Message Broker in shared runtime environments.
Typical environment configurations and common set-ups with regards to high availability and workload balancing.
What kind of solutions do we see implemented on top of message broker what are the demands for these solutions in terms of availability and isolation?
How do we cater for these needs in a shared runtime environment?
Also takes a look at the organization developing solutions targeting a shared runtime environment and how different organizations pose different requirements and challenges.
Presentation given at IBM Transaction & Messaging conference in Barcelon 2008.
Presentation held by Mr.Goce Bogatinov and Mr. Jordan Tikvesanski as a part of the - Cooperation between academia and ICT businesses Session at the 8th SEEITA and 7th MASIT Open Days Conference, 14th-15th October, 2010
An overview of liferay portal.
The outline is:
1.> Review Liferay Portal
– Enterprise Layer
– Extensions Framework
– Logical Architecture of Liferay
– Service layer
– Service Builder
– Web services
– Persistence Layer
– User Management: Organization, Site, User, Roles, Groups
2.> Out of the box features
– Document and Media Library
• Image Management
• Document Management
– Web Content Management
– Asset, Tagging, and Categorization
Liferay DXP Presentation
As presented during the session, this is the compatibility matrix that you need to check before integrating Liferay
If you have any questions, feel free to contact me on :
My Linkedin Profile : https://www.linkedin.com/in/elyesmakhlouf
My Email Address : makhloufelyes@gmail.com
My Blog : elyesmakhlouf.blogspot.com
From Monoliths to Services: Grafually paying your Technical DebtDavid Litvak Bruno
Talk about how to improve the architecture and reduce the technical debt of your applications. By gradually separating away responsibilities from your monolithic apps into single responsibility services.
Keynote presentation by IBM Distinguished Engineer and Chief Technology Officer of Java John Duimovich and IBM Vice President of Cloud Platform Development Tim Vanderham at JavaOne 2015.
Presentation on CM WebClient, the Ajax HTML generator for CA Plex. Updated for version 1.8, including Mobile Device Generation, New Themes, Portals/Portlets, Cloud, and more.
Liferay DevCon 2014: Lliferay Platform - A new and exciting visionJorge Ferrer
Liferay is very well known as a good platform for building portals. It provides a nice combination of out of the box features, extensibility and application development options to build almost any website, portal or complex application without starting from scratch every time. But is that all it can do?
For a few years the development world has been focusing more and more on developing for mobile and tablets, glasses and TVs or even provide public web APIs for any developers to build on top of a company’s services and content. And we have noticed “There isn’t a Liferay for those developers!”, most of that type development is started from scratch, “What if Liferay filled that gap?”
During this talk we will show how the most recent developments of the Liferay team are building a more versatile and modular platform than ever, an environment to leverage the most modern frontend development tools for enterprise needs, a set of tools to build mobile apps (for any device) with a powerful backend in a tenth of the time it typically takes. And all of it Open Source and fully standards based.
The Liferay 7 meetup organized by Azilen Technologies on 21st May, 2016 was undeniably a successful Meetup. Brief Overview given by Ravi Gupta & Hetal Prajapati on Liferay 7 Technology. Find here Presentation.
Document gives overview of Microservices and how Websphere commerce can be leveraged as microservices. It gives pros and cons of various approaches and challanges.
WebSphere Message Broker In Shared Runtime EnvironmentsMårten Gustafson
WebSphere Message Broker in shared runtime environments.
Typical environment configurations and common set-ups with regards to high availability and workload balancing.
What kind of solutions do we see implemented on top of message broker what are the demands for these solutions in terms of availability and isolation?
How do we cater for these needs in a shared runtime environment?
Also takes a look at the organization developing solutions targeting a shared runtime environment and how different organizations pose different requirements and challenges.
Presentation given at IBM Transaction & Messaging conference in Barcelon 2008.
Presentation held by Mr.Goce Bogatinov and Mr. Jordan Tikvesanski as a part of the - Cooperation between academia and ICT businesses Session at the 8th SEEITA and 7th MASIT Open Days Conference, 14th-15th October, 2010
An overview of liferay portal.
The outline is:
1.> Review Liferay Portal
– Enterprise Layer
– Extensions Framework
– Logical Architecture of Liferay
– Service layer
– Service Builder
– Web services
– Persistence Layer
– User Management: Organization, Site, User, Roles, Groups
2.> Out of the box features
– Document and Media Library
• Image Management
• Document Management
– Web Content Management
– Asset, Tagging, and Categorization
Liferay DXP Presentation
As presented during the session, this is the compatibility matrix that you need to check before integrating Liferay
If you have any questions, feel free to contact me on :
My Linkedin Profile : https://www.linkedin.com/in/elyesmakhlouf
My Email Address : makhloufelyes@gmail.com
My Blog : elyesmakhlouf.blogspot.com
From Monoliths to Services: Grafually paying your Technical DebtDavid Litvak Bruno
Talk about how to improve the architecture and reduce the technical debt of your applications. By gradually separating away responsibilities from your monolithic apps into single responsibility services.
Keynote presentation by IBM Distinguished Engineer and Chief Technology Officer of Java John Duimovich and IBM Vice President of Cloud Platform Development Tim Vanderham at JavaOne 2015.
Presentation on CM WebClient, the Ajax HTML generator for CA Plex. Updated for version 1.8, including Mobile Device Generation, New Themes, Portals/Portlets, Cloud, and more.
Liferay DevCon 2014: Lliferay Platform - A new and exciting visionJorge Ferrer
Liferay is very well known as a good platform for building portals. It provides a nice combination of out of the box features, extensibility and application development options to build almost any website, portal or complex application without starting from scratch every time. But is that all it can do?
For a few years the development world has been focusing more and more on developing for mobile and tablets, glasses and TVs or even provide public web APIs for any developers to build on top of a company’s services and content. And we have noticed “There isn’t a Liferay for those developers!”, most of that type development is started from scratch, “What if Liferay filled that gap?”
During this talk we will show how the most recent developments of the Liferay team are building a more versatile and modular platform than ever, an environment to leverage the most modern frontend development tools for enterprise needs, a set of tools to build mobile apps (for any device) with a powerful backend in a tenth of the time it typically takes. And all of it Open Source and fully standards based.
How does social media impact the contact centre and visa versa? An overview of why every business needs to integrate these functions and some tips on how to do so well.
MKT 571 Final Exam Answers
1) Which of the following is most closely associated with a proactive marketing orientation?
A. It involves delivering superior value.
B. It is about understanding and meeting customers’ expressed needs.
C. It represents the “make and sell” philosophy.
D. The marketer focuses on the customers’ latent or hidden needs.
2) Marketing __________ is the art and science of choosing target markets and getting, keeping, and growing customers through creating, delivering, and communicating superior customer value.
A. internally
B. management
C. segmentation
D. integration
3) Business buyers ______________.
A. are geographically as diverse as consumers
B. tend to be geographically concentrated with over half of them in seven states
C. are largely concentrated in the southwestern United States
D. use geographical dispersion to keep shipping costs low
4) Toyota, the maker of the Scion brand, is using what kind of brand strategy wi
2015 - HCBS National Conference
Panel Presentation on how three states are leveraging the benefits of MLTSS to meet the needs of individuals receiving home and community based services through Medicaid.
Enterprise API : Best practice for World class API ecosystem is an attempt on my part to explain the best practice in deploying API infrastructure in the organization.
As soon as we start working on an API, architecture issues arise. Many mistaken common beliefs turn out to be fiction in this area. A poorly designed API architecture will lead to misuse or – even worse – not be used at all by its intended clients: application developers.
To facilitate and accelerate design and development of your APIs, we share our vision and beliefs with you in this Reference Card. They come from our direct experience on API projects.
Learn what APIs and Microservices are and how they are different. After all, together they power some of the most amazing applications on the internet. https://www.webguru-india.com/blog/apis-and-microservices-what-are-they/
Understanding API Architectures: Web API vs. Minimal API – An In-Depth Compar...Polyxer Systems
In this comprehensive guide learn the distinctions between Web API & Minimal API for your project understanding and get detailed insights on framework differences, benefits & limits.
Building enterprise depth APIs with the IBM hybrid integration portfolioKim Clark
APIs are fast becoming central to the way that an enterprise presents itself to partners and customers, enabling innovation and automation. A well crafted API is today's front page advertisement for your enterprise's capabilities, but there must be substance beneath the API, for it to fulfil its promise. Success beyond initial launch of the API rides upon many factors.
In this talk we'll focus on the architectural elements that need to be considered in order to ensure the API will be secure, scalable, agile to change, manageable and maintainable. Along the way we will discuss how to leverage the sweet spots of IBM's hybrid integration portfolio to make your API initiative more productive, and maintainable into the future.
Taking Control of Your Future: Own Your Service PlatformsAlan Quayle
Taking Control of Your Future: Own Your Service Platforms
Presented at TADSummit Lisbon, 18th November 2015
Antonio Cruz
Software Architect &
Project Manager
SAPO (Portugal Telecom)
Quantifying the business success achieved with SAPO’s Service Delivery Broker. Explaining the importance of owning the platform to control your future.
App modernization projects are hard. Enterprises are looking to cloud-native platforms like Pivotal Cloud Foundry to run their applications, but they’re worried about the risks inherent to any replatforming effort.
Fortunately, several repeatable patterns of successful incremental migration have emerged.
In this webcast, Google Cloud’s Prithpal Bhogill and Pivotal’s Shaun Anderson will discuss best practices for app modernization and securely and seamlessly routing traffic between legacy stacks and Pivotal Cloud Foundry.
API Development involves designing, building, and implementing Application Programming Interfaces (APIs) that enable seamless communication and data exchange between different software systems. There are various types of APIs, including RESTful APIs, SOAP APIs, GraphQL, and WebSocket APIs, each serving specific purposes. API specifications, such as OpenAPI Specification (OAS) and GraphQL Schema Definition Language (SDL), define the structure and behavior of APIs. Documentation plays a crucial role in API development, providing clear instructions, examples, and troubleshooting guidance for developers who want to integrate with the API.
Click Here For More Details: https://www.connectinfosoft.com/rest-api-development-service/
Apigee is an API development and management platform which offers an overlay or interface for your core service APIs by presenting them with a proxy layer. This enables security, rate limitation, quotas, and analytics, among other features.
Apigee is the main source of API capabilities and procedures for producers at the moment. Programming Interface Management describes the processes and tools that enable an organization to operate and administer its APIs. It controls how the entrance is routed to the backend management and how the response is returned.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
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.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
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/
3. Agenda
1. Microservices
I. Need for Microservices
II. Definition
III. Function & Features
IV. Microservices vs SOA
V. Areas of caution
2. API management
I. API and how its used ?
II. API management function & features
III. Examples
4. Need for Microservices
In Monolithic Architecture the large monolithic code base intimidates developers,
especially ones who are new to the team. The application can be difficult to
understand and modify. As a result, development typically slows down
There are not hard module boundaries, modularity breaks down over time, to
implement a change or to deploy new versions of services frequently is difficult and
the quality of the code declines over time
Overloaded IDE - the larger the code base the slower the IDE and the less productive
developers are
Requires a long-term commitment to a technology stack
Fault isolation was required. one misbehaving component of a monolithic architecture
can bring down the entire system
5. Definition
Microservices is a software architecture style in which complex applications are
composed of small, independent processes communicating with each other using
language-agnostic APIs.
These services are small, highly decoupled and focus on doing a small
task, facilitating a modular approach to system-building.
These services are built around business capabilities and independently deployable
by fully automated deployment machinery.
6. Microservices
Architect the application by functionally decomposing it into a set of collaborating
services. Each service implements a set of narrowly, related functions.
Services communicate using either synchronous protocols such as HTTP/REST or
asynchronous protocols such as AMQP.
Services are developed and deployed independently of one another.
Each service has its own database in order to be decoupled from other services. When
necessary, consistency is between databases is maintained using either database
replication mechanisms or application-level events.
8. The services are easy to replace
Services are organized around capabilities, e.g. user interface front-end,
recommendation, logistics, billing, etc.
Services can be implemented using different programming languages, databases,
hardware and software environment, depending on what fits best
Architectures are symmetrical rather than hierarchical (producer - consumer)
Microservices Features
9. Microservices vs SOA
Microservices must be independently deployable, whereas SOA services are often
implemented in deployment monoliths.
Classic SOA is more platform driven, so microservices offer more choices in all
dimensions
Services in micro-service systems are smaller than most of those in SOA designs,
but most importantly micro services are stand-alone and are a manifestation of
the Single responsibility principle.
A service in SOA may have many responsibilities and thus may be as hard to evolve
as any monolithic application.
SOA initially started with XML/WSDL, but microservice architecture uses REST api.
12. Areas of Caution
Developers must deal with the additional complexity of creating a distributed
system.
Testing is more difficult
Deployment complexity for different service types.
Increased memory consumption.
The tangled dependencies might make it difficult to decompose your
monolithic application into a set of services.
14. API
Application programming interface (API) is a set of routines, protocols, and tools
for building software applications. An API expresses a software component in
terms of its operations, inputs, outputs, and underlying types.
15. API
A good API makes it easier to develop a program by providing all the building
blocks. A programmer then puts the blocks together.
APIs do all this by "exposing" some of a program's internal functions to the outside
world in a limited fashion.
An API specification can take many forms, including an International Standard, such
as POSIX, vendor documentation, such as the Microsoft Windows API, or
the libraries of a programming language, e.g., the Standard Template
Library in C++ or the Java APIs.
16. How API is used?
API in procedural languages: API specifies a set of functions or routines that
accomplish a specific task or are allowed to interact with a specific software
component
API in object-oriented languages: is a description of how objects work in a given
object-oriented language expressed as a set of classes with an associated list of class
methods
API libraries and frameworks: An API can also be related to a software framework a
framework can be based on several libraries implementing several APIs
API and protocols: When an API implements a protocol it can be based on proxy
methods for remote invocations that underneath rely on the communication
protocol
The role of the API can be exactly to hide the detail of the transport protocol
17. API Management
API management is a system in which an enterprise publishes application
programming interfaces (APIs) in a secure environment. The enterprise maintains
the APIs in a registry and exposes them to consumers inside or outside the
enterprise.
18. API Management Functions
API management software tools typically provide the following functions:
Automate and control connections between an API and the applications
that use it
Ensure consistency between multiple API implementations and versions
Monitor traffic from individual apps
Provide memory management and caching mechanisms to improve
application performance
Protect the API from misuse by wrapping it in security procedures and
policies
19. API Management Features
Documentation – Sounds boring, right? Still, one of the most common problems of
developers is figuring out how an API works. An API management service has to provide
an easy way to read the documentation and enable developers to “try before they buy”.
Analytics and Statistics – It is critical to understand how people use your API and get
insights for your business.
Deployment – Should be flexible and support public or private clouds, on-premises
implementations, or combinations.
Developer engagement – Engaging with your API consumers, developer or partners is
important. Getting an easily accessible developer portal will significantly facilitate
onboarding.
20. API Management Features
Sandbox environment – This feature will increase both the value of an API and
its adoption rate. What better than being able to develop and test your code.
Traffic management and caching abilities.
Security – APIs carry sensitive data, so it is important to protect the exposed
information. The service has to at least provide identity and access
management for users and developers.
Monetization – Provide the capability to monetize your API.
Availability – Should be available, scalable and redundant. An API environment
can become demanding and the service should be able to deal with any kind of
errors, problems or temporary traffic spikes.
Support of Legacy systems.
21. API Examples
The developer of a game app, for instance, can use the Dropbox API to let users
store their saved games in the Dropbox cloud
Sign In into many apps and Web sites using their Facebook ID—a feature that
relies upon Facebook APIs
Companies can shut down services and APIs that your applications depend on—or
they can go out of business entirely like Google regularly shuts down when it
doesn't see any profit in them—like Google Health or more recently, Google
Reader.