前言

公司之前使用Ado.net和Dapper进行数据访问层的操作, 进行读写分离也比较简单, 只要使用对应的数据库连接字符串即可. 而最近要迁移到新系统中,新系统使用.net core和EF Core进行数据访问. 所以趁着国庆假期拿出一两天时间研究了一下如何EF Core进行读写分离.

思路

根据园子里的Jeffcky大神的博客, 参考

EntityFramework Core进行读写分离最佳实践方式,了解一下(一)?

EntityFramework Core进行读写分离最佳实践方式,了解一下(二)?

最简单的思路就是使用手动切换EF Core上下文的连接, 即context.Database.GetDbConnection().ConnectionString = "xxx", 但必须要先创建上下文, 再关闭之前的连接, 才能进行切换

另一种方式是通过监听Diagnostic来将进行查询的sql切换到从库执行, 这种方式虽然可以实现无感知的切换操作, 但不能满足公司的业务需求. 在后台管理或其他对数据实时性要求比较高的项目里,查询操作也都应该走主库,而这种方式却会切换到从库去. 另一方面就是假若公司的库比较多,每种业务都对应了一个库, 每个库都对应了一种DbContext, 这种情况下, 要实现自动切换就变得很复杂了.

上面的两种方式都是从切换数据库连接入手,但是频繁的切换数据库连接势必会对性能造成影响. 我认为最理想的方式是要避免数据库连接的切换, 且能够适应多DbContext的情况, 在创建上下文实例时,就指定好是访问主库还是从库, 而不是在后期再进行数据库切换. 因此, 在上下文实例化时,就传入相应的数据库连接字符串, 这样一来DbContext的创建就需要交由我们自己来进行, 就不是由DI容器进行创建了. 同时仓储应该区分为只读和可读可写两种,以防止其他人对从库进行写操作.

实现

  1. public interface IReadOnlyRepository<TEntity, TKey>
  2. where TEntity : class, IEntity<TKey>
  3. where TKey : IEquatable<TKey>
  4. {}
  5. public interface IRepository<TEntity, TKey> : IReadOnlyRepository<TEntity, TKey>
  6. where TEntity : class, IEntity<TKey>
  7. where TKey : IEquatable<TKey>
  8. {}

IReadOnlyRepository接口是只读仓储接口,提供查询相关方法,IRepository接口是可读可写仓储接口,提供增删查改等方法, 接口的实现就那些东西这里就省略了.

  1. public interface IRepositoryFactory
  2. {
  3. IRepository<TEntity, TKey> GetRepository<TEntity, TKey>(IUnitOfWork unitOfWork)
  4. where TEntity : class, IEntity<TKey>
  5. where TKey : IEquatable<TKey>;
  6. IReadOnlyRepository<TEntity, TKey> GetReadOnlyRepository<TEntity, TKey>(IUnitOfWork unitOfWork)
  7. where TEntity : class, IEntity<TKey>
  8. where TKey : IEquatable<TKey>;
  9. }
  10. public class RepositoryFactory : IRepositoryFactory
  11. {
  12. public RepositoryFactory()
  13. {
  14. }
  15. public IRepository<TEntity, TKey> GetRepository<TEntity, TKey>(IUnitOfWork unitOfWork)
  16. where TEntity : class, IEntity<TKey>
  17. where TKey : IEquatable<TKey>
  18. {
  19. return new Repository<TEntity, TKey>(unitOfWork);
  20. }
  21. public IReadOnlyRepository<TEntity, TKey> GetReadOnlyRepository<TEntity, TKey>(IUnitOfWork unitOfWork)
  22. where TEntity : class, IEntity<TKey>
  23. where TKey : IEquatable<TKey>
  24. {
  25. return new ReadOnlyRepository<TEntity, TKey>(unitOfWork);
  26. }
  27. }

