apollo

国内一些开源框架(软件)的整理

旧街凉风 提交于 2019-12-06 16:10:11
#很出名的就不介绍了,例如dubbo、RocketMQ、FastJson、Druid等 一、Elastic-Job--当当网 简介:Elastic-Job是当当网大牛基于Zookepper,Quartz开发并且开源的Java分布式定时任务,解决Quartz不支持分布式的弊端。 官网: http://elasticjob.io/ github: https://github.com/elasticjob/elastic-job-lite 二、Apollo--携程 简介:Apollo(阿波罗)是携程框架部门研发的分布式配置中心,能够集中化管理应用不同环境、不同集群的配置,配置修改后能够实时推送到应用端,并且具备规范的权限、流程治理等特性,适用于微服务配置管理场景。 github: https://github.com/ctripcorp/apollo 三、CAT--美团点评 简介:CAT 是基于 Java 开发的实时应用监控平台,为美团点评提供了全面的实时监控告警服务。 github: https://github.com/dianping/cat 四、Arthas--阿里巴巴 Arthas 是Alibaba开源的Java诊断工具,深受开发者喜爱。在线排查问题,无需重启;动态跟踪Java代码;实时监控JVM状态。 Arthas 支持JDK 6+,支持Linux/Mac/Windows

GraphQL Query Runs Sucessfully One Time and Fails To Run Again using Apollo and AWS AppSync

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-06 15:51:54
I'm using the basic client configuration from the example on the first page of https://github.com/awslabs/aws-mobile-appsync-sdk-js repo: const client = new AWSAppSyncClient({ url: appSyncConfig.graphqlEndpoint, region: appSyncConfig.region, auth: { type: appSyncConfig.authenticationType, apiKey: appSyncConfig.apiKey, } }); But without the <Rehydrated> component, and with a Redux <Provider> component. The highest level parent component is wrapped like this: <Provider store={store}> <ApolloProvider client={client}> <App/> </ApolloProvider> </Provider> I've tried swapping the order for the

Redux-thunk: `dispatch is not a function`

半城伤御伤魂 提交于 2019-12-06 15:12:37
So, I'm having an issue with an action returning the above mentioned error (See attached image), instead of updating redux state as expected. What am I overlooking here? actionCreators.js export function userToken(token) { console.log('userToken has been fired'); return (dispatch) => { dispatch({ type: 'Graphcool_Token', payload: token }); } } App.js .... // Root Query const allPostsCommentsQuery = graphql(All_Posts_Comments_Query, { options: { cachePolicy: 'offline-critical', fetchPolicy: 'cache-first', }, }); export const mapDispatchToProps = (dispatch) => { return bindActionCreators

ApolloGraphql FileNotFoundException: source/apollo/generatedIR/debug/src (Is a directory)

