An obscure but ubiquitous design pattern in PHP development is known as Funky Caching. Using real architectural examples as a lens to look at this one simple PHP design pattern, we see how we can design web architectures that are "organic, democratic, and lasting"
A sure way to make data and ML work for you in a 10x manner is to start with low-hanging fruit: a recommender system. It's been a useful application of data science to the consumer-facing web since the early days of the internet. This talk explains how one was built to recommend colleges to prospective high school students, the application of popularity tables and collaborative filters, as well as other approaches and the reasons for doing them.
"Managing API Complexity". Matthew Flaming, TembooYandex
APIs are proliferating on the web, providing app developers with ready access to a wide range of data and services, yet very few apps take advantage of more than one or two API providers. Arbitrary inconsistencies between APIs -- from authentication to input/output formats to details as small as timestamps or pagination -- mean every new API brings its own unnecessarily redundent learning curve, draining developer's most precious resource: time.
Temboo is part of an emerging class of services for managing and scaling API usage. By NORMALIZING access to APIs (as well as their associated documentation and credentials) these services do for development what PaaS and server virtualization have already done for app deployment and infrastructure. "Code virtualization", whereby all the tedious details of API access are abstracted away in standardized cloud-based processes, will free developers to spend their time writing only the code that actually makes their app unique. And that means more unique apps for everyone.
PDF version of my slide deck for "PHP Without PHP" given at International PHP Conference in Berlin, Germany on May 2009
Abstract:
An obscure but ubiquitous design pattern in PHP development is known as Funky Caching. Using real architectural examples as a lens to look at this one simple PHP design pattern, we see how we can design web architectures that are "organic, democratic, and lasting."
An update of my Perl Myths talk (for http://ossbarcamp.com in Dublin, Ireland, September 2009). It covers jobs, cpan, community, best practices, power tools, and perl 6.
In Opera Software we use Perl extensively.
From internal systems to high traffic web sites and browser-integration services like Opera Link and Opera Unite.
Most of them are mission-critical systems, up and running 24x7.
A sure way to make data and ML work for you in a 10x manner is to start with low-hanging fruit: a recommender system. It's been a useful application of data science to the consumer-facing web since the early days of the internet. This talk explains how one was built to recommend colleges to prospective high school students, the application of popularity tables and collaborative filters, as well as other approaches and the reasons for doing them.
"Managing API Complexity". Matthew Flaming, TembooYandex
APIs are proliferating on the web, providing app developers with ready access to a wide range of data and services, yet very few apps take advantage of more than one or two API providers. Arbitrary inconsistencies between APIs -- from authentication to input/output formats to details as small as timestamps or pagination -- mean every new API brings its own unnecessarily redundent learning curve, draining developer's most precious resource: time.
Temboo is part of an emerging class of services for managing and scaling API usage. By NORMALIZING access to APIs (as well as their associated documentation and credentials) these services do for development what PaaS and server virtualization have already done for app deployment and infrastructure. "Code virtualization", whereby all the tedious details of API access are abstracted away in standardized cloud-based processes, will free developers to spend their time writing only the code that actually makes their app unique. And that means more unique apps for everyone.
PDF version of my slide deck for "PHP Without PHP" given at International PHP Conference in Berlin, Germany on May 2009
Abstract:
An obscure but ubiquitous design pattern in PHP development is known as Funky Caching. Using real architectural examples as a lens to look at this one simple PHP design pattern, we see how we can design web architectures that are "organic, democratic, and lasting."
An update of my Perl Myths talk (for http://ossbarcamp.com in Dublin, Ireland, September 2009). It covers jobs, cpan, community, best practices, power tools, and perl 6.
In Opera Software we use Perl extensively.
From internal systems to high traffic web sites and browser-integration services like Opera Link and Opera Unite.
Most of them are mission-critical systems, up and running 24x7.
It takes a Village to do the Impossible - Jeff LindsayDocker, Inc.
From one of the most quietly prolific open source developers in the Docker ecosystem comes an exciting new open source tool unlike anything you've seen before. And while that's probably true,it's actually quite mundane in his grand scheme. A two part talk starting with a demo, and then a sampling of what's to come and how you can be a part of it.
Web technologies are in a constant state of flux. It’s impossible to predict which will fail, which will shine brightly then quickly fade away, and which have real longevity. Rapid innovation is what makes web app development so exciting, but shiny new things shouldn’t be pursued without a solid understanding of the underlying web platform.
ITKonekt 2023: The Busy Platform Engineers Guide to API GatewaysDaniel Bryant
API Gateways are certainly not a new technology, but the way in which they are being deployed, configured, and operated within modern platforms is forcing many of us to rethink our approach. Can we simply lift and shift our existing gateway into the cloud? Is our API gateway GitOps friendly (and does it need to be)? And what about service meshes, CNI, eBPF, and...
Join this talk for a whistle stop tour of modern API gateways, which a focus on deploying and managing this technology within Kubernetes (on which many modern platforms are built):
- Understand why platform engineers should care about API Gateways today
- Learn about API gateways, options, and requirements for modern platforms
- Identify key considerations for migrating to the cloud or building a new platform on Kubernetes
- Understand how cloud native workflows impact the user/developer experience (UX/DX) of an API gateway
- Explore the components of a complete "edge stack" that supports end-to-end development flows
онстантин часто выступает на конференциях с рассказами на совершенно разные и очень полезные Ruby-темы, но мы рады, что нам удалось сохранить изначальную тему выступления — Константин будет рассказывать именно о Sinatra: о истории, текущем состоянии и будущем фреймворка.
Take a simple PHP trick and follow it on a huge tangent to the philosophy of good web architecture.
Presentation given as Flash Talk at Automattic Meetup in Seaside on September 2010
Presentation originally a long form, but in the spirit of things, I have cut it down.
Automattic is the company I work for. The company is distributed worldwide and once a year we gather at a remote location and meet face-to-face. This year, all the employees are taking a little time during the meetup to compose and give at least one presentation for each other, talking about any subject we are passionate about.
This is based on <a>a PHP Advent article I wrote almost two years ago</a> and formed a low key presentation. I thought it’d be nice to give a more “traditional” PHP talk at the meetup—but one which I felt the audience at large could relate to.
I hope you enjoy it.
Dégraissons le mammouth ou Darwin a encore frappé - La théorie de l'évolution...Arnauld Loyer
Dégraissons le mammouth ou Darwin a encore frappé
La théorie de l'évolution appliquée au développement informatique - cas pratique de l'architecture du site PMU.fr
Depuis 1980, Lehman nous avertit: un programme doit évoluer ou péricliter, mais alors qu'il devient de plus en plus gros, la complexité résultante tend à limiter son évolution. Comment remédier à cela? Quelle architecture adopter pour un site à fort trafic comme celui du PMU?
Après avoir abordé les problématiques d'évolution et de maintenance d'une application monolithique, nous verrons pourquoi et surtout comment séparer les composants et les comportements de notre application.
Du monolithe aux micro services, du distribué, des messages, du publish/subscribe, du REST, une approche polyglotte, ... au cours de cet exposé, nous verrons quelques uns des choix retenus pour garantir la survie et l'évolution de notre application. Nous verrons comment nous avons construit un socle solide permettant de répondre aux nouvelles manières de faire du Web, d'être adapté aux applications mobiles et aux télés connectées. Ce sera l'occasion d'aborder aussi bien les principes architecturaux et les principes organisationnels qui nous ont permis d'atteindre cet objectif.
Simplicity - develop modern web apps with tiny frameworks and toolsRui Carvalho
You have learned for years how to do big enterprise applications with big enterprise frameworks. Sometimes it was good, but sometimes it was over-engineered, rarely fun. It changed a lot a few years ago with Asp.Net Mvc and with a lot of impulse of the community. But today, the web moves faster and faster, and people want tools that do the job in a simple way and that just works. Today we have these tools in .Net and they grow every day for our pleasure.
Get an overview of why you should care about Simplicity and how you can build great web apps in a simpler way with small frameworks and tools "that just work" (with pieces of NancyFx, SimpleData, RavenDb, Nuget, jQuery, Markdown, Bootstrapper, ...)
Slides of my #Web.Net conference 2012 in Milano
cheers!
2019-02 The Recommendation Engine @ SunshinePHPterry chay
One of the surest ways to start down that path of making your data science and machine learning work for you is to find low-hanging fruit. Recommender systems have proven to be one of the most useful applications of data science to the consumer-facing web since the earliest days of the internet. This talk covers why and how one was built to recommend colleges to prospective high school students, the application of popularity tables and collaborative filters, as well as other approaches and the reasons for doing them sparkled with some war stories about their success and failures. Hopefully after this you can find how your data can work for your users to transparently improve their interaction with your websites instead of sitting in the back office somewhere helping some executive add graphs to their TPS reports.
It takes a Village to do the Impossible - Jeff LindsayDocker, Inc.
From one of the most quietly prolific open source developers in the Docker ecosystem comes an exciting new open source tool unlike anything you've seen before. And while that's probably true,it's actually quite mundane in his grand scheme. A two part talk starting with a demo, and then a sampling of what's to come and how you can be a part of it.
Web technologies are in a constant state of flux. It’s impossible to predict which will fail, which will shine brightly then quickly fade away, and which have real longevity. Rapid innovation is what makes web app development so exciting, but shiny new things shouldn’t be pursued without a solid understanding of the underlying web platform.
ITKonekt 2023: The Busy Platform Engineers Guide to API GatewaysDaniel Bryant
API Gateways are certainly not a new technology, but the way in which they are being deployed, configured, and operated within modern platforms is forcing many of us to rethink our approach. Can we simply lift and shift our existing gateway into the cloud? Is our API gateway GitOps friendly (and does it need to be)? And what about service meshes, CNI, eBPF, and...
Join this talk for a whistle stop tour of modern API gateways, which a focus on deploying and managing this technology within Kubernetes (on which many modern platforms are built):
- Understand why platform engineers should care about API Gateways today
- Learn about API gateways, options, and requirements for modern platforms
- Identify key considerations for migrating to the cloud or building a new platform on Kubernetes
- Understand how cloud native workflows impact the user/developer experience (UX/DX) of an API gateway
- Explore the components of a complete "edge stack" that supports end-to-end development flows
онстантин часто выступает на конференциях с рассказами на совершенно разные и очень полезные Ruby-темы, но мы рады, что нам удалось сохранить изначальную тему выступления — Константин будет рассказывать именно о Sinatra: о истории, текущем состоянии и будущем фреймворка.
Take a simple PHP trick and follow it on a huge tangent to the philosophy of good web architecture.
Presentation given as Flash Talk at Automattic Meetup in Seaside on September 2010
Presentation originally a long form, but in the spirit of things, I have cut it down.
Automattic is the company I work for. The company is distributed worldwide and once a year we gather at a remote location and meet face-to-face. This year, all the employees are taking a little time during the meetup to compose and give at least one presentation for each other, talking about any subject we are passionate about.
This is based on <a>a PHP Advent article I wrote almost two years ago</a> and formed a low key presentation. I thought it’d be nice to give a more “traditional” PHP talk at the meetup—but one which I felt the audience at large could relate to.
I hope you enjoy it.
Dégraissons le mammouth ou Darwin a encore frappé - La théorie de l'évolution...Arnauld Loyer
Dégraissons le mammouth ou Darwin a encore frappé
La théorie de l'évolution appliquée au développement informatique - cas pratique de l'architecture du site PMU.fr
Depuis 1980, Lehman nous avertit: un programme doit évoluer ou péricliter, mais alors qu'il devient de plus en plus gros, la complexité résultante tend à limiter son évolution. Comment remédier à cela? Quelle architecture adopter pour un site à fort trafic comme celui du PMU?
Après avoir abordé les problématiques d'évolution et de maintenance d'une application monolithique, nous verrons pourquoi et surtout comment séparer les composants et les comportements de notre application.
Du monolithe aux micro services, du distribué, des messages, du publish/subscribe, du REST, une approche polyglotte, ... au cours de cet exposé, nous verrons quelques uns des choix retenus pour garantir la survie et l'évolution de notre application. Nous verrons comment nous avons construit un socle solide permettant de répondre aux nouvelles manières de faire du Web, d'être adapté aux applications mobiles et aux télés connectées. Ce sera l'occasion d'aborder aussi bien les principes architecturaux et les principes organisationnels qui nous ont permis d'atteindre cet objectif.
Simplicity - develop modern web apps with tiny frameworks and toolsRui Carvalho
You have learned for years how to do big enterprise applications with big enterprise frameworks. Sometimes it was good, but sometimes it was over-engineered, rarely fun. It changed a lot a few years ago with Asp.Net Mvc and with a lot of impulse of the community. But today, the web moves faster and faster, and people want tools that do the job in a simple way and that just works. Today we have these tools in .Net and they grow every day for our pleasure.
Get an overview of why you should care about Simplicity and how you can build great web apps in a simpler way with small frameworks and tools "that just work" (with pieces of NancyFx, SimpleData, RavenDb, Nuget, jQuery, Markdown, Bootstrapper, ...)
Slides of my #Web.Net conference 2012 in Milano
cheers!
2019-02 The Recommendation Engine @ SunshinePHPterry chay
One of the surest ways to start down that path of making your data science and machine learning work for you is to find low-hanging fruit. Recommender systems have proven to be one of the most useful applications of data science to the consumer-facing web since the earliest days of the internet. This talk covers why and how one was built to recommend colleges to prospective high school students, the application of popularity tables and collaborative filters, as well as other approaches and the reasons for doing them sparkled with some war stories about their success and failures. Hopefully after this you can find how your data can work for your users to transparently improve their interaction with your websites instead of sitting in the back office somewhere helping some executive add graphs to their TPS reports.
2013-08 10 evil things - Northeast PHP Conference Keynoteterry chay
This does not cover the animations or videos, because the Youtube (included) video has bugs related to the builds/transitions, it might be a good idea to download the slides separately and follow along in that window. (When the official conference video is available, I'll upload that instead.)
Abstract: http://www.northeastphp.org/talks/view/156/Keynote-Ten-Evil-Things-Features-Engineering-at-Wikipedia
A framework for understanding what, how, and why Features engineering is done on Wikipedia.
Wikipedia is the 5th largest website on the internet. The problem: the community that builds the "sum of all knowledge" is shrinking.
The goal of Features Engineering is to reverse that editor trend. This talk covers 10 concepts in the modern web that Wikipedia is leveraging to reverse the decline.
10 Evil(ish) Things and how they relate to Features Engineering at the WMFterry chay
Draft of 5 minute talk about Features Engineering for Wikimedia Foundation Monthly Metrics.
Note this is a PDF because Keynote upload is currently broken on SlideShare. I am including the speaker notes because of this. You can view the builds on Youtube: http://www.youtube.com/watch?v=ltqNe-ZyANE&feature=youtu.be
Also the licensing is reserved because a couple of the images I used are not CC-BY-SA, if I have time I'll work on that.)
ome companies are born lucky, and some companies have to make their luck. If your business unfortunately falls into the latter category, the way you make your luck in the Web 2.0 world is through virality. It’s a simple concept: a tiny bit of math, a lot of experimentation, and almost no common sense. Using experiences at three startups, Terry will explain what viral tuning is and how it is done. Learn how mushy business terminology like “hockey stick” and “viral marketing” meets the hard programming reality of building it on your LAMP website.
http://www.oscon.com/oscon2011/public/schedule/detail/18892
2011 07 Living without your Linemen—OSCONterry chay
http://www.oscon.com/oscon2011/public/schedule/detail/18893
If a website architect is the quarterback, then site operations is the offensive line—overworked, underappreciated, and only noticed when it fails. They make you look good. However, four years ago cloud computing networks like Amazon Web Services and Slicehost have appeared. While deficiencies in frameworks in other languages have forced those worlds to adopt Infrastructure-as-a-Service, the PHP world—with it’s ultra-cheap shared-hosting (on one end) and tradition of dominance on some of the most trafficked websites (on the other)—has been slow to move. But as the technology continues to disrupt, modern web engineers will be expected to use their programming skills to not only build, but also provision and maintain fast, scalable websites.
The efficiencies of a web-based language and experience in scalable website architecture offer a unique opportunity for programmers to transfer their skills when wearing a sysop hat. Not to mention some of the best libraries for programming them are written in PHP! When going from a small pet project to a go-live site, maybe we can learn to live without our linemen.
Presentation given as Flash Talk at Automattic Meetup in Seaside on September 2010
Presentation is supposed to be Pecha Kucha style. But due to preparation constraints, it's given as a short form.
Automattic is the company I work for. The company is distributed worldwide and once a year we gather at a remote location and meet face-to-face. This year, all the employees are taking a little time during the meetup to compose and give at least one presentation for each other, talking about any subject we are passionate about.
I started writing this talk a couple years back, and I have never found a venue to actually deliver it. Matt, claims that, “You will not find a friendlier group of people to present to in the world” and that “Everybody has a story.”
This is mine.
Hope you enjoy it.
10 Minute Lightning Talk for the Automattic Meetup at Seaside, September 2010
Automattic is the company I work for. The company is distributed worldwide and once a year we gather at a remote location and meet face-to-face. This year, all the employees are taking a little time during the meetup to compose and give at least one presentation for each other, talking about any subject we are passionate about.
For this presentation I chose the subject of photography. Specifically, taking one photo from start to publish describing how I took the shot and the editing steps I chose.
Like many bloggers—Automattic is also known as WordPress—I’m passionate about photography and I felt that many of the other people it the room might be interested in it also—our founder and CEO’s online handle is “photomatt.”
I hope you enjoy this presentation!
This was the second presentation I gave that day. I composed it just after I finished the first.
Presentation given as Flash Talk at Automattic Meetup in Seaside on September 2010
Presentation is given as an Ignite Talk format (20 slides x 15 seconds/slide = 5 minutes. Autopush.)
Automattic is the company I work for. The company is distributed worldwide and once a year we gather at a remote location and meet face-to-face. This year, all the employees are taking a little time during the meetup to compose and give at least one presentation for each other, talking about any subject we are passionate about.
In the e-mail requesting submissions, Matt mentioned that <a>Scott Berkun “did a very cool post and video on giving ignite talks</a>, so I modelled this talk after that.
Hope you enjoy it.
An obscure but ubiquitous design pattern in PHP development is known as Funky Caching. Using real architectural examples as a lens to look at this one simple PHP design pattern, we see how we can design web architectures that are "organic, democratic, and lasting/"
A PDF version of my slidedeck for the closing keynote at PHP|tek titled "Chinese Proverbs" and given at PHP|tek Chicago in May 2009.
There was no abstract for this talk.
This 7-second Brain Wave Ritual Attracts Money To You.!nirahealhty
Discover the power of a simple 7-second brain wave ritual that can attract wealth and abundance into your life. By tapping into specific brain frequencies, this technique helps you manifest financial success effortlessly. Ready to transform your financial future? Try this powerful ritual and start attracting money today!
ER(Entity Relationship) Diagram for online shopping - TAEHimani415946
https://bit.ly/3KACoyV
The ER diagram for the project is the foundation for the building of the database of the project. The properties, datatypes, and attributes are defined by the ER diagram.
Multi-cluster Kubernetes Networking- Patterns, Projects and GuidelinesSanjeev Rampal
Talk presented at Kubernetes Community Day, New York, May 2024.
Technical summary of Multi-Cluster Kubernetes Networking architectures with focus on 4 key topics.
1) Key patterns for Multi-cluster architectures
2) Architectural comparison of several OSS/ CNCF projects to address these patterns
3) Evolution trends for the APIs of these projects
4) Some design recommendations & guidelines for adopting/ deploying these solutions.
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
1. PHP without PHP
The Philosophy of
Good Architecture
terry chay
2018-03-15T11:00+0500
Confoo, Montreal, Canada
http://bit.ly/confoo19-architecture
Expecting "Where Have
All My Servers Gone?"
Sorry, Last minute change, too late to
make the program.
(I guess the speaker found his servers.)
9. Code Complete
The metaphor of Code as
construction comes from this
book…
W e n o w k n o w t h i s i s
fundamentally wrong…
10. Mythical Man Month
“man-month” is a term from
construction work
The premise is that man and
months are interchangeable.
This means that in order to
reach a deadline I simply add
more people to the project.
11. F i r s t c o n s i d e r s o m e t h i n g l i k e
painting a fence: everything is
partionable (man-month).
…add a constant time for training.
…add communication cost: n(n-1)/2.
Compare to the unpartitionable
(single man)
Adding people to a late project
makes it later!
paritionable
with training
traning + communication
unpartitionable
29. PHP is “Cheap”
“A project done in Java will cost 5 times
as much, take twice as long, and be
harder to maintain than a project done
in a scripting language such as PHP or
Perl.”
—Phillip Greenspun
30. PHP is “Scalable”
“That a Java servlet performs better
than a PHP script, under optimal
conditions [has] nothing to do with
scalability. The point is can your
application continue to deliver
consistent performance as volume
increases. PHP delegates all the ‘hard
stuff’ to other systems.”
—Harry Fuecks
31. PHP is “Pragmatic”
“PHP is not about purity in CS
principles or architecture; it is about
solving the ugly web problem with an
admittedly ugly, but extremely
functional and convenient solution. If
you are looking for purity, you are in
the wrong boat. Get out now before
you get hit by a wet cat!”
—Rasmus Lerdorf
32. Not PHP? A framework?
Your language is a set of different
choices.
Some choices were made for you (by a
framework).
Choices create a different
environment.
Leverage those choices to be in
harmony with that environment!
41. Design Hubris?
“I'm a developer, I can make software
conform to my needs.”
Trying to “lord over the environment
with an isolated man-made imposition.”
“But what I mean is it’s all man-made in
software, there is no environment.”
Language, infrastructure, team, etc.
it's all the environment
55. Design Patterns
Defined
“Each pattern describes a
problem which occurs over
a n d o v e r a g a i n i n o u r
e n v i r o n m e n t , a n d t h e n
describes the core of the
solution to that problem, in
such a way that you can use
this solution a million times
over, without ever doing it
the same way twice.”
shorten quote
72. Organic
“Form and function are one”
think beyond funky-caching!
Funky-caching is just a sleight-of-
hand
…actually a design pattern you've
seen before and used many times.
76. Cache-Aside Pattern
Instead of dynamic page generation
maybe it's a database query or remote
web query
Instead cache in file system, the cache
could be Memcache or Redis
instead of bypassing app server, bypass
your entire website (reverse proxy or
Content Distribution Network)
Whether to use it an how is ALWAYS
determined by environment
ORGANIC: Form and function are one
78. Democratic
“design should accommodate needs.”
Me
"Ruby on Rails is a rounded rectangle.”
“PHP is a Ball of Nails.”
let me build a bridge to the ruby
world…
79. mod_ruby and AWS
mod_ruby shares app space
Ruby on Rails could not be used in a
shared environment, PHP could
2006: Amazon adds EC2 to AWS
Ruby world adopted it in droves
because of a NEED.
80. Ruby gave us modern devops
Puppet/Chef
GitHub
Heroku/Engineyard
vagrant
81. Ruby was Democratic
Ruby and cloud computing was design
accommodating need
Democratic: Design should
accommodate need
In the PHP world we adopt those
tools (php is scalable by being
"shared none")
(other worlds like Python and Go,
adopt and extend to give us things like
Ansible and docker)
84. JavaScript hits big time
Code richer libaries: JQuery,
Underscores, BackboneJS…
barrier to install: npm
Compiling those libraries into single
file: webpack
webpack means we have transpiler:
Coffeescript, TypeScript,…
Facebook's php mentality: "Practical":
webpack: ES5 (webpack) into
javascript, performance
85. NPM, Webpack & Plasticity
Facebook's PHP mentality:
"Practical": ReactJS
javascript framework focus on performance
(vdom)
we have webpack, why not write it in
ECMAScript6 and transpile it to browser code?
PHP's PHP mentality:
"Cheap"
“npm is great, let's copy it! (including its
package manafest)” -> composer
All things that remove barriers: Plasticity