RepositoryFactory提供仓储对象的实例化

  1. public interface IUnitOfWork : IDisposable
  2. {
  3. public DbContext DbContext { get; }
  4. /// <summary>
  5. /// 获取只读仓储对象
  6. /// </summary>
  7. IReadOnlyRepository<TEntity, TKey> GetReadOnlyRepository<TEntity, TKey>()
  8. where TEntity : class, IEntity<TKey>
  9. where TKey : IEquatable<TKey>;
  10. /// <summary>
  11. /// 获取仓储对象
  12. /// </summary>
  13. IRepository<TEntity, TKey> GetRepository<TEntity, TKey>()
  14. where TEntity : class, IEntity<TKey>
  15. where TKey : IEquatable<TKey>;
  16. int SaveChanges();
  17. Task<int> SaveChangesAsync(CancellationToken cancelToken = default);
  18. }
  19. public class UnitOfWork : IUnitOfWork
  20. {
  21. private readonly IServiceProvider _serviceProvider;
  22. private readonly DbContext _dbContext;
  23. private readonly IRepositoryFactory _repositoryFactory;
  24. private bool _disposed;
  25. public UnitOfWork(IServiceProvider serviceProvider, DbContext context)
  26. {
  27. Check.NotNull(serviceProvider, nameof(serviceProvider));
  28. _serviceProvider = serviceProvider;
  29. _dbContext = context;
  30. _repositoryFactory = serviceProvider.GetRequiredService<IRepositoryFactory>();
  31. }
  32. public DbContext DbContext { get => _dbContext; }
  33. public IReadOnlyRepository<TEntity, TKey> GetReadOnlyRepository<TEntity, TKey>()
  34. where TEntity : class, IEntity<TKey>
  35. where TKey : IEquatable<TKey>
  36. {
  37. return _repositoryFactory.GetReadOnlyRepository<TEntity, TKey>(this);
  38. }
  39. public IRepository<TEntity, TKey> GetRepository<TEntity, TKey>()
  40. where TEntity : class, IEntity<TKey>
  41. where TKey : IEquatable<TKey>
  42. {
  43. return _repositoryFactory.GetRepository<TEntity, TKey>(this);
  44. }
  45. public void Dispose()
  46. {
  47. if (_disposed)
  48. {
  49. return;
  50. }
  51. _dbContext?.Dispose();
  52. _disposed = true;
  53. }
  54. // 其他略
  55. }
  1. /// <summary>
  2. /// 数据库提供者接口
  3. /// </summary>
  4. public interface IDbProvider : IDisposable
  5. {
  6. /// <summary>
  7. /// 根据上下文类型及数据库名称获取UnitOfWork对象, dbName为null时默认为第一个数据库名称
  8. /// </summary>
  9. IUnitOfWork GetUnitOfWork(Type dbContextType, string dbName = null);
  10. }

