RestMS Introduction

download RestMS Introduction

If you can't read please download the document

description

A brief introduction to messaging for the web, and the new RestMS protocol specification. Presented at FOSDEM 2009.

Transcript of RestMS Introduction

  • 1.
      • RestMS
    • A new protocol for
    • web messaging
    • by Pieter Hintjens, iMatix Corporation
    • February, 2009

2. Why do we need Messaging?

  • To connect the pieces together
    • It's cheap to make applications
    • But how do they talk to each other?
  • To create information feeds
    • I'm renting my apartment
  • To mine information feeds
    • I'm searching for an apartment
    • Think: Yahoo! Pipes

3. What Messaging should offer

  • Easy to connect to from any application
  • Generic tools for creating & mining feeds
  • Early filtering vs. late filtering
    • Don't send unwanted data over the network
  • Scalability
    • 1, 10, 100, 1000, 10K, 100K messages/sec
  • Loose coupling
    • Hiding applications from each other

4. Use cases

  • Server-side search of current events
  • Watch IRC channels for interesting stuff
  • Monitor thousands of news channels
  • Track thousands of postings and uploads
  • Follow thousands of stock values
  • etc.

5. The State of the Art

  • Web messaging
    • Simple direct messaging
    • RSS, AtomPub, XMPP, SOAP
  • Business messaging
    • Java repackaging of legacy tools
    • Queues, pub-sub
  • Enterprise messaging
    • Mostly expensive closed products
    • Queues, pub-sub

6. Challenges

  • Routing model
    • Hard-wired or dynamic?
    • Fixed algorithms or extensible?
  • Protocol vs. product
    • Real competition in the market?
    • Free and open digital standard?
  • Complexity
    • Simple to understand and use
    • Or, enterprise technology?

7. Why is messaging unpopular?

  • Too complex
    • Results 1 - 10 of about 264,000 for 'soap too complex'.
    • Complexity means extra cost
  • Not interoperable
    • Products are not standards
    • Languages are not universal
  • Still too few FOSS solutions
    • Mainly due to lack of open standards

8. In an Ideal World...

  • Based on free and open standards
  • Generic & extensible routing
  • Easy to use in any language
  • Runs nicely on any operating system
  • Fast enough for real work
    • Low latency (10usec to 1sec)
    • High volume (1/sec to 1M /sec)

9. AMQP

  • Free and open standard
  • Generic & extensible routing
  • Not easy to use in any language
    • It's a complex binary protocol that needs an API stack for each language
  • Runs nicely on any operating system
  • Fast enough for real work
  • AMQP is great except it's inaccessible

10. AtomPub

  • Free and open standard
  • A single limited routing model
    • Publish to feed, read from feed: no filtering or routing
  • Easy to use in any language
  • Runs nicely on any operating system
  • Fast enough for real work
  • AtomPub is great except it's limited

11. So why RestMS?

  • AMQP showed us something new
    • Generic routing (exchange-binding-queue)
    • Portability (Linux, AIX, Solaris, win32)
    • Interoperability (C, C++, Java, .NET, Python)
    • Performance (~500k msg/sec in OpenAMQ)
  • But it remains inaccessible
    • How do I use AMQP from the web?
    • How do I use AMQP in language X?

12. Magic potions

  • Take the best of AMQP and AtomPub
  • Shake briskly, allow to cook:
  • AMQP's routing model (improved)
  • RESTful access over ordinary HTTP(S)
  • Portable & interoperable
  • Documented as free and open standard
  • Interoperate with AMQP networks

13. Architecture Public Internet Company Intranet RestMS Server HTTP network AMQP network RestMS Server 14. How RestMS works

  • Publishers send messages tofeeds
  • Subscribers createpipes
    • Andjointheir pipes to feeds
  • Subscribers then read from their pipes
    • Get message, process message, loop
  • Joins specify the routing arguments
    • By key, by expression, etc.

15. RESTful access

  • If you know HTTP, you know REST
  • Create/Read/Update/Delete resource
    • POST creates a new resource
    • GET reads a resource
    • PUT updates a resource
    • DELETE spawns... just kidding, it deletes the resource
  • Resources are mostly shown in XML
    • But RestMS also supports JSON

16. Why REST / HTTP is cool

  • It is simple
  • It uses existing transports
  • It uses existing security
  • It uses existing libraries
  • It uses existing metaphors (CRUD)
  • It scales on a web infrastructure
    • Proper attention to caching

17. REST / HTTP gotchas

  • Rather chatty
    • Can be solved by batching writes and reads
  • Polled vs. event driven
    • Can be solved by using long polls
  • Rather verbose (XML envelopes)
    • Ignore the problem, it will go away
  • Not an enterprise technology
    • Wait, it will be

18. What's available now?

  • restms.org
    • Draft RestMS specifications
    • Example client code (Perl, for now)
  • openamq.org
    • Source code for OpenAMQ & Zyre
  • zyre.com
    • All about Zyre
  • live.zyre.com
    • Live RestMS server, running Zyre

