The document discusses delivery strategies for new apps. It covers how IT has evolved from a monopoly controlled by a few organizations to a democratized free market with many options. This disruption has benefits for businesses but is challenging for traditional enterprise IT. The document examines how monopolies were once useful for undertaking large projects but can become problematic by restricting innovation over time. Today, computing power is widely available at low costs, marking a shift from when machines were expensive and humans were cheap.
The document discusses key considerations for designing a successful software-as-a-service (SaaS) enterprise. It recommends adopting a single-instance, multi-tenant architecture from the beginning to reduce costs. It also emphasizes the importance of automation and best practices for onboarding, monitoring, security, support, and operations to deliver a high-quality customer experience.
Open Architecture for Developing Multitenant Software-as-a-Service ApplicationsJavier Mijail Espadas Pech
As cloud computing infrastructures are growing, in terms of usage, its requirements about software design, management and deployment are increasing as well. Software-as-a-Service (SaaS) platforms play a key role within this cloud environment. SaaS, as a part of the cloud offer, allows to the software providers to deploy and manage their own applications in the clouds in a subscription basis. The problem with the current SaaS offers is the lack of openness of in their platforms and the need for learning a whole new paradigm when trying to initiate in the SaaS market. Big players, such as: Amazon, Google or Microsoft, offer their proprietary SaaS solutions. Another consideration is the amount of current Web applications that need to be re-engineered into this cloud paradigm. This research work aims to reduce the effort required to enter into the SaaS market by presenting an architecture based on open source components for developing, deploying and managing SaaS applications.
The document discusses the testing life cycle process. It involves testing activities from the beginning of a project through requirements, design, development, integration testing, system testing, and release. Key phases include test planning, case design, execution, and using various testing types and tools. An effective testing team has defined roles and responsibilities throughout the project life cycle.
Les Hazlewood, Stormpath co-founder and CTO and the Apache Shiro PMC Chair demonstrates how to design a beautiful REST + JSON API. Includes the principles of RESTful design, how REST differs from XML, tips for increasing adoption of your API, and security concerns.
Presentation video: https://www.youtube.com/watch?v=5WXYw4J4QOU
More info: http://www.stormpath.com/blog/designing-rest-json-apis
Further reading: http://www.stormpath.com/blog
Sign up for Stormpath: https://api.stormpath.com/register
Stormpath is a user management and authentication service for developers. By offloading user management and authentication to Stormpath, developers can bring applications to market faster, reduce development costs, and protect their users. Easy and secure, the flexible cloud service can manage millions of users with a scalable pricing model.
- The document discusses quality assurance in the software development lifecycle, including key concepts, practices, and challenges.
- It defines quality assurance, software development lifecycle phases, and differences between verification and validation. Common testing types like unit, integration, and non-functional testing are also covered.
- The document then describes quality assurance practices used in industry, such as creating QA plans, requirements reviews, test case development, and validation activities at different stages. Finally, challenges of quality assurance are discussed around testing focus, cost of fixes, schedules, and career opportunities.
The document provides an overview of quality assurance and software testing processes. It describes key concepts like requirements gathering, test planning, test case development, defect reporting, retesting and sign off. It also covers quality standards, software development life cycles, testing methodologies, documentation artifacts, and project management structures.
The document discusses the history and evolution of cloud computing. It explains how computing transitioned from being an expensive monopoly controlled by IT, to becoming more affordable, flexible and driven by user needs. Virtualization played a key role by allowing more efficient use of hardware and enabling automation. Now cloud platforms aim to provide on-demand, self-service computing resources that can adapt based on user demands.
The document provides a history of cloud computing and virtualization. It discusses how computing transitioned from being an expensive monopoly controlled by IT, to becoming more affordable and accessible to businesses and individuals. This was enabled by technologies like client-server computing, the web browser, mobility, and most recently cloud computing. The document also covers the history of virtualization, how it allows more efficient use of hardware by running multiple workloads on a single machine, and how this led to portability, ephemeral deployments, and increased automation of IT systems.
Layering Mobile Onto Your Online ExperienceDay Software
You have less than 7 seconds to make an impression and the Web is no longer limited to merely your browser. With the advent of smartphones and tablet devices, you need to engage your audience at anywhere, at anytime. How do you create a consistent and easy-to-use online presence across the web and mobile? Find out how CQ5 lets you do this easily from one fun-to-use interface.
Cedric Huesler, Product Marketing Director, Day Software
The document discusses various topics related to online tools, technologies, and skills, including building online polls and maps, remixing content, location-aware web and mobile technologies, user skills reports, search engine optimization, analytics data, and engaging with collective intelligence on the web. It also references the origins and mission of the Open University to bring degree-level education to those without access to traditional universities through communications technologies.
The document discusses designing mobile web experiences. It begins by noting that while some devices like the iPhone are popular, the overall penetration of smartphones remains relatively low globally. It then examines the diversity of mobile devices and browsers in use. The document argues for an adaptive approach that works across different browsers and devices, using techniques like responsive design with media queries. It provides guidelines for mobile-friendly development, such as using semantic HTML, limiting animations for performance, and structuring CSS to deliver the right styles for each device type. The goal is to make the mobile web accessible to all users, not just those with specific devices.
The document is a presentation about how product management has changed with the rise of cloud computing and analytics. It discusses how these technologies have made experimentation easier and faster by reducing upfront costs and improving measurement. Product managers are now able to conduct many parallel experiments in production and gain real-time feedback on what works, rather than relying on justification, surveys or roadmaps. This new approach favors learning over planning and emphasizes discovering what doesn't work rather than getting features perfectly right.
The document discusses how open source and sharing of scientific data is important, especially for issues like climate change. It says that raw data should always be released with full transparency on how it was collected. The processing methods, assumptions, and limitations should be explained clearly, and code should be rewritten from scratch by others to avoid biases. Overall it promotes full transparency and independent verification in scientific research.
Another version of my talk about the state of the Internet Operating System, but this one focused on how it will affect business intelligence. Given at Greenplum Days in Las Vegas, held in conjunction with the Gartner BI Summit.
If your job is to make things for the web, and the company you work for doesn’t build fitness trackers, or robots, or smart light bulbs, or a cloud service that aims to connect all these things, you could be forgiven for not caring all that much about today's Internet of Things. My aim with this talk is to shift the conversation away from things and back to people. In doing so, I hope to also arm you with tools to better understand, and find your place, within this complex but fascinating landscape.
First presented at Generate Conference in San Francisco on July 15, 2016.
Open Source in the Cloud Computing EraTim O'Reilly
While open source software plays an important role in many cloud applications, we need to understand where the cloud is taking us or we'll find ourselves in the grip of a new monopoly. Open source needs to get serious about building interoperable open data services - they are the operating system of the internet.
Tim O'Reilly discusses the concept of "Government as a Platform" where government opens up access to its data and services to citizens and developers. This allows citizens and third parties to build innovative applications on top of the platform to increase transparency, collaboration, and problem solving. The key aspects of this model are open data, social media engagement of citizens, and prioritizing the creation of useful government services over preferred contractors.
Henry Story: Philosophy and the Social WebPhiloWeb
1. The document discusses social networks and how they function similarly to Jeremy Bentham's Panopticon, with network operators able to see all user connections and data, while users only see a limited view of their own networks.
2. It notes how users can leave social networks, but at the cost of losing access to their data and connections with friends. Each social network operates as a "data silo" where information cannot be ported to other networks.
3. The document argues that a more open system is needed where users have portable profiles and globally unique identifiers, similar to systems used for telephone numbers, email addresses and web domains. This would allow borderless communication across networks.
The document discusses how technology trends are revolutionizing business and encourages embracing change. It highlights how the internet has empowered people as content creators and participants, and how social media has changed crisis communications and given everyone a voice. New forms of user-generated content like Wikipedia and YouTube are discussed. The document envisions a future where video communication is prevalent and allows people to have immersive experiences together across distances as if they were together in person.
The document discusses the rise of mobile devices and their potential for museums. It notes that over half the global population now owns a mobile phone and smartphones are increasingly popular. The document outlines several options for museums to engage mobile audiences, including adapting existing websites, developing separate mobile sites or apps, or creating mobile web apps. It argues that mobile offers opportunities to provide contextual, ubiquitous experiences and engage visitors both on-site and off-site.
Top 10 Things Steve Ballmer tells his Closest Friends about Microsoft’s Share...Mark Fidelman
We've have it on great authority; from a friend of a friend who knows someone who might be a close friend of Ballmer (we think Steve Ballmer) that the following is what he tells them.
Mobile Monday Atlanta Aug10 2009v2 ShortEd Pimentel
MobileMonday Atlanta Relaunches and partners with GTRI Georgia-Tech-Reasearch-Institute to accelerate startups and foster economic growth in GA(Greater Atlanta Area)
The document discusses complexity in Drupal and other software ecosystems using an analogy to biological ecosystems and the platypus. It argues that software like Drupal evolves in unpredictable ways due to contributions from many independent actors. This results in emergent complexity that is difficult to plan for but can be understood by viewing the software as a dynamic, interdependent ecosystem. The post encourages understanding complexity rather than ignoring it, and adapting to changes by studying the habitat and key contributors that software depends on.
Similar to Delivery strategies: Apps don't deploy themselves (20)
Book as api hugh mc guire and alistair croll - toc nyc 2013Alistair Croll
1. The document discusses the idea of books as bundles of content, structure, and format that should adapt to how they are being used.
2. It argues that the concept of a fixed "publication date" is misleading given that book content is constantly shifting, and books must be linked to outside information in the age of big data.
3. The future of books is seen as their application programming interface (API) that separates content from structure, allowing the two to evolve independently and be recombined in new ways.
1) The document discusses how big data provides both opportunities and challenges for society. It can be used for good by improving healthcare, philanthropy, and cities, but also for bad by eroding privacy, justifying prejudices, and leaking private truths.
2) People are not good at objectively analyzing big data and often make mistakes like mistaking correlation for causation. They also tend to ignore new evidence that contradicts their preexisting views.
3) Legacy companies that could best capitalize on big data often struggle to change and innovate due to existing habits and resistance to change within the organization. Radical disruption may require having nothing to lose and changing how change itself is approached.
Savvis Symphony is a cloud computing platform that offers virtual private data centers (VPDCs) with flexible, on-demand provisioning of compute and storage resources. It provides an enterprise-grade infrastructure across Savvis' 31 data centers with options for customized service levels and scalable resources. VPDCs can be provisioned through an intuitive portal in minutes to host a variety of application types and workloads. The platform aims to enable hybrid cloud solutions through multi-tiered security profiles and the ability to extend or burst workloads between on-premise and cloud environments.
Amazon Web Services provides cloud computing services to customers in 190 countries, focusing on security, operational excellence, flexibility and choice, innovation, and lowering costs. AWS has a global infrastructure with regions in the US, Europe, Asia Pacific, and South America. It offers a variety of computing, storage, database, application services and has over 30 services available. AWS aims to rapidly innovate based on customer feedback by continuously adding new services and features weekly/monthly while also lowering prices over time to help customers compete globally.
Cloud computing brings together maturing technology and new delivery models to address workloads in three emerging models: private cloud within organizations, public cloud outside organizations, and community clouds sharing resources. Cost savings and faster time to value are leading reasons for considering cloud. Applicable workloads include those benefiting from flexibility, rapid time to market, and innovation. Risks need assessment for sensitive workloads. IBM offers cloud services structured in analytics, collaboration, development and test, infrastructure, and business services.
The document provides an overview of various Google cloud computing services including Google App Engine, Google Storage, Google Prediction API, BigQuery, Google SQL Service, Google Fusion Tables, and Google Refine. It discusses the services and how they fit into the categories of SaaS, PaaS, and IaaS. It also provides details on App Engine, Storage, and new App Engine features for data analysis like the Mapper, Channel, and Matcher APIs.
CloudOps evening presentation from Salesforce.comAlistair Croll
Peter Coffee, VP and Head of Platform Research at Salesforce, discussed building business apps on the Force.com platform. Force.com provides developers with tools to build scalable apps faster and at lower costs compared to traditional platforms. It offers capabilities such as visual process design, business rules, social business processes, and real-time device interactions. Force.com also enables secure communities and social business through its security and sharing models.
This document discusses how cloud computing is transforming enterprise IT and data centers. It begins by providing background on cloud computing and how it enables utility computing. There are two main models of cloud computing: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). IaaS involves renting virtual infrastructure like virtual machines, while PaaS involves deploying code to a shared cloud platform and paying for only the resources used. The document explores how these models work and their differences.
20-minute speed-run presentation on what metrics and web analytics information startups need to collect. Focuses on companies with a lean methodology, and the kinds of data that will actually help them achieve product/market fit before the money runs out.
The document discusses the history and development of a new technology called blockchain. Blockchain was originally developed for cryptocurrencies like Bitcoin as a way to record transactions in a secure, decentralized manner without the need for a central authority. It has since grown in popularity and found applications beyond digital currencies, with many industries now exploring how blockchain could be used to improve areas like supply chain management, digital identity, and financial transactions.
This document discusses the democratization of information technology and the increasing accessibility of cloud computing resources over time. It notes several conferences and publications from 2008 to 2010 focusing on the growth of cloud computing and its impact on web businesses and performance. The document suggests that IT is becoming more accessible to everyone through clouds.
Public clouds go mainstream - october 19 - 10mAlistair Croll
The document discusses the evolution and growth of cloud computing from 2008 to the present. It notes that clouds have become mainstream, with hybrid models combining public, private, and on-premise resources becoming the norm. The document outlines how cloud taxonomies and models have developed over time, from initial definitions to strategies for using clouds. It predicts that hybrid approaches will dominate as not all workloads can fully transition to the cloud. The concluding section advises assessing workloads based on their technical suitability for the cloud and business case for migration in order to determine the best approach.
Private clouds and enterprise it - october 18 - 30mAlistair Croll
The document discusses private clouds and enterprise IT. It makes two main points. First, there may be a return to more centralized IT models as public clouds become more capable of supporting complex enterprise workloads. Second, we are addicted to old metaphors for technology and clouds will likely not resemble the common metaphors of "cloudbursting" or simple cloud hosting. The reality for enterprises will be hybrid cloud models that combine on-premise and on-demand services tailored to specific workloads and policies.
Cloud 101 - Workshop from Gov2.0 in DC, May 2010Alistair Croll
The document provides an overview of cloud computing by discussing key topics across six parts:
Part one discusses how cloud computing has disrupted IT by democratizing access. Part two covers the history of virtualization. Part three explains how cloud stacks separate concerns between physical infrastructure, virtual platforms, and applications. Part four frames clouds as an on-demand business model compared to traditional IT. Part five outlines the major types of cloud services including IaaS, PaaS and differences between them. Finally, part six notes that in reality, most cloud offerings blend aspects of infrastructure, platforms and software as a service.
The document discusses topics related to community monitoring and analytics. It mentions vendor relationship management, social credibility in advertising, the decline of press releases, and centralized portals. It then outlines various metrics that may be audited for community efforts, including reputation, page rank, visits, followers, conversions, revenue, problems averted, feature adoption, call volumes, and CRM metrics. It discusses tying online visits to user identities, aggregating and segmenting analytics data, and experimenting with message delivery and monitoring spread. Tracking outcomes and responding is also mentioned.
Data Protection in a Connected World: Sovereignty and Cyber Securityanupriti
Delve into the critical intersection of data sovereignty and cyber security in this presentation. Explore unconventional cyber threat vectors and strategies to safeguard data integrity and sovereignty in an increasingly interconnected world. Gain insights into emerging threats and proactive defense measures essential for modern digital ecosystems.
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
AC Atlassian Coimbatore Session Slides( 22/06/2024)apoorva2579
This is the combined Sessions of ACE Atlassian Coimbatore event happened on 22nd June 2024
The session order is as follows:
1.AI and future of help desk by Rajesh Shanmugam
2. Harnessing the power of GenAI for your business by Siddharth
3. Fallacies of GenAI by Raju Kandaswamy
How to Avoid Learning the Linux-Kernel Memory ModelScyllaDB
The Linux-kernel memory model (LKMM) is a powerful tool for developing highly concurrent Linux-kernel code, but it also has a steep learning curve. Wouldn't it be great to get most of LKMM's benefits without the learning curve?
This talk will describe how to do exactly that by using the standard Linux-kernel APIs (locking, reference counting, RCU) along with a simple rules of thumb, thus gaining most of LKMM's power with less learning. And the full LKMM is always there when you need it!
MYIR Product Brochure - A Global Provider of Embedded SOMs & SolutionsLinda Zhang
This brochure gives introduction of MYIR Electronics company and MYIR's products and services.
MYIR Electronics Limited (MYIR for short), established in 2011, is a global provider of embedded System-On-Modules (SOMs) and
comprehensive solutions based on various architectures such as ARM, FPGA, RISC-V, and AI. We cater to customers' needs for large-scale production, offering customized design, industry-specific application solutions, and one-stop OEM services.
MYIR, recognized as a national high-tech enterprise, is also listed among the "Specialized
and Special new" Enterprises in Shenzhen, China. Our core belief is that "Our success stems from our customers' success" and embraces the philosophy
of "Make Your Idea Real, then My Idea Realizing!"
What Not to Document and Why_ (North Bay Python 2024)Margaret Fero
We’re hopefully all on board with writing documentation for our projects. However, especially with the rise of supply-chain attacks, there are some aspects of our projects that we really shouldn’t document, and should instead remediate as vulnerabilities. If we do document these aspects of a project, it may help someone compromise the project itself or our users. In this talk, you will learn why some aspects of documentation may help attackers more than users, how to recognize those aspects in your own projects, and what to do when you encounter such an issue.
These are slides as presented at North Bay Python 2024, with one minor modification to add the URL of a tweet screenshotted in the presentation.
Scaling Connections in PostgreSQL Postgres Bangalore(PGBLR) Meetup-2 - MydbopsMydbops
This presentation, delivered at the Postgres Bangalore (PGBLR) Meetup-2 on June 29th, 2024, dives deep into connection pooling for PostgreSQL databases. Aakash M, a PostgreSQL Tech Lead at Mydbops, explores the challenges of managing numerous connections and explains how connection pooling optimizes performance and resource utilization.
Key Takeaways:
* Understand why connection pooling is essential for high-traffic applications
* Explore various connection poolers available for PostgreSQL, including pgbouncer
* Learn the configuration options and functionalities of pgbouncer
* Discover best practices for monitoring and troubleshooting connection pooling setups
* Gain insights into real-world use cases and considerations for production environments
This presentation is ideal for:
* Database administrators (DBAs)
* Developers working with PostgreSQL
* DevOps engineers
* Anyone interested in optimizing PostgreSQL performance
Contact info@mydbops.com for PostgreSQL Managed, Consulting and Remote DBA Services
Details of description part II: Describing images in practice - Tech Forum 2024BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and transcript: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
Implementations of Fused Deposition Modeling in real worldEmerging Tech
The presentation showcases the diverse real-world applications of Fused Deposition Modeling (FDM) across multiple industries:
1. **Manufacturing**: FDM is utilized in manufacturing for rapid prototyping, creating custom tools and fixtures, and producing functional end-use parts. Companies leverage its cost-effectiveness and flexibility to streamline production processes.
2. **Medical**: In the medical field, FDM is used to create patient-specific anatomical models, surgical guides, and prosthetics. Its ability to produce precise and biocompatible parts supports advancements in personalized healthcare solutions.
3. **Education**: FDM plays a crucial role in education by enabling students to learn about design and engineering through hands-on 3D printing projects. It promotes innovation and practical skill development in STEM disciplines.
4. **Science**: Researchers use FDM to prototype equipment for scientific experiments, build custom laboratory tools, and create models for visualization and testing purposes. It facilitates rapid iteration and customization in scientific endeavors.
5. **Automotive**: Automotive manufacturers employ FDM for prototyping vehicle components, tooling for assembly lines, and customized parts. It speeds up the design validation process and enhances efficiency in automotive engineering.
6. **Consumer Electronics**: FDM is utilized in consumer electronics for designing and prototyping product enclosures, casings, and internal components. It enables rapid iteration and customization to meet evolving consumer demands.
7. **Robotics**: Robotics engineers leverage FDM to prototype robot parts, create lightweight and durable components, and customize robot designs for specific applications. It supports innovation and optimization in robotic systems.
8. **Aerospace**: In aerospace, FDM is used to manufacture lightweight parts, complex geometries, and prototypes of aircraft components. It contributes to cost reduction, faster production cycles, and weight savings in aerospace engineering.
9. **Architecture**: Architects utilize FDM for creating detailed architectural models, prototypes of building components, and intricate designs. It aids in visualizing concepts, testing structural integrity, and communicating design ideas effectively.
Each industry example demonstrates how FDM enhances innovation, accelerates product development, and addresses specific challenges through advanced manufacturing capabilities.
this resume for sadika shaikh bca studentSadikaShaikh7
I am a dedicated BCA student with a strong foundation in web technologies, including PHP and MySQL. I have hands-on experience in Java and Python, and a solid understanding of data structures. My technical skills are complemented by my ability to learn quickly and adapt to new challenges in the ever-evolving field of computer science.
Blockchain and Cyber Defense Strategies in new genre timesanupriti
Explore robust defense strategies at the intersection of blockchain technology and cybersecurity. This presentation delves into proactive measures and innovative approaches to safeguarding blockchain networks against evolving cyber threats. Discover how secure blockchain implementations can enhance resilience, protect data integrity, and ensure trust in digital transactions. Gain insights into cutting-edge security protocols and best practices essential for mitigating risks in the blockchain ecosystem.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
What's Next Web Development Trends to Watch.pdfSeasiaInfotech2
Explore the latest advancements and upcoming innovations in web development with our guide to the trends shaping the future of digital experiences. Read our article today for more information.
Fluttercon 2024: Showing that you care about security - OpenSSF Scorecards fo...Chris Swan
Have you noticed the OpenSSF Scorecard badges on the official Dart and Flutter repos? It's Google's way of showing that they care about security. Practices such as pinning dependencies, branch protection, required reviews, continuous integration tests etc. are measured to provide a score and accompanying badge.
You can do the same for your projects, and this presentation will show you how, with an emphasis on the unique challenges that come up when working with Dart and Flutter.
The session will provide a walkthrough of the steps involved in securing a first repository, and then what it takes to repeat that process across an organization with multiple repos. It will also look at the ongoing maintenance involved once scorecards have been implemented, and how aspects of that maintenance can be better automated to minimize toil.
Are you interested in learning about creating an attractive website? Here it is! Take part in the challenge that will broaden your knowledge about creating cool websites! Don't miss this opportunity, only in "Redesign Challenge"!
INDIAN AIR FORCE FIGHTER PLANES LIST.pdfjackson110191
These fighter aircraft have uses outside of traditional combat situations. They are essential in defending India's territorial integrity, averting dangers, and delivering aid to those in need during natural calamities. Additionally, the IAF improves its interoperability and fortifies international military alliances by working together and conducting joint exercises with other air forces.
Interaction Latency: Square's User-Centric Mobile Performance MetricScyllaDB
Mobile performance metrics often take inspiration from the backend world and measure resource usage (CPU usage, memory usage, etc) and workload durations (how long a piece of code takes to run).
However, mobile apps are used by humans and the app performance directly impacts their experience, so we should primarily track user-centric mobile performance metrics. Following the lead of tech giants, the mobile industry at large is now adopting the tracking of app launch time and smoothness (jank during motion).
At Square, our customers spend most of their time in the app long after it's launched, and they don't scroll much, so app launch time and smoothness aren't critical metrics. What should we track instead?
This talk will introduce you to Interaction Latency, a user-centric mobile performance metric inspired from the Web Vital metric Interaction to Next Paint"" (web.dev/inp). We'll go over why apps need to track this, how to properly implement its tracking (it's tricky!), how to aggregate this metric and what thresholds you should target.
7. Photo by Alan Cleaver from his Flicker Freestock set. Thanks, Alan!
http://www.flickr.com/photos/alancleaver/2638883650/
Thursday, June 17, 2010
You’ll save money!
10. What we’ll cover
The democratization of IT
Understanding your constraints and goals
Possible delivery strategies
Thursday, June 17, 2010
11. 1950 1960 1970 1980 1990 2000 2010
Government
Military
Business
Hobbyist
Consumer Internet
Consumer lifestyle
Media
Thursday, June 17, 2010
Think about the evolution of computing.
12. Where’s the risk?
1970: 1980: 1990: 2000:
The right The right The right The right
hardware application integration adoption
Client-server Vendor
Web, SaaS, XML
architectures dominance
Enterprise
application adoption is
the new frontier
Thursday, June 17, 2010
13. Why this happened
Disruption and the democratization of IT
Thursday, June 17, 2010
20. http://www.flickr.com/photos/brewbooks/3319730327/
(16MB)
Thursday, June 17, 2010
First, the machines were expensive. That meant they were a scarce resource, and someone had to control what we could do with
them.
21. http://www.flickr.com/photos/argonne/4563394851/
Thursday, June 17, 2010
Second, they were complicated. It took a very strange sect of experts to understand them. AVIDAC, Argonne's first digital
computer, began operation in January 1953. It was built by the Physics Division for $250,000. Pictured is pioneer Argonne
computer scientist Jean F. Hall.
AVIDAC stands for "Argonne Version of the Institute's Digital Automatic Computer" and was based on the IAS architecture
developed by John von Neumann.
30. Thursday, June 17, 2010
For the most part, governments have a monopoly on roadwork, because it’s something we need, but the benefits are hard to
quantify or charge back for.
34. For much of its history, AT&T and its Bell System functioned as
a legally sanctioned, regulated monopoly.
The US accepted this principle, initially in a 1913 agreement
known as the Kingsbury Commitment.
Anti-trust suit filed in 1949 led in 1956 to a consent decree
whereby AT&T agreed to restrict its activities to the regulated
business of the national telephone system and government
work.
Changes in telecommunications led to a U.S. government
antitrust suit in 1974.
In 1982 when AT&T agreed to divest itself of the wholly owned
Bell operating companies that provided local exchange service.
In 1984 Bell was dead. In its place was a new AT&T and seven
regional Bell operating companies (collectively, the RBOCs.)
http://www.corp.att.com/history/history3.html
Thursday, June 17, 2010
When monopolies are created with a specific purpose, that’s good. But when they start to stagnate and restrict competition, we
break them apart.
35. http://www.flickr.com/photos/ktylerconk/4096965228/
Thursday, June 17, 2010
In fact, there’s a lot of antitrust regulation that prevents companies from controlling too much of something because they can
stifle innovation and charge whatever they want. That’s one of the things the DOJ does.
36. First: Monopoly good.
Thursday, June 17, 2010
In other words, early on monopolies are good because they let us undertake hugely beneficial, but largely unbillable, tasks.
37. Then: Monopoly bad.
Thursday, June 17, 2010
Later, however, they’re bad because they reduce the level of creativity and experimentation.
39. http://www.flickr.com/photos/mbrubeck/4460320021/
Thursday, June 17, 2010
It’s also not complicated. Everyone can use a computer. Because today, the computer is cheap and the human’s expensive we
spend so much time on user interfaces, from GUIs to augmented reality to touchscreens to voice control to geopresence.
44. Thursday, June 17, 2010
They can shop around—choosing SaaS, clouds, and internal IT according to their business requirements.
45. http://www.codeproject.com/KB/miscctrl/ScriptStudio.aspx Wufoo.com
Thursday, June 17, 2010
They’re increasingly able to build the applications themselves, but expect IT to deliver smooth, fast platforms on which to
experiment.
46. USERS
APPS
PLATFORMS
HARDWARE
Thursday, June 17, 2010
It’s an inversion of the traditional IT “pyramid”, where the hardware dictates the platforms, which in turn dictates, the apps,
which dictates what users can do.
47. USERS
APPS
PLATFORMS
HARDWARE
Thursday, June 17, 2010
Today, what users want to do drives the apps they use, which drives the platforms and the hardware.
48. Three really big changes.
Thursday, June 17, 2010
We’ve had big changes since that time. The first was client-server computing: the idea that
not everything lived in a mainframe, and some things worked well on the desktop. Software
like Visicalc—the first spreadsheet—were useful for businesses, even those who couldn’t
afford a mainframe.
49. http://www.flickr.com/photos/scriptingnews/3471500626/
Thursday, June 17, 2010
We’ve had big changes since that time. The first was client-server computing: the idea that
not everything lived in a mainframe, and some things worked well on the desktop. Software
like Visicalc—the first spreadsheet—were useful for businesses, even those who couldn’t
afford a mainframe.
50. http://en.wikipedia.org/wiki/File:NCSA_Mosaic.PNG
Thursday, June 17, 2010
A second big change was the Web. This browser-based model made computing accessible to
the masses. As a result, it became part of society, and everyone knew how to work it. These
days, you don’t have to teach a new hire how to use a web browser: they know what links do;
what the back button is; and so on.
51. !"#$%%&&&'()*+,'*-.%#!-/-0%#)1234566)*/%789:;7<=>%?
Thursday, June 17, 2010
A third change is the move to mobility. This has been bigger overseas, where the mobile
phone is the dominant way of accessing the Internet, but it’s still a shift to the always-
connected, always-on lifestyles we lead today.
52. Now here come clouds
Thursday, June 17, 2010
We’ve had big changes since that time. The first was client-server computing: the idea that
not everything lived in a mainframe, and some things worked well on the desktop. Software
like Visicalc—the first spreadsheet—were useful for businesses, even those who couldn’t
afford a mainframe.
55. Picking a delivery strategy
Identifying your constraints
Thursday, June 17, 2010
56. Square pegs
Does how your app will be used match the goals
you have for it?
Thursday, June 17, 2010
57. One to one One to many
http://exzanian.blogspot.com/2009/04/zuma-news-only-blip-on-world-radar.html
http://www.scottpargettphotography.com/images/photos/crowd.jpg
Thursday, June 17, 2010
First, think about the flow of communication and process. Is your intended use one-to-one,
or one-to-many?
58. !
Simple Detailed
Thursday, June 17, 2010
Then think about message complexity. Are you sending quick, brief information; or very
detailed data?
59. Community
Detailed Email Article
Blog
Private post
wiki
Forum Google
comment group
Forum
Linkedin post
IRC profile
change
Blog
comment
Complexity
Facebook
status
update
IM Twitter
Simple
One to one One to many
Thursday, June 17, 2010
Form follows function: The dimensions of enterprise software. The reality is that every kind of
interaction is unique. Some are private, one-to-one; others are open to everyone. Some are
brief snippets; others, detailed prose. Different apps are better for different kinds of
interaction; others won’t feel natural.
60. Operational constraints
What are the rules and limitations to consider?
Thursday, June 17, 2010
62. Figure 3 Interactive user productivity versus computer response time for human-intensive
interactions for system A
E 600
-
3
T -" INTERACTIVE USER PRODUCTIVITY (IUP)
w
-HUMAN-INTENSIVE COMPONENT OF IUP
7 MEASURED DATA (HUMAN-INTENSIVE
E 500 -
A
z " COMPONENT)
U
E
-
w
E 0
>
-
>
- -
400
3
n
F
2
0
0
300 -
200 -
100 -
0
0- I 1 I I I
0 1 2 3 4 5
COMPUTER RESPONSE TIME (SI
(1981) A. J. Thadhani, IBM Systems Journal, Volume 20, number 4
Thursday, June 17, 2010
There’s a study fromThe human-intensive component of IUP is computed by using between
IBM in 1981 that shows strong evidence of the relationship
performance and productivity.period 1 interactions, instead of all TSO interactions in more
completed As systems get faster, users get EXPONENTIALLY
productive. Equation 1.
When the number of logged-on users on the systemis small, it is
possible for afew users to have aninordinately large effect on the
aggregate user work, and hence bias theresults.To minimize
bias, all data with fewer than twenty-five logged-on users were
excluded from the analysis. Furthermore, to minimize the effect
of changes in the aggregate user work at different times of the
66. Thursday, June 17, 2010
Many SaaS providers are adding customization and scripting that blurs the lines of what’s a
cloud, and what’s an app, and what’s a programming language. Now that you can write code
for Google Apps -- as in this example of a script that sends custom driving directions to
everyone in a spreadsheet -- the distinction is less and less clear.
68. Standardized
Easy Impossible
Sloppy Easy
Tailored
Slow, Fast/lean, with
inefficient economies of scale
Thursday, June 17, 2010
Unfortunately, there’s a tradeoff here -- everyone wants fast, cheap, and customized. You
can only have two. The more tailored your IT systems are, the more you’ll be paying for them
and the slower they’ll be. At the same time, if you use the same applications and processes
as everyone else you may sacrifice important differentiators.
69. http://www.flickr.com/photos/andrewparnell/2738598951/
Thursday, June 17, 2010
An increasingly important criteria is the ability to connect existing systems to new ones.
Whether this is legacy applications (for authentication, data exchange, or single sign-on); or
to third-party customers and partners, the ability to link your systems to others is a huge
deal.
70. Thursday, June 17, 2010
This is one of the reasons a thriving ecosystem around a platform is so important -- because
it’s an indicator of ability to develop to the platform, as well as a starting point for integration
and extension.
71. http://www.flickr.com/photos/oobrien/7597395/
Thursday, June 17, 2010
Then there’s compliance and security. This may include geographic and legislative issues
(where you can put your data) as well as auditing and logging (some industries require
physical collection by a separate system.)
72. Security is a...
Reason to avoid clouds
23%
Reason to move to clouds
43%
No opinion
34%
http://www.thewhir.com/web-hosting-news/102309_IT_Firms_Skeptical_About_Cloud_PEER_1_Study
Thursday, June 17, 2010
This isn’t just about avoiding on-demand systems. The odds are good that many cloud
providers are better at security than you are.
73. Budget & operating
constraints
What can you afford to take on?
Thursday, June 17, 2010
74. Airfare
DNS
Cloud
Public
transit
Important
research
Hotel
Thursday, June 17, 2010
Affordability
75. Money spent
Point at which
it’s cheaper to
buy than rent
Time (years)
Thursday, June 17, 2010
The economics of renting versus buying apply here, too, since the investment is approaching
zero. The traditional way of looking at this is to compare an upfront investment to the rental
model of a lesser investment (integration, training) and a pay-as-you-go cost.
76. Money spent
Cheaper to rent
for longer
Time (years)
Thursday, June 17, 2010
Several things have changed in recent years in this respect. First, the upfront investment of a
pay-as-you-go model has dropped: everyone knows how to use a browser; everyone can
access things remotely; vendors have trial models; and so on. So it takes longer to get to the
point where it’s cheaper to run your own thing.
77. Unforeseen
costs of owning
Money spent
Time (years)
Thursday, June 17, 2010
There’s also the impact of owning things. Often, IT is a distraction; we make decisions based
on existing investments, which means we don’t change things when we can, which means we
become less agile.
78. Money spent
Efficiencies from
economies of
scale passed on
to customers
Time (years)
Thursday, June 17, 2010
There’s also the impact of owning things. Often, IT is a distraction; we make decisions based
on existing investments, which means we don’t change things when we can, which means we
become less agile.
79. 5 year planning horizon
6 months
Money spent
Payoff time
Time (years)
Thursday, June 17, 2010
But even if you ignore all of these, here’s why pay-as-you-go wins more and more often:
Your time horizon isn’t what it used to be. By the time you’ve paid off your in-house
investment, your business will have changed in order to adapt, and you’ll be after something
else.
80. Ease of adoption
How readily will your users take to it?
Thursday, June 17, 2010
81. Thursday, June 17, 2010
Existing standards: why do you know what to do here?
82. Thursday, June 17, 2010
Learning curve is okay; in fact, it’s recommended. Think what it would be like to have to use
a wizard every time you wanted to do something.
83. Thursday, June 17, 2010
Consider Excel: most beginners can grasp it easily; but it’s designed to allow experts to be
more productive. This is essential when evaluating how readily your user base will adopt
something -- not just on day one, but on day fifty, when they’re expected to be fast and
error-free.
84. http://www.flickr.com/photos/farhannasir/4577508824/
Thursday, June 17, 2010
Also consider the impact of mobility, and new platforms. Will your users be able to adopt the
application in all the places they work?
85. App/usage fit: Does app function match planned use?
Is the flow of information the right degree of open?
Do users work at the right degree of information detail?
Operational constraints
Will it perform fast enough to make users productive?
Can I customize it to my business without making it suck?
Can I connect it to myself and my partners?
Does it comply with legal, privacy, security requirements?
Budget & operating constraints
How does it embody new payment models (freemium, etc.)?
Do I understand the ROI & TCO of my chosen approach?
Ease of adoption
Does it use existing standards & conventions my users know?
Can first-timers use it, but experts be fast & efficient?
Will it work in mobile, disconnected, touch UI, etc.?
Thursday, June 17, 2010
Here’s a quick recap of the criteria we just saw.
86. Possible delivery strategies
Platforms & business models to choose from.
Thursday, June 17, 2010
Okay, now let’s look at some of the platforms and business models you can use for this.
87. Dedicated On-premise Virtual Third-party
hardware private clouds private clouds public clouds
Thursday, June 17, 2010
There’s a spectrum of platforms out there on which you can run an application.
88. Bare metal
(this is your computer)
Thursday, June 17, 2010
First, there’s bare metal.
95. http://www.flickr.com/photos/genewolf/147722350
Thursday, June 17, 2010
Which
inevitably
leads
to
automa3on
and
scrip3ng:
We
need
to
spin
up
and
down
machines,
and
move
them
from
place
to
place.
This
is
hard,
error-‐prone
work
for
humans,
but
perfect
for
automa3on
now
that
rack-‐and-‐stack
has
been
replaced
by
point-‐and-‐click
97. Virtualization divorces the app from the machine.
One on many (or) Many on one
Physical machine
Virtual machine
Virtual Virtual Virtual
Physical Physical Physical machine machine machine
machine machine machine
Virtual Virtual Virtual
Physical Physical Physical machine machine machine
machine machine machine
Thursday, June 17, 2010
Okay, so these things mean we have applications that run “virtually” – that is, they’re divorced
from the underlying hardware. One machine can do ten things; ten machines can do one
thing.
98. “Cloudy”
tech.
Thursday, June 17, 2010
These
are
the
founda7ons
on
which
new
IT
is
being
built.
Taken
together,
they’re
a
big
part
of
the
movement
towards
cloud
compu7ng,
whether
that’s
in
house
or
on-‐demand.
If
you
do
all
these
things,
you’re
running
what
many
people
call
a
“private
cloud”
99. Virtual private clouds
(feels like yours)
Thursday, June 17, 2010
If you like the virtualization, but don’t like having to carry a screwdriver around, virtual
private clouds may be right for you.
100. http://nature.wallpaperme.com/Nature-Historical-Buildings/Fairy+Tale+Fantasy_
+Neuschwanstein+Castle_+Bavaria_+Germany.jpg.html?g2_imageViewsIndex=1
Thursday, June 17, 2010
In this approach, you have a machine that feels like it’s your own -- complete with a private
IP address and so on. If you want to connect it to the Internet, you do so yourself; it’s just like
virtual infrastructure, but someone else is running it.
101. Infrastructure as a Service
Amazon EC2, Rackspace Cloud, Terremark,
Gogrid, Joyent (and nearly every private cloud
built on Zenserver or VMWare.)
Thursday, June 17, 2010
When IT people talk about cloud computing, they usually mean something called IaaS.
103. • 60 seconds per page
Desktop EC2 • 200 machine
Pages 17,481 17,481 instances
Minutes/page 1 1 • 1,407 hours of virtual
# of machines 1 200 machine time
Total minutes 17,481 • Searchable database
Total hours 291.4 26.0 available 26 hours
Total days 12.1 1.1 later
• $144.62 total cost
Thursday, June 17, 2010
A great example of these clouds in action is what the Washington Post did with Hillarly
Clinton’s diaries during her campaign. They needed to get all 17,481 pages of Hillary Clinton’s White House
schedule scanned and searchable quickly. Using 200 machines, the Post was able to get the data to reporters in only 26 hours. In
fact, the experiment is even more compelling: Desktop OCR took about 30 minutes per page to properly scan, read, resize, and
format each page – which means that it would have taken nearly a year, and cost $123 in power, to do the work on a single machine.
104. Machine Web
Image server
Machine instance
Thursday, June 17, 2010
In an IaaS model, you’re getting computers as a utility. The unit of the transaction is a virtual
machine. It’s still up to you to install an operating system, and software, or at least to choose
it from a list. You don’t really have a machine -- you have an image of one, and when you
stop the machine, it vanishes.
105. DB Machine
Storage
server Image
Machine instance
App Machine
Server Image
Machine instance
Web Machine
server Image
Machine instance
Thursday, June 17, 2010
Most applications consist of several machines -- web, app, and database, for example. Each
is created from an image, and some, like databases, may use other services from the cloud to
store and retrieve data from a disk
106. DB
Storage server
Machine instance
Bigger
App
machine
instance
Server
Machine instance
Web
server
Machine instance
Thursday, June 17, 2010
If you run out of capacity, you can upgrade to a bigger machine (which is called “scaling
vertically.”)
107. DB
Storage
server
Machine instance
App
Server
Machine instance
Web
server
Machine instance
Load
balancer
Machine instance
Thursday, June 17, 2010
Or you can create several machines at each tier, and use a load balancer to share traffic
between them. These kinds of scalable, redundant architectures are common -- nay,
recommended -- in a cloud computing world where everything is uncertain.
108. Platform as a Service
Google App Engine, Salesforce Force.com,
Rackspace Cloud Sites, Joyent Smart Platform,
(and nearly every enterprise mainframe.)
Thursday, June 17, 2010
The second kind of cloud is called Platform as a Service. In this model, you don’t think about
the individual machines—instead, you just copy your code to a cloud, and run it. You never
see the machines. In a PaaS cloud, things are very different.
109. Shared components
Data Processing platform
Storage
API
Others’ Others’
code code
User Auth
database API
Your Others’
code code
Image Image
functions API Others’ Others’
code code
...
Big Blob Governor Console Schedule
objects API
Thursday, June 17, 2010
- You write your code; often it needs some customization.
- That code runs on a share processing platform
- Along with other people’s code
- The code calls certain functions to do things like authenticate a user, handle a payment,
store an object, or move something to a CDN
- To keep everything running smoothly (and bill you) the platform has a scheduler (figuring
out what to do next) and a governor (ensuring one program doesn’t use up all the resources)
as well as a console.
115. http://www.flickr.com/photos/olitaillon/3354855989/
Thursday, June 17, 2010
This is a very different model from IaaS. On the one hand, it’s more liberating, because you
don’t have to worry about managing the machines. On the other hand, it’s more restrictive,
because you can only do what the PaaS lets you.
116. IaaS and PaaS differences
IaaS PaaS
Any operating system you Use only selected
want languages and built-in APIs
Limited by capacity of Limited by governors to
virtual machine avoid overloading
Scale by adding more Scaling is automatic
machines
Use built-in storage
Many storage options (file (Bigtable, etc.)
system, object, key-value)
Thursday, June 17, 2010
In the case of Google’s App Engine, you have to use their functions and store things in the
way they want you to. You get great performance from doing so, but it probably means
rewriting your code a bit.
117. Quota Limit
Governor Apps per developer 10
(usage cap) Time per request 30s
Blobstore (total file size) 1GB
Maximum HTTP response size 10MB
Datastore item size 1MB
Application code size 150MB
Daily cap Emails per day 1,500
(free quota) Bandwidth in per day 1 GB
Bandwidth out per day 1GB
CPU time per day 6.5h
HTTP requests per day 1,300,000
Datastore API calls per day 10,000,000
URLFetch API calls per day 657,084
http://en.wikipedia.org/wiki/Google_App_Engine
Thursday, June 17, 2010
PaaS platforms impose usage caps and billing tiers. Here’s Google App Engine’s set of quotas
and free caps.
119. Software as a Service
Salesforce.com, Google Apps, Microsoft Office
Live, pretty much any ISV still around today.
Thursday, June 17, 2010
The third kind of “cloud” app is really just a new software delivery model; I hesitate to call
them clouds at all, actually. It’s SaaS. And it’s what most people outside of IT think of as
“cloud computing.”
120. Thursday, June 17, 2010
The third kind of cloud is called Software as a Service, or SaaS. Some people argue that this
isn’t a cloud at all, just a new way of delivering software. But it’s also what the masses—the
non-technologists—think cloud computing means. The problem is that SaaS is pretty much
synonymous with “dynamic website” or “the Internet” these days. Nevertheless, if an ISV is
shipping software on discs still, their days are numbered.
121. How you pay for it
Lots of business models
Thursday, June 17, 2010
122. DIY
You can always write your own stuff.
Thursday, June 17, 2010
123. Open source
Standing on the shoulders of giants
Thursday, June 17, 2010
124. Github analysis by Franck Cuny: http://www.flickr.com/photos/franck_/sets/72157623447857405/
Thursday, June 17, 2010
Github is a great example of how social coding has transformed and revitalized the open
source world, particularly for high-level languages like Rails and Python.
125. Thursday, June 17, 2010
One last thought about building your own, rather than building it as part of a bigger
platform: Adoption is what matters. There’s a build-your-own dilemma: If you create a new
environment, you need to change users’ patterns.
126. Licensed
software
Oh, how quaint.
http://www.penneydesign.com/
folio_IM_retrogamesmodernthemes.html
Thursday, June 17, 2010
127. Freemium
And other sad, bad portmanteaux
Thursday, June 17, 2010
128. Collaborative Transactional
business business
model User creates model
content
Free Paid
Content becomes
Content remains
part of template
private
library
Engagement, Eventual
Revenues
SEO ranking conversion
Thursday, June 17, 2010
New freemium models for SaaS blend transactional and collaborative revenue approaches. In
this model, “free” users help build the corpus of templates, contributing to SEO ranking and
the richness of the offering; while paying users can keep their work private.
129. Composed application
Stitching together loosely coupled pieces
Thursday, June 17, 2010
133. Thursday, June 17, 2010
Whether it’s PaaS, SaaS, or IaaS, the model is the same: Sell IT on demand, rather than as
software or machines.
134. Adoption
The real risk when the app is a utility
Thursday, June 17, 2010
135. Thursday, June 17, 2010
The whole reason you deploy apps is so that you can focus on the things you do best:
whatever adds the most value to your business.
136. Thursday, June 17, 2010
You also deploy apps to handle processes you didn’t want to do yourself anyway.
137. “What information consumes is rather
obvious: it consumes the attention of its
recipients. Hence, a wealth of information
creates a poverty of attention and a need
to allocate that attention efficiently among
the overabundance of information sources
that might consume it.”
Herbert Simon
Thursday, June 17, 2010
The problem isn’t delivery: we have plenty of options for that. It’s adoption.
142. ATTENTION ENGAGEMENT CONVERSION
NEW
VISITORS
SEARCHES GROWTH CONVERSION
PAGES TIME RATE
TWEETS NUMBER
OF VISITS
PER ON x
MENTIONS VISIT SITE
GOAL
ADS SEEN LOSS VALUE
BOUNCE
RATE
Thursday, June 17, 2010
Here’s the simplest possible analytics model.
143. For transactional sites
Can people buy things?
Thursday, June 17, 2010
Remember the four kinds of sites? You need to analyze and optimize the app you’re
delivering in the same way.
A site that wants visitors to complete a transaction—normally a purchase—is transactional.
There’s an “ideal path” through the site that its designers intended, resulting in a goal or
outcome of some kind. The goal isn’t always a purchase; it can also be enrollment (signing
up for email) or lead generation (asking salespeople to contact them), and can happen either
online or off.
For e-commerce, that’s whatever your transaction consists of.
144. For media sites
Are ads loading quickly and successfully clicked
through?
Is content loading fast enough for visitors?
Thursday, June 17, 2010
These sites offer content that attracts and retains an audience. They make money from that
content through sponsorship, advertising, or affiliate referrals. Search engines, Adwords-
backed sites, newspapers, and well-known bloggers are media properties.
For media sites, that’s making money from ads.
145. For collaboration sites
Can visitors contribute (posting content, voting?)
Is bad content being mitigated (trolling, spam)?
Thursday, June 17, 2010
On these sites, visitors generate the content themselves. Wikis, news aggregators, user
groups, classified ad listings, and other web properties in which the value of the site is
largely derived from things created by others are all collaborative.
For collaboration, that’s creating and curating content.
146. For SaaS sites
Are your end users productive?
Are they making fewer mistakes?
Is the site working during customers’ business hours?
Thursday, June 17, 2010
These sites are hosted versions of software someone might buy. SaaS subscribers expect
reliability and may pay a monthly per-seat fee for employees to use the service. Revenues
come from subscriptions, and a single subscriber may have many user accounts. On some
SaaS sites, users are logged in for hours every day.
For SaaS sites, that’s productivity and an error-free experience.
147. Enterprise subscriber $
1
End user (employee) $
Refund $
2
Renewal, upsell, SLA
reference SaaS site violation
Performance
Good Bad 3
Helpdesk Support
5 $
Usability escalation costs
7
4
Good Bad
Productivity
Good Bad
6
Churn $
Impact on site
$ Positive $ Negative
Thursday, June 17, 2010
The closest your app will be to one of the four “public” websites is a SaaS site. Here’s
the business model for a SaaS site.
148. (Insert your app here)
?
Are they adopting the app at the rate you expect?
Are they abandoning the old ways?
What are they using most or neglecting?
How productive are they?
Where are they making mistakes?
Thursday, June 17, 2010
What does your adoption and usage map look like?
149. The cycle of optimization
Metrics & strategy
Optimization
Collection
& change
Link to KPI/
Reporting
ROI
Institutionalizing
the results
Thursday, June 17, 2010
Optimization involves a constant cycle of collection, reporting, communicating and sharing
the data, tying it to business processes, changing the system, and repeating.
150. The good news:
you can experiment easily
We stop worrying about ROI when I is zero.
Thursday, June 17, 2010
152. Beyond adoption: outcomes
Business
Deployment Awareness Adoption
outcomes
Thursday, June 17, 2010
Once you’ve got adoption, you’re not done: the same tools will let you measure the
outcomes:
- More productivity
- Abandonment of old/bad methods
- More leads
- Lower cost
- Fewer errors
- Etc.
156. The next 3 days
The inside-out organization: Connecting to
Tuesday
customers and markets
Mobile Platforms and Enterprise Agility
The Politics of Delivery: Compliance and
Wednesday
Governance
Platform Options in the New IT Landscape
Social Behavior, Usage Patterns, and Adoption
Can IT Lead the Social Business Strategy
Thursday
Formulation Process?
Delivery Strategies: The Road Ahead
Thursday, June 17, 2010
157. Thanks!
@acroll
alistair@bitcurrent.com
Thursday, June 17, 2010