IDbProvider 接口, 根据上下文类型和配置文件中的数据库连接字符串名称创建IUnitOfWork, 在DI中的生命周期是Scoped,在销毁的同时会销毁数据库上下文对象, 下面是它的实现, 为了提高性能使用了Expression来代替反射.

  1. public class DbProvider : IDbProvider
  2. {
  3. private readonly IServiceProvider _serviceProvider;
  4. private readonly ConcurrentDictionary<string, IUnitOfWork> _works = new ConcurrentDictionary<string, IUnitOfWork>();
  5. private static ConcurrentDictionary<Type, Func<IServiceProvider, DbContextOptions, DbContext>> _expressionFactoryDict =
  6. new ConcurrentDictionary<Type, Func<IServiceProvider, DbContextOptions, DbContext>>();
  7. public DbProvider(IServiceProvider serviceProvider)
  8. {
  9. _serviceProvider = serviceProvider;
  10. }
  11. public IUnitOfWork GetUnitOfWork(Type dbContextType, string dbName = null)
  12. {
  13. var key = string.Format("{0}${1}$", dbName, dbContextType.FullName);
  14. IUnitOfWork unitOfWork;
  15. if (_works.TryGetValue(key, out unitOfWork))
  16. {
  17. return unitOfWork;
  18. }
  19. else
  20. {
  21. DbContext dbContext;
  22. var dbConnectionOptionsMap = _serviceProvider.GetRequiredService<IOptions<FxOptions>>().Value.DbConnections;
  23. if (dbConnectionOptionsMap == null || dbConnectionOptionsMap.Count <= 0)
  24. {
  25. throw new Exception("无法获取数据库配置");
  26. }
  27. DbConnectionOptions dbConnectionOptions = dbName == null ? dbConnectionOptionsMap.First().Value : dbConnectionOptionsMap[dbName];
  28. var builderOptions = _serviceProvider.GetServices<DbContextOptionsBuilderOptions>()
  29. ?.Where(d => (d.DbName == null || d.DbName == dbName) && (d.DbContextType == null || d.DbContextType == dbContextType))
  30. ?.OrderByDescending(d => d.DbName)
  31. ?.OrderByDescending(d => d.DbContextType);
  32. if (builderOptions == null || !builderOptions.Any())
  33. {
  34. throw new Exception("无法获取匹配的DbContextOptionsBuilder");
  35. }
  36. var dbUser = _serviceProvider.GetServices<IDbContextOptionsBuilderUser>()?.FirstOrDefault(u => u.Type == dbConnectionOptions.DatabaseType);
  37. if (dbUser == null)
  38. {
  39. throw new Exception($"无法解析类型为“{dbConnectionOptions.DatabaseType}”的 {typeof(IDbContextOptionsBuilderUser).FullName} 实例");
  40. }
  41. var dbContextOptions = dbUser.Use(builderOptions.First().Builder, dbConnectionOptions.ConnectionString).Options;
  42. if (_expressionFactoryDict.TryGetValue(dbContextType, out Func<IServiceProvider, DbContextOptions, DbContext> factory))
  43. {
  44. dbContext = factory(_serviceProvider, dbContextOptions);
  45. }
  46. else
  47. {
  48. // 使用Expression创建DbContext
  49. var constructorMethod = dbContextType.GetConstructors()
  50. .Where(c => c.IsPublic && !c.IsAbstract && !c.IsStatic)
  51. .OrderByDescending(c => c.GetParameters().Length)
  52. .FirstOrDefault();
  53. if (constructorMethod == null)
  54. {
  55. throw new Exception("无法获取有效的上下文构造器");
  56. }
  57. var dbContextOptionsBuilderType = typeof(DbContextOptionsBuilder<>);
  58. var dbContextOptionsType = typeof(DbContextOptions);
  59. var dbContextOptionsGenericType = typeof(DbContextOptions<>);
  60. var serviceProviderType = typeof(IServiceProvider);
  61. var getServiceMethod = serviceProviderType.GetMethod("GetService");
  62. var lambdaParameterExpressions = new ParameterExpression[2];
  63. lambdaParameterExpressions[0] = (Expression.Parameter(serviceProviderType, "serviceProvider"));
  64. lambdaParameterExpressions[1] = (Expression.Parameter(dbContextOptionsType, "dbContextOptions"));
  65. var paramTypes = constructorMethod.GetParameters();
  66. var argumentExpressions = new Expression[paramTypes.Length];
  67. for (int i = 0; i < paramTypes.Length; i++)
  68. {
  69. var pType = paramTypes[i];
  70. if (pType.ParameterType == dbContextOptionsType ||
  71. (pType.ParameterType.IsGenericType && pType.ParameterType.GetGenericTypeDefinition() == dbContextOptionsGenericType))
  72. {
  73. argumentExpressions[i] = Expression.Convert(lambdaParameterExpressions[1], pType.ParameterType);
  74. }
  75. else if (pType.ParameterType == serviceProviderType)
  76. {
  77. argumentExpressions[i] = lambdaParameterExpressions[0];
  78. }
  79. else
  80. {
  81. argumentExpressions[i] = Expression.Call(lambdaParameterExpressions[0], getServiceMethod);
  82. }
  83. }
  84. factory = Expression
  85. .Lambda<Func<IServiceProvider, DbContextOptions, DbContext>>(
  86. Expression.Convert(Expression.New(constructorMethod, argumentExpressions), typeof(DbContext)), lambdaParameterExpressions.AsEnumerable())
  87. .Compile();
  88. _expressionFactoryDict.TryAdd(dbContextType, factory);
  89. dbContext = factory(_serviceProvider, dbContextOptions);
  90. }
  91. var unitOfWorkFactory = _serviceProvider.GetRequiredService<IUnitOfWorkFactory>();
  92. unitOfWork = unitOfWorkFactory.GetUnitOfWork(_serviceProvider, dbContext);
  93. _works.TryAdd(key, unitOfWork);
  94. return unitOfWork;
  95. }
  96. }
  97. public void Dispose()
  98. {
  99. if (_works != null && _works.Count > 0)
  100. {
  101. foreach (var unitOfWork in _works.Values)
  102. unitOfWork.Dispose();
  103. _works.Clear();
  104. }
  105. }
  106. }
  107. public static class DbProviderExtensions
  108. {
  109. public static IUnitOfWork GetUnitOfWork<TDbContext>(this IDbProvider provider, string dbName = null)
  110. {
  111. if (provider == null)
  112. return null;
  113. return provider.GetUnitOfWork(typeof(TDbContext), dbName);
  114. }
  115. }
  1. /// <summary>
  2. /// 业务系统配置选项
  3. /// </summary>
  4. public class FxOptions
  5. {
  6. public FxOptions()
  7. {
  8. }
  9. /// <summary>
  10. /// 默认数据库类型
  11. /// </summary>
  12. public DatabaseType DefaultDatabaseType { get; set; } = DatabaseType.SqlServer;
  13. /// <summary>
  14. /// 数据库连接配置
  15. /// </summary>
  16. public IDictionary<string, DbConnectionOptions> DbConnections { get; set; }
  17. }
  18. public class FxOptionsSetup: IConfigureOptions<FxOptions>
  19. {
  20. private readonly IConfiguration _configuration;
  21. public FxOptionsSetup(IConfiguration configuration)
  22. {
  23. _configuration = configuration;
  24. }
  25. /// <summary>
  26. /// 配置options各属性信息
  27. /// </summary>
  28. /// <param name="options"></param>
  29. public void Configure(FxOptions options)
  30. {
  31. SetDbConnectionsOptions(options);
  32. // ...
  33. }
  34. private void SetDbConnectionsOptions(FxOptions options)
  35. {
  36. var dbConnectionMap = new Dictionary<string, DbConnectionOptions>();
  37. options.DbConnections = dbConnectionMap;
  38. IConfiguration section = _configuration.GetSection("FxCore:DbConnections");
  39. Dictionary<string, DbConnectionOptions> dict = section.Get<Dictionary<string, DbConnectionOptions>>();
  40. if (dict == null || dict.Count == 0)
  41. {
  42. string connectionString = _configuration["ConnectionStrings:DefaultDbContext"];
  43. if (connectionString == null)
  44. {
  45. return;
  46. }
  47. dbConnectionMap.Add("DefaultDb", new DbConnectionOptions
  48. {
  49. ConnectionString = connectionString,
  50. DatabaseType = options.DefaultDatabaseType
  51. });
  52. return;
  53. }
  54. var ambiguous = dict.Keys.GroupBy(d => d).FirstOrDefault(d => d.Count() > 1);
  55. if (ambiguous != null)
  56. {
  57. throw new Exception($"数据上下文配置中存在多个配置节点拥有同一个数据库连接名称,存在二义性:{ambiguous.First()}");
  58. }
  59. foreach (var db in dict)
  60. {
  61. dbConnectionMap.Add(db.Key, db.Value);
  62. }
  63. }
  64. }
  65. /// <summary>
  66. /// DbContextOptionsBuilder配置选项
  67. /// </summary>
  68. public class DbContextOptionsBuilderOptions
  69. {
  70. /// <summary>
  71. /// 配置DbContextOptionsBuilder, dbName指定数据库名称, 为null时表示所有数据库,默认为null
  72. /// </summary>
  73. /// <param name="build"></param>
  74. /// <param name="dbName"></param>
  75. /// <param name="dbContextType"></param>
  76. public DbContextOptionsBuilderOptions(DbContextOptionsBuilder build, string dbName = null, Type dbContextType = null)
  77. {
  78. Builder = build;
  79. DbName = dbName;
  80. DbContextType = dbContextType;
  81. }
  82. public DbContextOptionsBuilder Builder { get; }
  83. public string DbName { get; }
  84. public Type DbContextType { get; }
  85. }

