微服务架构(Microservice architecture)

 我们有多个用Java，C＃，nodeJS和python编写的独立应用程序。 所有这些应用程序共享一个共同属性 - 它们使用REST API基于每个客户的计划从某些源提取数据并将其存储在CSV文件中，稍后使用存储过程将数据从CSV文件导入到不同的SQL数据库。 每个应用程序用于集成来自不同第三方服务的数据。 
 
 例如 - app A从源A'获取数据，app B从源B获取数据' 
 
 我正在考虑通过编写一个可以处理来自不同来源的数据的多租户单个应用程序来替换这些多个独立的应用程序。 所有这些单独的小应用程序将配置为用Java编写的自定义作业。 例如 - REST API身份验证，在创建CSV之前预处理数据等。 
 
 所以，我想编写一个从源A'获取数据的作业（Java文件）和从源B'获取数据的另一个作业。 主应用程序将执行此自定义作业。 主应用程序将支持诸如作业调度，日志记录等常用功能。 
 
 后来我打算用nifi处理从CSV到SQL数据库的数据导入。 
 
 这会是一个好方法吗？ 我打算用Java编写这个应用程序。 
 
 解决方案背后的原因 
 
 
 
 多个代码库来维护 
 
 
 在提取数据时没有并发性 
 
 
 所有这些应用程序都作为单个实例部署 
 
 
 如果我需要更新一个作业，我需要部署整个应用程序。 如何绕过这个过程？ 有什么方法可以部署工作而不是整个应用程序？ 
 
 构建此解决方案的好方法是什么？ 

We have multiple separate applications written in Java,C#,nodeJS and python. All these application share a common property - they pull data from some source based on schedule per customer basis using REST API and store it in CSV file, later import data from CSV file to different SQL database using stored procs. Each application is used to integrate data from different third party service.
 
For example - app A fetching data from source A' and app B fetching data from source B' 
 
I'm thinking of replacing these multiple separate applications by writing one multi-tenant single application which can handle pulling data from different sources. All these separate small applications will be configured as a custom job written in Java. For example - REST API authentication, pre-processing of data before creating CSV etc.
 
So, I want to write a job (Java file) that fetches data from source A' and another job that fetches data from source B'. The main application will execute this custom job. The common functionality such as job scheduling, logging etc will be supported by the main application.
 
Later I intend to use nifi to handle data import from CSV to SQL database.
 
Will this be a good approach? I'm planning to write this application in Java.
 
Reason behind the solution
 
 
 
Multiple code base to maintain
 
 
No concurrency in pulling data
 
 
All these applications are deployed as a single instance
 
 
If I need to update one job I need to deploy the whole application. How to get around this process? Is there any way I can deploy just the job and not the whole application?
 
What would be the good way to architect this solution?

原文：https://stackoverflow.com/questions/45203055