Multi-tenancy in Spring Cloud Data Flow





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am starting to work on evaluation of Spring Cloud DataFlow.
One of the considerations I have is ability to execute Tasks or Streams in context of a particular tenant. This is especially true if we need per-tenant configuration of task triggers.



Do you know of any way to support this or in general support multi-tenant Spring Cloud Data Flow environment?










share|improve this question























  • Thanks for your answer. I understand your comment and slightly encouraged by this. My real need is in a SaaS environment, how do you provide capabilities of SCDF on a per-tenant basis. This includes dashboard, etc.

    – M Shnayderman
    Nov 22 '18 at 5:50


















0















I am starting to work on evaluation of Spring Cloud DataFlow.
One of the considerations I have is ability to execute Tasks or Streams in context of a particular tenant. This is especially true if we need per-tenant configuration of task triggers.



Do you know of any way to support this or in general support multi-tenant Spring Cloud Data Flow environment?










share|improve this question























  • Thanks for your answer. I understand your comment and slightly encouraged by this. My real need is in a SaaS environment, how do you provide capabilities of SCDF on a per-tenant basis. This includes dashboard, etc.

    – M Shnayderman
    Nov 22 '18 at 5:50














0












0








0








I am starting to work on evaluation of Spring Cloud DataFlow.
One of the considerations I have is ability to execute Tasks or Streams in context of a particular tenant. This is especially true if we need per-tenant configuration of task triggers.



Do you know of any way to support this or in general support multi-tenant Spring Cloud Data Flow environment?










share|improve this question














I am starting to work on evaluation of Spring Cloud DataFlow.
One of the considerations I have is ability to execute Tasks or Streams in context of a particular tenant. This is especially true if we need per-tenant configuration of task triggers.



Do you know of any way to support this or in general support multi-tenant Spring Cloud Data Flow environment?







spring-cloud-dataflow






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '18 at 15:33









M ShnaydermanM Shnayderman

1




1













  • Thanks for your answer. I understand your comment and slightly encouraged by this. My real need is in a SaaS environment, how do you provide capabilities of SCDF on a per-tenant basis. This includes dashboard, etc.

    – M Shnayderman
    Nov 22 '18 at 5:50



















  • Thanks for your answer. I understand your comment and slightly encouraged by this. My real need is in a SaaS environment, how do you provide capabilities of SCDF on a per-tenant basis. This includes dashboard, etc.

    – M Shnayderman
    Nov 22 '18 at 5:50

















Thanks for your answer. I understand your comment and slightly encouraged by this. My real need is in a SaaS environment, how do you provide capabilities of SCDF on a per-tenant basis. This includes dashboard, etc.

– M Shnayderman
Nov 22 '18 at 5:50





Thanks for your answer. I understand your comment and slightly encouraged by this. My real need is in a SaaS environment, how do you provide capabilities of SCDF on a per-tenant basis. This includes dashboard, etc.

– M Shnayderman
Nov 22 '18 at 5:50












1 Answer
1






active

oldest

votes


















0














A bit of background before we get into the details.



SCDF is a lightweight RESTful (Sring Boot) application, which happens to include orchestration mechanics to deploy, launch, or operate on data pipelines made of stream/task applications (aka: Spring Boot applications).



For high-availability, fault-tolerance, resiliency along with multi-tenancy requirements, SCDF delegates it and relies on the platform where you run it.



Let's dive into the details now.



When you deploy streams/task from SCDF to Cloud Foundry, you will deploy them to an Org/Space boundary, which happens to be accessible by folks who have access to it. Extending that, when you use the SCDF Tile for PCF, you'd be able to create a service-instance for SCDF from a particular Org/Space combination, so it naturally comes with the said boundary. The boundary then becomes an environment for project/team specific streams/tasks to run without collisions - thus preserving the tenancy attributes.