FxOptions是业务系统的配置选项(随便取得), 在通过service.GetService<IOptions>()时会调用IConfigureOptions完成FxOptions的初始化. DbContextOptionsBuilderOptions用来提供DbContextOptionsBuilder的相关配置

  1. public interface IDbContextOptionsBuilderUser
  2. {
  3. /// <summary>
  4. /// 获取 数据库类型名称,如 SQLSERVER,MYSQL,SQLITE等
  5. /// </summary>
  6. DatabaseType Type { get; }
  7. /// <summary>
  8. /// 使用数据库
  9. /// </summary>
  10. /// <param name="builder">创建器</param>
  11. /// <param name="connectionString">连接字符串</param>
  12. /// <returns></returns>
  13. DbContextOptionsBuilder Use(DbContextOptionsBuilder builder, string connectionString);
  14. }
  15. public class SqlServerDbContextOptionsBuilderUser : IDbContextOptionsBuilderUser
  16. {
  17. public DatabaseType Type => DatabaseType.SqlServer;
  18. public DbContextOptionsBuilder Use(DbContextOptionsBuilder builder, string connectionString)
  19. {
  20. return builder.UseSqlServer(connectionString);
  21. }
  22. }

IDbContextOptionsBuilderUser接口用来适配不同的数据库来源