19. Conclusions

  • Messaging is a great tool
  • But the good stuff is too complex
  • And the simple stuff is too limited
  • Time for a simple, capable option
  • Based on a free and open standard
  • With a solid implementation

20. Thank you

  • Comment & discuss at zyre.com
  • Email list, see www.openamq.org

URBAN STREAM REHABILITATION. INTRODUCTION, OBJECTIVES & IMPACTS INTRODUCTION, OBJECTIVES & IMPACTS INTRODUCTION, OBJECTIVES & IMPACTS INTRODUCTION, OBJECTIVES.

URBAN STREAM REHABILITATION. INTRODUCTION, OBJECTIVES & IMPACTS INTRODUCTION, OBJECTIVES & IMPACTS INTRODUCTION, OBJECTIVES & IMPACTS INTRODUCTION, OBJECTIVES.

Introduction - University of Cambridge · Introduction. Introduction

Introduction - University of Cambridge · Introduction. Introduction

Introduction to introduction to introduction to … Optimization

Introduction to introduction to introduction to … Optimization

Introduction to Transducers, Introduction to Transducers ... on... · Introduction to Transducers, Introduction to Transducers, Sensors and ActuatorsSensors and Actuators Introduction

Introduction to Transducers, Introduction to Transducers ... on... · Introduction to Transducers, Introduction to Transducers, Sensors and ActuatorsSensors and Actuators Introduction

1. INTRODUCTION INTRODUCTION - Deusto

1. INTRODUCTION INTRODUCTION - Deusto

§1.1.1 INTRODUCTION: 1. INTRODUCTION

§1.1.1 INTRODUCTION: 1. INTRODUCTION

Introduction | Introduction | Millennium Serials · 2018. 4. 17. · MARC Display | Print | Introduction | Millennium Serials INTRODUCTION Introduction This tutorial introduces the

Introduction | Introduction | Millennium Serials · 2018. 4. 17. · MARC Display | Print | Introduction | Millennium Serials INTRODUCTION Introduction This tutorial introduces the

Topics Introduction 1 / 3 Introduction 2 / 3 Introduction 3 / 3.

Topics Introduction 1 / 3 Introduction 2 / 3 Introduction 3 / 3.

4ALPH4 GIEO(lNDL4) LIMITED€¦ · 1st Floor, New Trading Ring, Rotunda Building, Phiroze Jeejeebhoy Towers, ... 2020 inter alia to consiclel' and approve the Auditec:fAIlMCiaI RestMs

4ALPH4 GIEO(lNDL4) LIMITED€¦ · 1st Floor, New Trading Ring, Rotunda Building, Phiroze Jeejeebhoy Towers, ... 2020 inter alia to consiclel' and approve the Auditec:fAIlMCiaI RestMs

Introduction to Logic Introduction

Introduction to Logic Introduction

PRODUCT INTRODUCTION Company Introduction

PRODUCT INTRODUCTION Company Introduction

Introducción / Introduction / Introduction

Introducción / Introduction / Introduction

1 Introduction t 1. Introduction to Nanotechnology - UFAMhome.ufam.edu.br/berti/nanomateriais/Introduction to Nanotechnology... · Introduction t 1. Introduction to Nanotechnology

1 Introduction t 1. Introduction to Nanotechnology - UFAMhome.ufam.edu.br/berti/nanomateriais/Introduction to Nanotechnology... · Introduction t 1. Introduction to Nanotechnology

1. Introduction 10 - therackonline.com€¦ · 1. Introduction 10 - therackonline.com ... Introduction)

1. Introduction 10 - therackonline.com€¦ · 1. Introduction 10 - therackonline.com ... Introduction)

1. Introduction 1. Introduction 1. Introduction 1 ... · Introduction 1. Introduction 1. Introduction 1. Introduction 6061B0242401. The Phone Screen From the Phone screen, you can

1. Introduction 1. Introduction 1. Introduction 1 ... · Introduction 1. Introduction 1. Introduction 1. Introduction 6061B0242401. The Phone Screen From the Phone screen, you can

An Erlang Implementation of Restms. Why have messaging? Separates applications cheaply Feed information to the right applications cheaply Interpret feed.

An Erlang Implementation of Restms. Why have messaging? Separates applications cheaply Feed information to the right applications cheaply Interpret feed.

Introduction Chapitre 1 · Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Introduction Chapitre 1 · Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

R as a Web Service Introduction Introduction Introduction

R as a Web Service Introduction Introduction Introduction

CrowPiwithMineCraftPiEdition · 2 CrowPiwithMineCraftPiEdition-Introduction-MinecraftPiEdition-Introduction-Whatyouwillneed-Introduction-RunningMinecraft-Introduction ...

CrowPiwithMineCraftPiEdition · 2 CrowPiwithMineCraftPiEdition-Introduction-MinecraftPiEdition-Introduction-Whatyouwillneed-Introduction-RunningMinecraft-Introduction ...

Introduction: Definition Introduction: Philosophy

Introduction: Definition Introduction: Philosophy