Last week (6/11/17 - 12/11/17) we focused on some core refactorings in how our dependencies are managed and organized across all our repositories. We found some issues and we are planning to fixed them one by one. @igdianov presented on friday a session about GraphQL subscriptions and a PoC to bring those features into our new component called activiti-cloud-notifications. This will enable our services to push notifications via the STOMP protocol to all interested parties. We are also working hard to get some examples with our brand new Activiti Cloud Connectors, to demonstrate how you can scale our services based on demand when hosting in a Cloud Infrastructure such as Kubernetes.
@willkzhou worked on Elasticsearch repository implementation for querying Tasks and Process Instances. Testing this coming week before committing current code.
@daisuke-yoshimoto only updated Runtime Bundle Endpoints to use content type header instead of PATH.
@igdianov worked on a GraphQL subscription mechanism for Tasks and Process Intances, new RFC post coming. Polished PoC and explored using Spring WebSocket Message Broker for better and more robust web application messaging backbone. This week I am going to prepare and commit PoC in development branch, explore integration with Apollo GraphQL client library and expand RFC descriptions for review and discussion.
@constantin-ciobotaru - out on holidays -
@lucianoprea working on Spring REST docs for Activiti Cloud Services Audit
@balsarori worked on our first iteration of our new Form Service, which is an evolution of the form services provided in version 6.x
@ffazzini working on kubernetes probes, swagger fixes in audit and query services
@ryandawsonuk - out on holidays -
@erdemedeiros added badges to all the repositories and checked that the quality tools were properly set. Currently working with @salaboy to improve the dependency management across the repositories.
@salaboy worked on improving our Swagger contract for runtime bundles and improved dependency management for all our repositories to be more aligned with JGitflow practices. A blog post about our lesson learned with maven, multi repositories and Jgitflow is coming.
This week is going to be all about Cloud Connectors and refining our services to support Spring Cloud Contracts and Spring Rest Docs. We are going to provide some examples on how you can test our services against their contracts without the need of starting an instance. We are also working on a Feign generated client for our runtime bundles, so you can leverage the power of service discovery, circuit breakers and much more for service to service interactions.
Ping us in Gitter if you want to contribute: https://gitter.im/Activiti/Activiti7