使用

  1. {
  2. "FxCore": {
  3. "DbConnections": {
  4. "TestDb": {
  5. "ConnectionString": "xxx",
  6. "DatabaseType": "SqlServer"
  7. },
  8. "TestDb_Read": {
  9. "ConnectionString": "xxx",
  10. "DatabaseType": "SqlServer"
  11. }
  12. }
  13. }
  14. }
  1. class Program
  2. {
  3. static void Main(string[] args)
  4. {
  5. var config = new ConfigurationBuilder()
  6. .AddJsonFile("appsettings.json")
  7. .Build();
  8. var services = new ServiceCollection()
  9. .AddSingleton<IConfiguration>(config)
  10. .AddOptions()
  11. .AddSingleton<IConfigureOptions<FxOptions>, FxOptionsSetup>()
  12. .AddScoped<IDbProvider, DbProvider>()
  13. .AddSingleton<IUnitOfWorkFactory, UnitOfWorkFactory>()
  14. .AddSingleton<IRepositoryFactory, RepositoryFactory>()
  15. .AddSingleton<IDbContextOptionsBuilderUser, SqlServerDbContextOptionsBuilderUser>()
  16. .AddSingleton<DbContextOptionsBuilderOptions>(new DbContextOptionsBuilderOptions(new DbContextOptionsBuilder<TestDbContext>(), null, typeof(TestDbContext)));
  17. var serviceProvider = services.BuildServiceProvider();
  18. var dbProvider = serviceProvider.GetRequiredService<IDbProvider>();
  19. var uow = dbProvider.GetUnitOfWork<TestDbContext>("TestDb"); // 访问主库
  20. var repoDbTest = uow.GetRepository<DbTest, int>();
  21. var obj = new DbTest { Name = "123", Date = DateTime.Now.Date };
  22. repoDbTest.Insert(obj);
  23. uow.SaveChanges();
  24. Console.ReadKey();
  25. var uow2 = dbProvider.GetUnitOfWork<TestDbContext>("TestDb_Read");
  26. var uow2 = dbProvider.GetUnitOfWork<TestDbContext>("TestDb_Read"); // 访问从库
  27. var repoDbTest2 = uow2.GetReadOnlyRepository<DbTest, int>();
  28. var data2 = repoDbTest2.GetFirstOrDefault();
  29. Console.WriteLine($"id: {data2.Id} name: {data2.Name}");
  30. Console.ReadKey();
  31. }
  32. }

这里直接用控制台来做一个例子,中间多了一个Console.ReadKey()是因为我本地没有配置主从模式,所以实际上我是先插入数据,然后复制到另一个数据库里,再进行读取的.

总结

本文给出的解决方案适用于系统中存在多个不同的上下文,能够适应复杂的业务场景.但对已有代码的侵入性比较大,不知道有没有更好的方案,欢迎一起探讨.

