SemanticScuttle - klotz.me

klotz: api* + orchestration*

Bookmarks on this page are managed by an admin user.

0 bookmark(s) - Sort by: Date ↓ / Title / - Bookmarks from other users for this tag

11. [concurrency-interest] jdk9 Candidate classes Flow and SubmissionPublisher

    2015-01-17 Tags: java, reactive, orchestration, api, doug lea by klotz
12. Hexagonal Architecture–The Great Reconciler?

    2015-01-12 Tags: api, orchestration, microservices by klotz
13. Retrofit and RxJava (Netflix Open Source Meetup S02E02 07/2014) // Speaker Deck

    2014-12-30 Tags: api, orchestration, java, retrofit, rxjava, netflix, square by klotz
14. Ratpack: Simple, lean & powerful HTTP apps

    2014-12-30 Tags: java, java8, netty, guava, functional reactive programming, api, orchestration by klotz
15. Neatly Composing REST Calls Using Retrofit and RxJava - Jonas Lüthke

    2014-12-29 Tags: rxjava, retrofit, orchestration, api by klotz
16. mulesoft/mule

    Mule uses components to conduct backend processes for specific business logic (like checking the customer and inventory databases). Then, the components route messages to the correct application (such as an order fulfillment system). This use is called a Staged Event-Driven Architecture (SEDA) for core asynchronous message processing in flows. Importantly, components don't have to have any Mule-specific code; they can simply be POJOs, Spring beans, Java beans, Groovy scripts, or web services containing the business logic for processing data. Components can even be developed in other languages such as Python, JavaScript, Ruby, and PHP. Mule’s catalog of building blocks includes the most commonly used Enterprise Integration Patterns.
    
    A flow, therefore, is the construct within which you link together several individual components (i.e. building blocks) to handle the receipt, processing, and eventual routing of a message. You can connect many flows together to build a complete application which you can then deploy on premise, on Mule, on another application server, or in the cloud. Practically speaking, you could build, deploy, and run a Mule application in a matter of hours, rather than spending weeks or months building point-to-point connections between systems. Studio, Mule’s Eclipse-based graphical IDE, makes it even easier to model, then configure, test, and deploy your applications. Mule is so named because it “carries the heavy development load” of connecting systems.

    2014-12-23 Tags: mule, api, orchestration, github by klotz
17. Service Orchestration and Choice Routing Example - Current Mule Documentation

    2014-12-23 Tags: orchestration, xml, api by klotz
18. nirmata | Getting Started with Microservices Using Netflix OSS & Docker - nirmata

    2014-12-23 Tags: netflix, api, orchestration by klotz
19. ql.io | eBay Developers Program

    2014-12-12 Tags: api, orchestration, ebay by klotz
20. ql.io

    To call three HTTP APIs, write this script
    Try me
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    prodid = select ProductID 0 » .Value from eBay.FindProducts where
    QueryKeywords = 'macbook pro';
    details = select * from eBay.ProductDetails where
    ProductID in ('{prodid}') and ProductType = 'Reference';
    reviews = select * from eBay.ProductReviews where
    ProductID in ('{prodid}') and ProductType = 'Reference';
    
    return select d.ProductID 0 » .Value as id, d.Title as title,
    d.ReviewCount as reviewCount, r.ReviewDetails.AverageRating as rating
    from details as d, reviews as r
    where d.ProductID 0 » .Value = r.ProductID.Value
    via route '/myapi' using method get;
    and curl away
    1
    curl http://<host>:<port>/myapi

    2014-12-12 Tags: api, orchestration, ebay by klotz

Top of the page

First / Previous / Next / Last / Page 2 of 0