最后都变了- 提交于 2019-12-06 11:22:45
I am trying to add ApolloGraphql to my android project, but when i try to rebuild the project, i get : org.gradle.api.UncheckedIOException: java.io.FileNotFoundException: /Users/mcebotari/Downloads/Projects/Barcloud/app/build/generated/source/apollo/generatedIR/snapshotDebug/src (Is a directory) in build.gradle i have added the needed dependencies: apply plugin: 'com.android.application' apply plugin: 'kotlin-android' apply plugin: 'kotlin-android-extensions' apply plugin: 'kotlin-kapt' apply plugin: 'com.apollographql.android' android { compileSdkVersion 27 defaultConfig { applicationId

Sentinel基于Apollo的持久化改造

亡梦爱人 提交于 2019-12-06 07:51:38
Sentinel基于Apollo的持久化改造 sentinel默认是将用户在dashboard中编辑过的流控信息保存在内存中,所以在重启后,所有之前配置过的流控规则也就不见了。但是sentinel给用户提供了可扩展的接口,用户可以根据自己熟悉的持久化引擎来做一定的相应的改造(apollo、nacos、zookeeper)。这里首先要了解下sentinel的规则管理和推送方式 规则管理和推送 一般来说,规则的管理和推送有以下三种方式: 推送模式 | 说明 | 优点 | 缺点 | --- | --- | --- | --- | 默认模式 | API 将规则推送至客户端并直接更新到内存中,扩展写数据源 | 简单,无任何依赖 | 不保证一致性;规则保存在内存中,重启即消失。严重不建议用于生产环境 | pull 模式 | 扩展写数据源(WritableDataSource), 客户端主动向某个规则管理中心定期轮询拉取规则,这个规则中心可以是 RDBMS、文件(数据库保存) 等 | 简单,无任何依赖;规则持久化 | 不保证一致性;实时性不保证,拉取过于频繁也可能会有性能问题。 push 模式 | 扩展读数据源(ReadableDataSource),规则中心统一推送,客户端通过注册监听器的方式时刻监听变化,比如使用 Nacos、Zookeeper 等配置中心。这种方式有更好的实时性和一致性保证

What are the differences between Apollo Client and Relay? [closed]

☆樱花仙子☆ 提交于 2019-12-06 07:10:49
问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 2 years ago . I have just been introduced to GraphQL and am deciding between the two frameworks (Apollo and Relay) for implementing my front end React web app. I'm aware that Relay is built by Facebook, while Apollo is by Meteor. Has anyone tried both and how has your experience been? I'm

Apollo readQuery Fails Even Though Target Object is Present?

岁酱吖の 提交于 2019-12-06 07:04:38
I'm working on a call to readQuery. I'm getting an error message: modules.js?hash=2d0033b4773d9cb6f118946043f7a3d4385825fe:25847 Error: Can't find field resolutions({"id":"Resolution:DHSzPa8bvPCDjuAac"}) on object (ROOT_QUERY) { "resolutions": [ { "type": "id", "id": "Resolution:AepgCCio9KWGkwyMC", "generated": false }, { "type": "id", "id": "Resolution:DHSzPa8bvPCDjuAac", // <==ID I'M SEEKING "generated": false } ], "user": { "type": "id", "id": "User:WWv57KsvqWeAoBNHY", "generated": false } }. The object with that id appears to be plainly visible as the second entry in the list of

spring cloud zuul 集成 spring config、eureka 实现动态路由

社会主义新天地 提交于 2019-12-06 06:56:24
1.添加相关依赖包 <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.1.4.RELEASE</version> <relativePath/> <!-- lookup parent from repository --> </parent> <groupId>com.hht.zool</groupId> <artifactId>demo</artifactId> <version>0.0.1-SNAPSHOT</version> <name>demo<

Apollo updateQueries Not Called?

有些话、适合烂在心里 提交于 2019-12-06 06:11:36
I'm studying Apollo pub-sub in GitHunt-React and GitHunt-API. When I run those apps and enter a new comment, the comment is saved by the call to submit, and then the updateQueries codeblock runs here: const CommentsPageWithMutations = graphql(SUBMIT_COMMENT_MUTATION, { props({ ownProps, mutate }) { console.log('in CommentsPageWithMutations'); return { submit({ repoFullName, commentContent }) { <==RUNS THE MUTATION debugger; return mutate({ variables: { repoFullName, commentContent }, optimisticResponse: { __typename: 'Mutation', submitComment: { __typename: 'Comment', id: null, postedBy:

ActiveMQ to Apollo transition, Openwire to Stomp protocol configuration

二次信任 提交于 2019-12-06 05:58:49
I'm trying to switch from ActiveMQ 5.6 to Apollo 1.5. I have two soft that are exchanging messages, using publish/subscribe on topics. The first one is c++ and use openwire with tcp The second one is Javascript and use stomp with websockets With ActiveMQ everything worked fine, and the messages I sent could be read and write on both softs, and I didn't changed the clients since. Now, I send messages from the c++ soft (using openwire), and try to read them with the JS soft, and I get errors. In fact I receive message with header content-type: "protocol/openwire", but I expect stomp. this is how