EF Core 实现读写分离的最佳方案的更多相关文章

  1. EF core 实现读写分离解决方案

    我们公司2019年web开发已迁移至.NET core,目前有部分平台随着用户量增加,单一数据库部署已经无法满足我们的业务需求,一直在寻找EF CORE读写分离解决方案,目前在各大技术论坛上还没找到很 ...

  2. EntityFramework Core进行读写分离最佳实践方式,了解一下(二)?

    前言 写过上一篇关于EF Core中读写分离最佳实践方式后,虽然在一定程度上改善了问题,但是在评论中有的指出更换到从数据库,那么接下来要进行插入此时又要切换到主数据库,同时有的指出是否可以进行底层无感 ...

  3. EntityFramework Core进行读写分离最佳实践方式,了解一下(一)?

    前言 本来打算写ASP.NET Core MVC基础系列内容,看到有园友提出如何实现读写分离,这个问题提的好,大多数情况下,对于园友在评论中提出的问题,如果是值得深究或者大多数同行比较关注的问题我都会 ...

  4. Entity Framework Core 实现读写分离

    在之前的版本中我们可用构造函数实现,其实现在的版本也一样,之前来构造连接字符串,现在相似,构造DbContextOptions<T> 代码如下: public SContext(Maste ...

  5. SQL Server、MySQL主从搭建,EF Core读写分离代码实现

    一.SQL Server的主从复制搭建 1.1.SQL Server主从复制结构图 SQL Server的主从通过发布订阅来实现 1.2.基于SQL Server2016实现主从 新建一个主库&quo ...

  6. sql server几种读写分离方案的比较

    在生产环境中我们经常会遇到这种情况: 前端的oltp业务很繁忙,但是需要对这些运营数据进行olap,为了不影响前端正常业务,所以需要将数据库进行读写分离. 这里我将几种可以用来进行读写分离的方案总结一 ...

  7. 【爬坑笔记】c# 如何通过EF Core读写sql server的类似double型字段

    =============================================== 2019/8/31_第1次修改                       ccb_warlock == ...

  8. 基于 EntityFramework 的数据库主从读写分离服务插件

    基于 EntityFramework 的数据库主从读写分离服务插件 1. 版本信息和源码 1.1 版本信息 v1.01 beta(2015-04-07),基于 EF 6.1 开发,支持 EF 6.1 ...

  9. 2-18,19 搭建MySQL主从服务器并并通过mysql-proxy实现读写分离

    MySQL主从服务器 实现方式: MySQL  REPLICATION Replication可以实现将数据从一台数据库服务器(master)复制到一台或多台数据库服务器(slave) 默认情况下这种 ...

随机推荐

  1. net core天马行空系列: 泛型仓储和声明式事物实现最优雅的crud操作

    系列目录 1.net core天马行空系列:原生DI+AOP实现spring boot注解式编程 哈哈哈哈,大家好,我就是那个高产似母猪的三合,长久以来,我一直在思考,如何才能实现高效而简洁的仓储模式 ...

  2. 2018中国大学生程序设计竞赛 - 网络选拔赛 hdu 6440 Dream 模拟

    Dream Time Limit: 12000/6000 MS (Java/Others)    Memory Limit: 65536/65536 K (Java/Others)Total Subm ...

  3. CodeForces 758 C Unfair Poll

    Unfair Poll 题意:一共有n排同学每排同学有m个人, 老师问问题有一个顺序, 先从第一排开始问,问完第一排的所有同学之后,再问第2排的,对于所有排的访问顺序为 1,2,3……n-1,n,n- ...

  4. CodeForces 760 C. Pavel and barbecue(dfs+思维)

    题目链接:http://codeforces.com/contest/760/problem/C 题意:一共有N个烤炉,有N个烤串,一开始正面朝上放在N个位子上.一秒之后,在位子i的串串会移动到pi位 ...

  5. hdu 1301 Jungle Roads krusckal,最小生成树,并查集

    The Head Elder of the tropical island of Lagrishan has a problem. A burst of foreign aid money was s ...

  6. springboot中动态修改logback日志级别

    springboot中动态修改logback日志级别 在spring boot中使用logback日志时,项目运行中,想要修改日志级别. 代码如下: import org.slf4j.Logger; ...

  7. Linux中新建用户用不了sudo命令问题:rootr is not in the sudoers file.This incident will be reported解决

    参考:https://blog.csdn.net/lichangzai/article/details/39501025 如果执行sudo命令的用户没有执行sudo的权限,执行sudo命令时会报下面的 ...

  8. Spring Cloud官方文档中文版-声明式Rest客户端:Feign

    官方文档地址为:http://cloud.spring.io/spring-cloud-static/Dalston.SR2/#spring-cloud-feign 文中例子我做了一些测试在:http ...

  9. Fire Balls 11——平台组合,场景的美化

    版权申明: 本文原创首发于以下网站: 博客园『优梦创客』的空间:https://www.cnblogs.com/raymondking123 优梦创客的官方博客:https://91make.top ...

  10. CNCF 宣布成立应用交付领域小组,正式开启云原生应用时代

    作者|赵钰莹 作为云原生领域的顶级开源社区, Cloud Native Computing Foundation (云原生基金会,以下简称 CNCF)近日宣布成立 Application Delive ...