Similarly, when you deploy streams/task from SCDF to Kubernetes, you'd have the boundary defined by "namespaces" and the access-control.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53340941%2fmulti-tenancy-in-spring-cloud-data-flow%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    A bit of background before we get into the details.



    SCDF is a lightweight RESTful (Sring Boot) application, which happens to include orchestration mechanics to deploy, launch, or operate on data pipelines made of stream/task applications (aka: Spring Boot applications).



    For high-availability, fault-tolerance, resiliency along with multi-tenancy requirements, SCDF delegates it and relies on the platform where you run it.



    Let's dive into the details now.



    When you deploy streams/task from SCDF to Cloud Foundry, you will deploy them to an Org/Space boundary, which happens to be accessible by folks who have access to it. Extending that, when you use the SCDF Tile for PCF, you'd be able to create a service-instance for SCDF from a particular Org/Space combination, so it naturally comes with the said boundary. The boundary then becomes an environment for project/team specific streams/tasks to run without collisions - thus preserving the tenancy attributes.



    Similarly, when you deploy streams/task from SCDF to Kubernetes, you'd have the boundary defined by "namespaces" and the access-control.






    share|improve this answer




























      0














      A bit of background before we get into the details.



      SCDF is a lightweight RESTful (Sring Boot) application, which happens to include orchestration mechanics to deploy, launch, or operate on data pipelines made of stream/task applications (aka: Spring Boot applications).



      For high-availability, fault-tolerance, resiliency along with multi-tenancy requirements, SCDF delegates it and relies on the platform where you run it.



      Let's dive into the details now.



      When you deploy streams/task from SCDF to Cloud Foundry, you will deploy them to an Org/Space boundary, which happens to be accessible by folks who have access to it. Extending that, when you use the SCDF Tile for PCF, you'd be able to create a service-instance for SCDF from a particular Org/Space combination, so it naturally comes with the said boundary. The boundary then becomes an environment for project/team specific streams/tasks to run without collisions - thus preserving the tenancy attributes.



      Similarly, when you deploy streams/task from SCDF to Kubernetes, you'd have the boundary defined by "namespaces" and the access-control.






      share|improve this answer


























        0












        0








        0







        A bit of background before we get into the details.



        SCDF is a lightweight RESTful (Sring Boot) application, which happens to include orchestration mechanics to deploy, launch, or operate on data pipelines made of stream/task applications (aka: Spring Boot applications).



        For high-availability, fault-tolerance, resiliency along with multi-tenancy requirements, SCDF delegates it and relies on the platform where you run it.



        Let's dive into the details now.



        When you deploy streams/task from SCDF to Cloud Foundry, you will deploy them to an Org/Space boundary, which happens to be accessible by folks who have access to it. Extending that, when you use the SCDF Tile for PCF, you'd be able to create a service-instance for SCDF from a particular Org/Space combination, so it naturally comes with the said boundary. The boundary then becomes an environment for project/team specific streams/tasks to run without collisions - thus preserving the tenancy attributes.



        Similarly, when you deploy streams/task from SCDF to Kubernetes, you'd have the boundary defined by "namespaces" and the access-control.






        share|improve this answer













        A bit of background before we get into the details.



        SCDF is a lightweight RESTful (Sring Boot) application, which happens to include orchestration mechanics to deploy, launch, or operate on data pipelines made of stream/task applications (aka: Spring Boot applications).



        For high-availability, fault-tolerance, resiliency along with multi-tenancy requirements, SCDF delegates it and relies on the platform where you run it.



        Let's dive into the details now.



        When you deploy streams/task from SCDF to Cloud Foundry, you will deploy them to an Org/Space boundary, which happens to be accessible by folks who have access to it. Extending that, when you use the SCDF Tile for PCF, you'd be able to create a service-instance for SCDF from a particular Org/Space combination, so it naturally comes with the said boundary. The boundary then becomes an environment for project/team specific streams/tasks to run without collisions - thus preserving the tenancy attributes.



        Similarly, when you deploy streams/task from SCDF to Kubernetes, you'd have the boundary defined by "namespaces" and the access-control.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 16 '18 at 18:54









        Sabby AnandanSabby Anandan

        3,2051514




        3,2051514
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53340941%2fmulti-tenancy-in-spring-cloud-data-flow%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            The Sandy Post

            Danny Elfman

            Pages that link to "Head v. Amoskeag Manufacturing Co."