About All Things... |
Declarative,
Mobile 2.0,
REST,
Cloud,
Web 2.0,
Ajax,
Publish / Subscribe,
Event-Driven Architectures,
JSON,
Atom,
Microformats,
Linked Data,
P2P,
Identity,
Copyright,
Multimedia,
Cyberspace.
|
...taking programming beyond: Threads, Message Queues, Client-Server, CORBA, Web Services, SOAs, Agents, Synchronous Architectures, Imperative Programming - and even Applications, Desktops and Documents |
Duncan Cragg... |
...works for ThoughtWorks UK; originally from April 2002 to July 2007 and now recently re-joined. Previously worked as a Web Architect for the Financial Times. |
...went to both UCL and Imperial College of the University of London (in the Eighties); specialising in Logic during his MSc. |
...wonders when his LinkedIn Account will be useful |
...has a phone-cam, and used it on himself once, just before his weekly shave:
|
...can be contacted by
and followed on Twitter.
|
|
|
|
March 18, 2010 16:58
Around the middle of February I completed a basic persistence and networking
implementation for
Fjord,
then had to do other things for a month. Just recently I
fixed Fjord to work with the latest version of the
Node.js APIs.
Next project: I'm going to use Fjord in a Web Framework to be called "JSON-Mash".
I intend to show that JSON-Mash will be a great framework for rapidly building
truly interoperable and truly scalable online and distributed functionality.
Here's how JSON-Mash will work.
...
January 6, 2010 17:03
Well, I've put together the first few lines of Fjord, implemented on Node.js.
Here's the description on GitHub: Fjord is a language for expressing domain logic as match-rewrite functions over mashable JSON Web objects.
I'm developing Fjord very openly, in the hope someone out there will be interested in getting involved in helping guide its design and implementation. I suppose code speaks louder than blog posts.
...
August 13, 2009 11:43
In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.
Although eBay have what they call a 'REST' interface, it is, in
fact, a
STREST
interface, and only works for a few of the many function calls
that they make available via SOAP.
In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.
Part 9: Web Objects Ask, They Never Tell
...
July 16, 2009 16:16
In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.
Although eBay have what they call a 'REST' interface, it is, in
fact, a
STREST
interface, and only works for a few of the many function calls
that they make available via SOAP.
In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.
Part 8: WS-Are-You-Sure (Security, Reliable Messaging and Transactions)
...
December 19, 2008 17:05
Mobiles are unique - if you want to miss out on the opportunity they represent, you
could choose to see them as just slow computers with tiny interfaces and dodgy Internet
connections. Then try to squeeze in your traditional applications; try squeezing the
office desktop metaphor with its sedentary documents into a device the size of a mouse!
Alternatively, see them as the most personal, social and dynamic of devices that are
becoming connected to the Internet. Now a multi-billion-scale global opportunity opens
up to you. That's customers and dollars! In trying to grasp this, some are calling
it 'Mobile 2.0', by analogy with its sibling, Web 2.0.
In that light, the Killer App for Mobile 2.0 is the sharer, masher and updater of
People, Things, Times and Places... The key to getting Mobile 2.0 right is for it to
merge seamlessly into our lives. That means the handling of dynamic and shared data
becomes the top priority, even above the handling of applications.
This article describes a Mobile 2.0 platform that makes people and their stuff first
class - not applications.
...
December 11, 2008 11:45
In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.
Although eBay have what they call a 'REST' interface, it is, in
fact, a
STREST
interface, and only works for a few of the many function calls
that they make available via SOAP.
In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.
Part 7: Business Conversations
...
October 5, 2007 11:22
Last night's
Google London Open Source Jam
(also here)
was on the subject of the 'Web' (didn't they invent that? Oh no,
that was Microsoft).
This event has been getting better and better each time I've
attended. There were some very interesting lightning talks held
together with a tight structure and plenty of chance to chat,
drink cold Leffe and eat cold pizza. And nick [transatlantic
translation: 'steal'] the
Green & Black's chocolate.
An ideal Micro Conference...
...
June 26, 2007 15:17
Web 2.0's definition
includes seeing the Web as an application platform. Which means it
is in competition with Java and .Net, and with SOA, for both local
and widely distributed applications.
If the Web is going to be a platform, the skills you need to learn
to program it are the core Web 2.0 technologies such as Ajax, JSON,
Atom, Microformats and OpenID.
And Ruby. This language, that's capturing the hearts of many Web 2.0
programmers, is ideal for easing the transition from the Java
and .Net platforms to the Web platform, as I will show.
Even if you're part of a big company that is generally immune to the
latest trends, the marriage of Ruby and the Web-as-platform may be
something to prepare for. It could even displace your SOA agenda...
...
June 20, 2007 22:42
In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.
Although eBay have what they call a 'REST' interface, it is, in
fact, a
STREST
interface, and only works for a few of the many function calls
that they make available via SOAP (GetSearchResults, GetItem,
GetCategoryListings, etc).
In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.
Part 5: The Distributed Observer Pattern
...
April 8, 2007 13:38
In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.
Although eBay have what they call a 'REST' interface, it is, in
fact, a
STREST
interface, and only works for a few of the many function calls
that they make available via SOAP (GetSearchResults, GetItem,
GetCategoryListings, etc).
In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.
Part 4: Inter-Enterprise REST Integration
...
January 10, 2007 14:21
In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.
Although eBay have what they call a 'REST' interface, it is, in
fact, a
STREST
interface, and only works for a few of the many function calls
that they make available via SOAP (GetSearchResults, GetItem,
GetCategoryListings, etc).
In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.
Part 3: Business Functions
...
December 14, 2006 14:15
There were two things I knew about eBay's Architecture - that
they use J2EE and that they seem to like SOA. Both are
approaches I give, ahem, special mention to on all my pages at
the bottom of the left-hand column.
So it was with some apprehension that I opened up
this
(PDF) slide pack from
Dan Pritchett
and Randy Shoup of eBay, presented at
SD Forum 2006 recently.
I was expecting my prejudices around the issues and techniques of scaling web sites
to be challenged, at least.
...
July 13, 2006 14:33
Don't write your interactive Web application in custom
Javascript! The Web's Declarative nature needn't be
broken just because you want two-way dynamic data instead of
one-way documents on your site.
Instead, write Declaratively to generic Javascripts, plugins
and browser features such as
Hijax,
hInclude,
XForms,
SVG, XBL, etc.
...
March 22, 2006 17:00
Declarative Architectures focus on the What, not the How, of programming. The How has dominated the field - perhaps 80% of programming is done in the traditional Imperative style, where we tell the computer How to do a task in explicit steps.
I'd like to show in this blog how Declarative Architectures and technologies are not just an interesting sideshow to the main Imperative attraction, but a complete and powerful programming alternative in their own right - indeed, one which has already dominated certain fields.
Imagine being able to simply express What we want the computer to do - to give it constraints and rules - then let it work out for itself How to achieve our goals.
I believe that saying What, not How, will become the dominant paradigm in programming.
...
|
|
|
|