WSO2 Microservices Framework for Java (MSF4J)

Related tags

Microservice msf4j
Overview

Build status: Build Status

WSO2 Microservices Framework for Java (MSF4J)

WSO2 Microservices Framework for Java (MSF4J) is a lightweight high performance framework for developing & running microservices.

WSO2 MSF4J is one of the highest performing lightweight Java microservices frameworks. The following graphs show the throughput, memory consumption & latency characteristics of MSF4J against other microservices frameworks.

EchoThroughput

An echo service which accepts a 1KB request & echoes it back directly and using a temp file was developed for the respective frameworks, and requests were sent for different concurrency values. The test was repeated for each concurrency value for each framework and the average throughput was calculated. Tests were run out of the box without any tuning on 32 core 64GB server in JVM v1.8.0_60 with default configuration.

EchoMemory

Memory usage for each framework was observed after running the 1KB payload echo microservice on each framework & sending a number of requests at different concurrency levels to each service. The graph above shows the averaged out values after several runs for each framework.

Latency results was observed using the Apache bench provided percentile values. Results were plotted for various concurrency levels the simple echo test.

MeanLatency

Tests were run out of the box without any tuning on 32 core 64GB server in JVM v1.8.0_60 with default configuration.

More details about the performance test can found here.

Hello world with MSF4J

It is really easy to define & deploy a Java microservice using WSO2 MSF4J. You simply need to annotate your service and deploy it using a single line of code.

Let's get started by writing a hello world MSF4J microservice.

You can use the msf4j-microservice Maven archetype to create your first MSF4J project. Make sure you have JDK 1.8 and Maven 3.x installed, & run the following command.

mvn archetype:generate -DarchetypeGroupId=org.wso2.msf4j \
-DarchetypeArtifactId=msf4j-microservice -DarchetypeVersion=2.6.2 \
-DgroupId=org.example -DartifactId=Hello-Service -Dversion=0.1-SNAPSHOT \
-Dpackage=org.example.service -DserviceClass=HelloService

This will generate a project structure for you to quickly get started. Next navigate to the Hello-Service directory. You will find a pom.xml file and also an src directory.

pom.xml

This pom file inherits from the msf4j-service/pom.xml. It provides a way of setting things up quickly with minimum amount of configuration. Click here for more information.

<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 http://maven.apache.org/xsd/maven-4.0.0.xsd">

    <parent>
        <groupId>org.wso2.msf4j</groupId>
        <artifactId>msf4j-service</artifactId>
        <version>2.6.2</version>
    </parent>
    <modelVersion>4.0.0</modelVersion>

    <groupId>org.example</groupId>
    <artifactId>Hello-Service</artifactId>
    <version>0.1-SNAPSHOT</version>
    <name>WSO2 MSF4J Microservice</name>

    <properties>
        <microservice.mainClass>org.example.service.Application</microservice.mainClass>
    </properties>

</project>

You don't need to change anything in this pom.xml file.

HelloService.java

Change the org.example.service.HelloService class as follows to echo back the name input parameter. You can remove the auto generated code and replace it with the following code segment:

package org.example.service; 

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;

@Path("/hello")
public class HelloService {

    @GET
    @Path("/{name}")
    public String hello(@PathParam("name") String name) {
        return "Hello " + name;
    }

}

Application.java

This is the one-liner to deploy your service using WSO2 MSF4J.

public class Application {
    public static void main(String[] args) {
        new MicroservicesRunner()
                .deploy(new HelloService())
                .start();
    }
}

You can also pass in the port(s) as an argument to the MicroservicesRunner class constructor. When passing the port(s) as an argument, by default it binds to 0.0.0.0 host. Use "msf4j.host" environment variable to override the host value.

Build the Service

Run the following Maven command. This will create the fat jar Hello-Service-0.1-SNAPSHOT.jar in the target directory.

mvn package

This fat jar is a jar file that contains your microservice as well as all its dependencies.

Run the Service

You just have to run the following command to get your service up and running.

java -jar target/Hello-Service-*.jar

Test the Service with cURL

Run the following command or simply go to [http://localhost:8080/hello/wso2] (http://localhost:8080/hello/wso2) from your browser.

curl http://localhost:8080/hello/wso2

You should see a response that prints "Hello wso2"

Supported Annotations

In this section, we will look at the annotations used in MSF4J microservices. As you may have already noticed, we support a subset of the JAXRS annotations.

Class level annotations

@Path

Root path for resource methods. All the paths specified in the resource methods will be sub paths of this.

@Consumes

Default consume media type(s) for resource methods. The resource methods that do not specify @Consume annotation will inherit this consume media type(s).

@Produces

Default produce media type(s) for resource methods. The resource methods that do not specify @Produce annotation will inherit this produce media type(s).

Method level annotations

@Path

Endpoint of the resource method relative to @Path of the container resource class.

@Consumes

Media type(s) that the method can consume. This overrides the class level @Consumes media types.

@Produces

Media type(s) that is produced by the method. This overrides the class level @Produces media types.

@GET

HTTP GET method. Specify that the resource method supports HTTP GET method.

@PUT

HTTP PUT method. Specify that the resource method supports HTTP PUT method.

@POST

HTTP POST method. Specify that the resource method supports HTTP POST method.

@DELETE

HTTP DELETE method. Specify that the resource method supports HTTP DELETE method.

@HEAD

HTTP HEAD method. Specify that the resource method supports HTTP HEAD method.

@OPTIONS

HTTP OPTIONS method. Specify that the resource method supports HTTP OPTIONS method.

Parameter level annotations

@DefaultValue

Specify a default value for a resource method parameter. The value will be automatically converted to the corresponding parameter's type.

@Context

Inject additional objects to a resource method. Currently supports injection of the following objects.

  • org.wso2.msf4j.Request - This object can be used to access properties of the HTTP request. The transport session (org.wso2.msf4j.Session) can also be accessed via org.wso2.msf4j.Request#getSession(). See the Session-aware service sample.
  • org.wso2.msf4j.Response - This object can be used to send HTTP responses. You can make responses more clean way by returning an instance of javax.ws.rs.core.Response or a POJO. See the [StockQuote-Service] (samples/stockquote/fatjar) sample.
  • org.wso2.msf4j.HttpStreamer - This object can be used to stream a chunked request body and process it while the request is streaming. See the FileServer sample.
  • org.wso2.msf4j.formparam.FormParamIterator - This object can be used to stream a HTML form submission request body and process it while the request is streaming. See the FormParam sample.
@PathParam

/StockQuote/{symbol} to get value of symbol. The value will be automatically converted to the corresponding parameter type and assigned to that parameter.

@QueryParam

/Students?age=18 to get value of age. The value will be automatically converted to the corresponding parameter type and assigned to that parameter.

@HeaderParam

To read HTTP request header values. The value will be automatically converted to the corresponding parameter type and assigned to that parameter.

@CookieParam

Extracts the value from the specified cookie, converts to the corresponding parameter type and assigns the value to that parameter.

@FormParam

To support HTML form submission with application/x-www-form-urlencoded and multipart/form-data The value will be automatically converted to the corresponding parameter type and assigned to that parameter

@FormDataParam

To support complex form submission with multipart/form-data content type. E.g file uploads and beans. The values will be automatically converted to the corresponding parameter type and assigned to that parameter

Lifecycle Callback Methods

Support following Java lifecycle callback method annotations.

@PostConstruct

Invoke by the container on newly constructed service instances after all dependency injection has completed and before transport starts.

@PreDestroy

Invoke by the container during server shutdown before the container removes the service instance.

For a detailed example, check out the lifecycle sample here.

MSF4J Interceptors

Please do refer the following for complete instructions.

Develop and configure MSF4J services using Spring framework

Spring is a popular Java application development framework which supports concepts like Dependency Injection(DI) and Convention over Configuration. Spring support for MSF4J provides following features.

  1. Develop MSF4J services as Spring beans
  2. Develop and configure MSF4J components such as Interceptors and ExceptionMappers using Spring.
  3. Use Annotation or XML based Spring configuration to configure internals of MSF4J framework such as ports, SSL etc.

Following example illustrates how to use Spring annotations together with MSF4J annotations to build a RESTful service. The main advantage here is service developers can consume Spring features such as dependency injection , Spring AOP etc. in the Spring way.

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

import javax.ws.rs.GET;
import javax.ws.rs.Path;

@Component
@Path("/greeting")
public class Hello {

    @Autowired
    private HelloService helloService;

    @GET
    public String message() {
        return helloService.hello(" World");
    }
}

For further details refer Spring Helloworld sample.

Annotations for Analytics

In this section, we will look at the annotations available for analytics purposes MSF4J microservices. There are annotations for Metrics and HTTP Monitoring.

You will need to configure analytics when you want to publish Metrics and HTTP Monitoring events to WSO2 Data Analytics Server (DAS).

The Metrics data will be published to WSO2 DAS periodically. However the HTTP Monitoring events are published on each request.

For a detailed example, check out the Metrics and HTTP Monitoring sample.

Metrics Annotations

You can use the Metrics annnotations in your MSF4J microservices to understand how your microservices work in production.

There are three metrics annotations supported. Those are @Counted, @Metered and @Timed.

Each metric must have a unique name and the MSF4J will use the fully qualified method name as the metric name by default. You can give a custom name by using the "name" parameter. This custom name will be appended to the fully qualified method name with a dot character. You can set the "absolute" parameter to "true" if you want use only the given name as the metric name.

For example, see following table to understand how the final metric name is built by the Metrics runtime. Let's asssume that the annotation is added to the "hello" method of "HelloService" shown above.

Metrics Annotation Metric Name
@Counted org.example.service.HelloService.hello
@Counted(name = "helloCounter") org.example.service.HelloService.hello.helloCounter
@Counted(name = "helloCounter", absolute = true) helloCounter

The Metrics annotations can be used at the Method level and Class level.

You can also configure a level in Metrics Annotations. For more information about Metric Levels, see WSO2 Carbon Metrics. In MSF4J, you can load the metrics level configuration via the System Property named metrics.level.conf.

@Counted

Count the method invocations. There is a parameter named "monotonic" and it is set to false by default. This means that the counter is decremented when the method returns. This is useful to count the current invocations of the annotated method.

Use @Counted(monotonic = true) when you want the counter to increase monotonically. This is useful to count the total invocations of the annotated method

@Metered

Measure the rate of method invocations. This also keeps a count of the total invocations of the annotated method.

@Timed

Maintain a histogram of durations of each method invocation. This also measures the rate of method invocations and keeps a count of the total invocations of the annotated method.

HTTP Monitoring Annotation

You can use the annotation provided for HTTP Monitoring when you want to monitor each HTTP request and see the summary in "HTTP Monitoring Dashboard".

@HTTPMonitored

Monitor each HTTP request. This annotation can be used at the Class level and the Method level.

HTTP Message Tracing

MSF4J supports visual message tracing through user friendly dashboards in WSO2 DAS or Zipkin. MSF4J message tracing provides a detailed insight to the complex microservices interactions in a system making monitoring, trouble shooting and optimization of microservices very easy. Please check WSO2 DAS Tracing and Zipkin Tracing samples for more details.

Swagger Annotations

Swagger is a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection.

MSF4J supports all Swagger annotations out of the box.

To enable swagger support you need to add the following dependency to your project

<dependency>
     <groupId>org.wso2.msf4j</groupId>
     <artifactId>msf4j-swagger</artifactId>
     <version>2.6.2</version>
</dependency>

In order to retrieve Swagger definitions of your microservice, go to
http://<host>:<port>/swagger?path=<service_base_path>.

e.g. http://localhost:8080/swagger?path=/hello

To retrieve Swagger definitions of all microservices in your runtime, go to http://<host>:<port>/swagger.

e.g. http://localhost:8080/swagger

NOTE: Even without any Swagger annotation, default Swagger definitions will be generated using the JAXRS annotation in your MSF4J microservice.

The StockQuote sample demonstrates Swagger annotations in action.

ExceptionMapper

MSF4J supports JAXRS ExceptionMapper which allows creation of custom responses when exceptions are thrown from MSF4J services.

The StockQuote sample demonstrates ExceptionMapper in action.

The following code segment shows how ExceptionMappers are registered with the MSF4J runtime.

new MicroservicesRunner().addExceptionMapper(new SymbolNotFoundMapper(), new DuplicateSymbolMapper());

Circuit Breaker

Nygard's circuit breaker pattern is supported in MSF4J using the Netflix Hystrix library. For more details see the circuit breaker sample

Complete Feature List

  • Annotation based definition of microservices
  • High performance Netty based transport
  • WSO2 Developer Studio based tooling for microservices development starting from a Swagger API definition
  • Generate Swagger definition using Swagger annotations
  • Ability to develop and Configure MSF4J services using Spring framework
  • HTTP request & response streaming including support for javax.ws.rs.core.StreamingOutput.
  • ExceptionMapper
  • Support for metrics & visualization of metrics using WSO2 Data Analytics Server (DAS) dashboards
  • Message tracing with WSO2 DAS or Zipkin to get a detailed visual insight to the microservices interactions
  • Supports circuit breaker using Netflix Hystrix.
  • Support for securing microservices
  • Integration with rendering engines such as Mustache
  • Comprehensive samples demonstrating how to develop microservices based solutions
Comments
  • First time and try msf4j

    First time and try msf4j

    after maven new project, msf4j gennerate Application.java and MyService.java

    Run Application.java and ERROR

    Exception in thread "main" java.lang.NoClassDefFoundError: org/wso2/carbon/kernel/transports/CarbonTransport
        at org.example.service.Application.main(Application.java:28)
    Caused by: java.lang.ClassNotFoundException: org.wso2.carbon.kernel.transports.CarbonTransport
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        ... 1 more
    
    opened by magixsource 11
  • Normalize @Path values by always stripping leading and trailing /

    Normalize @Path values by always stripping leading and trailing /

    JAX-RS spec says that leading or trailing spaces of path values should be ignored. This allows to use either @Path("hello") or @Path("/hello"). Implement by trimming slashes and also replacing multiple / with a single one.

    Purpose

    Resolves #479

    Approach

    Add Utils.normalizePath and call where necessary

    Automation tests

    • Unit tests

      Modified and tested with "helloworld" sample

    Security checks

    • Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
    • Ran FindSecurityBugs plugin and verified report? yes
    • Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

    Samples

    Modified "helloworld" to no longer use "/" in path names

    opened by nkiesel 8
  • first time try ms4j

    first time try ms4j

    [INFO] Reactor Summary: [INFO] [INFO] WSO2 MSF4J - Parent Pom ............................ SUCCESS [ 4.941 s] [INFO] JAX-RS Delegates ................................... SUCCESS [ 8.873 s] [INFO] WSO2 MSF4J core .................................... FAILURE [ 3.272 s] [INFO] WSO2 MSF4J Spring .................................. SKIPPED [INFO] MSF4J-Parent ....................................... SKIPPED [INFO] WSO2 MSF4J Analytics ............................... SKIPPED . . . . [INFO] Sample: PathParam with Regex ....................... SKIPPED [INFO] WSO2 MSF4J OSGi tests .............................. SKIPPED [INFO] msf4j .............................................. SKIPPED [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 19.355 s [INFO] Finished at: 2016-07-18T11:21:46+05:30 [INFO] Final Memory: 49M/176M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.16:check (validate) on project msf4j-core: Failed during checkstyle execution: There are 16 errors reported by Checkstyle 6.2 with https://raw.githubusercontent.com/wso2/code-quality-tools/master/checkstyle/checkstyle.xml ruleset.

    i used mvn archetype:generate -DarchetypeGroupId=org.wso2.msf4j \ -DarchetypeArtifactId=msf4j-microservice -DarchetypeVersion=1.0.0 \ -DgroupId=org.example -DartifactId=Hello-Service -Dversion=1.0.0 \ -Dpackage=org.example.service -DserviceClass=HelloService as in quick start guidelines

    opened by lahirumadushanka 6
  • Solve issue in Request.getSession() method, when extracting Cookie header

    Solve issue in Request.getSession() method, when extracting Cookie header

    Purpose

    This PR solve the issue when retrieving the JSESSIONID in the Cookie header. Related issue #452

    Goals

    Resolve issue #452

    Approach

    Use .map(String::trim) function when extracting Cookie header.

    User stories

    When there exist multiple Cookie values in Cookie header separated by ;.

    As an example when there is Cookie header like Cookie:BSESSIONID=<cookie-value>;<space>JSESSIONID=<cookie-value>, then request.getSession() function split and get the JSESSIONID. Since it doesn't trim, it unable to find out correct session and because of that, it creates a new session instead of getting the previous session.

    Security checks

    • Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
    • Ran FindSecurityBugs plugin and verified report? no
    • Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

    Samples

    http-session

    Test environment

    java version "1.8.0_144" , OS - Linux Ubuntu, Browser - Chrome

    opened by BuddhiWathsala 5
  • Packages not found

    Packages not found

    I have created a new project in eclipse based on the archetype as specified in the documentation. When this has been created I get the following errors in the pom.xml file:

    Multiple annotations found at this line:
      - Missing artifact commons-io.wso2:commons-io:jar:2.4.0.wso2v1
      - Missing artifact org.wso2.carbon.transport:org.wso2.carbon.transport.http.netty:jar:2.1.2
      - Missing artifact org.wso2.carbon.messaging:org.wso2.carbon.messaging:jar:1.0.4
    

    These packages are declared in the parent pom.

    I have tried forcing an update of the snapshots as well as running maven clean install but these fail with the same errors. I have looked in the central maven repo but can't find these packages.

    I am using Eclipse neon with Java 1.8.

    opened by benhjt 5
  • Maven Archetype 2.0.0 not found

    Maven Archetype 2.0.0 not found

    Hello, I want to try the new msf4j framework but there is an error when trying to create the project with maven archetype. It tells that archetype version 2.0.0 does not exist. I've tried with version 1.0.0 with success but the generated code does not match the tutorial.

    Regards

    Samuel

    opened by hayaofr 5
  • Please update samples structure of netty-transports yaml file

    Please update samples structure of netty-transports yaml file

    Description:

    Using the below netty-transports file, getting following error:

    Unable to find property 'bossThreadPoolSize' on class: org.wso2.carbon.transport.http.netty.config.ListenerConfiguration in 'reader', line 21, column 23: bossThreadPoolSize: 2

    The same happens for workerThreadPoolSize

    I had to remove both properties from netty-transports.yml file to make it work. Now, using thread pooling configuration from deployment.yaml

    Affected Product Version: 2.4.X

    OS, DB, other environment details and versions:
    macos high Sierra 10.13

    Steps to reproduce: Run the built fat jar from target directory with -Dtransports.netty.conf=netty-transports.yml

    netty-transports.yml:

    listenerConfigurations:

    id: "msf4j-http" host: "127.0.0.1" port: 8080 bossThreadPoolSize: 2 workerThreadPoolSize: 250 parameters: - name: "execThreadPoolSize" value: 60

    • id: "msf4j-https" host: "127.0.0.1" port: 8443 bossThreadPoolSize: 2 workerThreadPoolSize: 250 scheme: https keyStoreFile: "conf/wso2carbon.jks" keyStorePass: wso2carbon certPass: wso2carbon
    opened by suchostone 4
  • Doesn't send a response when an interceptor returns a 'false'

    Doesn't send a response when an interceptor returns a 'false'

    When an interceptor returns a 'false' (e.g. in some authentication interceptor upon an authentication failure) an HTTP response is not sent. So that the client waits for a request and finally a timeout happens.

    Type/Bug 
    opened by rushmin 4
  • Location support in Response

    Location support in Response

    We are going to use below snippets in order to do POST request with 201 response. We want to send the Created resource location through the Response. Once we implement that we came up with below stack trace.

    WARN {org.wso2.msf4j.internal.MSF4JMessageProcessor} - Unmapped exception java.lang.UnsupportedOperationException at org.wso2.msf4j.delegates.MSF4JResponse$Builder.location(MSF4JResponse.java:334) at javax.ws.rs.core.Response.created(Response.java:699) at org.wso2.carbon.apimgt.rest.api.publisher.impl.ApisApiServiceImpl.apisPost(ApisApiServiceImpl.java:260) at org.wso2.carbon.apimgt.rest.api.publisher.ApisApi.apisPost(ApisApi.java:425) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:132) at org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:130) at org.wso2.msf4j.internal.MSF4JMessageProcessor.receive(MSF4JMessageProcessor.java:72) at org.wso2.carbon.transport.http.netty.listener.WorkerPoolDispatchingSourceHandler.lambda$publishToWorkerPool$12(WorkerPoolDispatchingSourceHandler.java:125) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    https://github.com/wso2/carbon-apimgt/blob/a94893c66473febc597b2895afe329ceccb1fbd3/components/apimgt/org.wso2.carbon.apimgt.rest.api.publisher/src/main/java/org/wso2/carbon/apimgt/rest/api/publisher/impl/ApisApiServiceImpl.java#L260

    enhancement 
    opened by tharindu1st 4
  • Duplicate README files found in the distribution

    Duplicate README files found in the distribution

    @afkham @thusithathilina It seems like there are two README files in [1]. Shouldn't it be better to move the content in README.txt to README.md and remove README.txt?

    [1] https://github.com/wso2/msf4j/tree/master/distribution/binary

    enhancement 
    opened by imesh 3
  • Sending response message to client if an interceptor returns false

    Sending response message to client if an interceptor returns false

    With the current implementation interceptors need to specifically invoke response.send() method for sending the response message back to the client:

    public abstract class AbstractBasicAuthSecurityInterceptor implements Interceptor {
        ...
    
        @Override
        public boolean preCall(Request request, Response responder, ServiceMethodInfo serviceMethodInfo) throws Exception {
            ...
            responder.setStatus(javax.ws.rs.core.Response.Status.UNAUTHORIZED.getStatusCode());
            responder.setHeader(javax.ws.rs.core.HttpHeaders.WWW_AUTHENTICATE, AUTH_TYPE_BASIC);
            responder.send();
            return false;
        }
        ...
    }
    

    This pull request improves this logic by invoking response.send() method in MSF4JMessageProcessor.dispatchMethod() if an interceptor returns false when Interceptor.preCall() is invoked.

    opened by imesh 3
  • Bump logback-core from 1.0.9 to 1.2.9 in /poms/parent

    Bump logback-core from 1.0.9 to 1.2.9 in /poms/parent

    Bumps logback-core from 1.0.9 to 1.2.9.

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump snakeyaml from 1.23 to 1.31 in /poms/parent

    Bump snakeyaml from 1.23 to 1.31 in /poms/parent

    Bumps snakeyaml from 1.23 to 1.31.

    Commits
    • a3e641b Remove unused code for comments
    • d2ed568 Remove unused code
    • ab76f86 Add @​Deprecated annotation to constructs marked with @​deprecated javadoc.
    • bc7869b Make billionLaughsAttackTest.billionLaughsAttackExpanded() robust
    • 4cfb7b7 Merged in make-billion-laughs-attack-test-robust (pull request #7)
    • da5ba16 Update changes.xml
    • 23fbcef add test with JavaBean property of parameterized Collection
    • 6385279 change how we set detected type to JavaBean Collection property item
    • 0468784 force keyNode to be String for JavaBeans
    • 467bcc9 expect node to be scalar when enforcings String keys
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump opensaml from 2.4.1 to 2.6.6 in /samples/jwt-claims/sso-agent-for-jwt-webapp

    Bump opensaml from 2.4.1 to 2.6.6 in /samples/jwt-claims/sso-agent-for-jwt-webapp

    Bumps opensaml from 2.4.1 to 2.6.6.

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump nimbus-jose-jwt from 2.25 to 7.9 in /poms/parent

    Bump nimbus-jose-jwt from 2.25 to 7.9 in /poms/parent

    Bumps nimbus-jose-jwt from 2.25 to 7.9.

    Changelog

    Sourced from nimbus-jose-jwt's changelog.

    version 1.0 (2012-03-01)

    • First version based on the OpenInfoCard JWT, JWS and JWE code base.

    version 1.1 (2012-03-06)

    • Introduces type-safe enumeration of the JSON Web Algorithms (JWA).
    • Refactors the JWT class.

    version 1.2 (2012-03-08)

    • Moves JWS and JWE code into separate classes.

    version 1.3 (2012-03-09)

    • Switches to Apache Commons Codec for Base64URL encoding and decoding
    • Consolidates the crypto utilities within the package.
    • Introduces a JWT content serialiser class.

    version 1.4 (2012-03-09)

    • Refactoring of JWT class and JUnit tests.

    version 1.5 (2012-03-18)

    • Switches to JSON Smart for JSON serialisation and parsing.
    • Introduces claims set class with JSON objects, string, Base64URL and byte array views.

    version 1.6 (2012-03-20)

    • Creates class for representing, serialising and parsing JSON Web Keys (JWK).
    • Introduces separate class for representing JWT headers.

    version 1.7 (2012-04-01)

    • Introduces separate classes for plain, JWS and JWE headers.
    • Introduces separate classes for plain, signed and encrypted JWTs.
    • Removes the JWTContent class.
    • Removes password-based (PE820) encryption support.

    version 1.8 (2012-04-03)

    • Adds support for the ZIP JWE header parameter.
    • Removes unsupported algorithms from the JWA enumeration.

    version 1.9 (2012-04-03)

    • Renames JWEHeader.{get|set}EncryptionAlgorithm() to JWEHeader.{get|set}EncryptionMethod().

    version 1.9.1 (2012-04-03)

    • Upgrades JSON Smart JAR to 1.1.1.

    version 1.10 (2012-04-14)

    • Introduces serialize() method to base abstract JWT class.

    version 1.11 (2012-05-13)

    • JWT.serialize() throws checked JWTException instead of

    ... (truncated)

    Commits
    • 10dce4f b64 works with JWTClaimsSet
    • 40b1fcf Adds new static X509CertUtils.parseWithException methods
    • 805fce1 [maven-release-plugin] prepare release 7.6
    • 1a72c5f [maven-release-plugin] prepare for next development iteration
    • af733f9 Changes JWSObject#serialize(boolean) method signature (iss #320)
    • d752e17 Merge branch 'fixB64'
    • 3fa65f3 Change log for 7.7
    • 1abe7c2 [maven-release-plugin] prepare release 7.7
    • dd19a71 [maven-release-plugin] prepare for next development iteration
    • 7f4dbc0 Issue #325 Enhancement: Add an optional proxy support to the DefaultResourceR...
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • Bump gson from 2.2.4 to 2.8.9 in /poms/parent

    Bump gson from 2.2.4 to 2.8.9 in /poms/parent

    Bumps gson from 2.2.4 to 2.8.9.

    Release notes

    Sourced from gson's releases.

    Gson 2.8.9

    • Make OSGi bundle's dependency on sun.misc optional (#1993).
    • Deprecate Gson.excluder() exposing internal Excluder class (#1986).
    • Prevent Java deserialization of internal classes (#1991).
    • Improve number strategy implementation (#1987).
    • Fix LongSerializationPolicy null handling being inconsistent with Gson (#1990).
    • Support arbitrary Number implementation for Object and Number deserialization (#1290).
    • Bump proguard-maven-plugin from 2.4.0 to 2.5.1 (#1980).
    • Don't exclude static local classes (#1969).
    • Fix RuntimeTypeAdapterFactory depending on internal Streams class (#1959).
    • Improve Maven build (#1964).
    • Make dependency on java.sql optional (#1707).

    Gson 2.8.8

    • Fixed issue with recursive types (#1390).
    • Better behaviour with Java 9+ and Unsafe if there is a security manager (#1712).
    • EnumTypeAdapter now works better when ProGuard has obfuscated enum fields (#1495).
    Changelog

    Sourced from gson's changelog.

    Version 2.8.9

    • Make OSGi bundle's dependency on sun.misc optional (#1993).
    • Deprecate Gson.excluder() exposing internal Excluder class (#1986).
    • Prevent Java deserialization of internal classes (#1991).
    • Improve number strategy implementation (#1987).
    • Fix LongSerializationPolicy null handling being inconsistent with Gson (#1990).
    • Support arbitrary Number implementation for Object and Number deserialization (#1290).
    • Bump proguard-maven-plugin from 2.4.0 to 2.5.1 (#1980).
    • Don't exclude static local classes (#1969).
    • Fix RuntimeTypeAdapterFactory depending on internal Streams class (#1959).
    • Improve Maven build (#1964).
    • Make dependency on java.sql optional (#1707).

    Version 2.8.8

    • Fixed issue with recursive types (#1390).
    • Better behaviour with Java 9+ and Unsafe if there is a security manager (#1712).
    • EnumTypeAdapter now works better when ProGuard has obfuscated enum fields (#1495).

    Version 2.8.7

    • Fixed ISO8601UtilsTest failing on systems with UTC+X.
    • Improved javadoc for JsonStreamParser.
    • Updated proguard.cfg (#1693).
    • Fixed IllegalStateException in JsonTreeWriter (#1592).
    • Added JsonArray.isEmpty() (#1640).
    • Added new test cases (#1638).
    • Fixed OSGi metadata generation to work on JavaSE < 9 (#1603).

    Version 2.8.6

    2019-10-04 GitHub Diff

    • Added static methods JsonParser.parseString and JsonParser.parseReader and deprecated instance method JsonParser.parse
    • Java 9 module-info support

    Version 2.8.5

    2018-05-21 GitHub Diff

    • Print Gson version while throwing AssertionError and IllegalArgumentException
    • Moved utils.VersionUtils class to internal.JavaVersion. This is a potential backward incompatible change from 2.8.4
    • Fixed issue google/gson#1310 by supporting Debian Java 9

    Version 2.8.4

    2018-05-01 GitHub Diff

    • Added a new FieldNamingPolicy, LOWER_CASE_WITH_DOTS that mapps JSON name someFieldName to some.field.name
    • Fixed issue google/gson#1305 by removing compile/runtime dependency on sun.misc.Unsafe

    Version 2.8.3

    2018-04-27 GitHub Diff

    • Added a new API, GsonBuilder.newBuilder() that clones the current builder
    • Preserving DateFormatter behavior on JDK 9

    ... (truncated)

    Commits
    • 6a368d8 [maven-release-plugin] prepare release gson-parent-2.8.9
    • ba96d53 Fix missing bounds checks for JsonTreeReader.getPath() (#2001)
    • ca1df7f #1981: Optional OSGi bundle's dependency on sun.misc package (#1993)
    • c54caf3 Deprecate Gson.excluder() exposing internal Excluder class (#1986)
    • e6fae59 Prevent Java deserialization of internal classes (#1991)
    • bda2e3d Improve number strategy implementation (#1987)
    • cd748df Fix LongSerializationPolicy null handling being inconsistent with Gson (#1990)
    • fe30b85 Support arbitrary Number implementation for Object and Number deserialization...
    • 1cc1627 Fix incorrect feature request template label (#1982)
    • 7b9a283 Bump bnd-maven-plugin from 5.3.0 to 6.0.0 (#1985)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • Bump commons-io from 2.5 to 2.7 in /perf-benchmark/Samples/ninja-echo-message

    Bump commons-io from 2.5 to 2.7 in /perf-benchmark/Samples/ninja-echo-message

    Bumps commons-io from 2.5 to 2.7.

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
Releases(v2.4.0)
  • v2.4.0(Sep 22, 2017)

    WSO2 MSF4J is a lightweight, high performance microservices runtime. It also provides a very simple programming model for developing Java based microservices.

    Source code(tar.gz)
    Source code(zip)
  • v2.2.1(Apr 4, 2017)

    WSO2 MSF4J is a lightweight, high performance microservices runtime. It also provides a very simple programming model for developing Java based microservices.

    This release of the WSO2 MSF4J includes the following key features. For further details please refer to the Product Page.

    Source code(tar.gz)
    Source code(zip)
  • v2.1.1(Feb 15, 2017)

    WSO2 MSF4J is a lightweight, high performance microservices runtime. It also provides a very simple programming model for developing Java based microservices. This release of the WSO2 MSF4J includes some minor bug fixes for 2.1.0

    Source code(tar.gz)
    Source code(zip)
  • v2.1.0(Nov 24, 2016)

    WSO2 MSF4J is a lightweight, high performance microservices runtime. It also provides a very simple programming model for developing Java based microservices.

    This release of the WSO2 MSF4J includes the following key features. For further details please refer to the Product Page.

    What’s New in This Release

    • HTTP session support
    • Cookie support
    • JAX-RS sub-resource support
    • Ability to run different services on different ports within the same runtime
    • Message tracing support for DAS
    • Pet store deployment based on docker compose
    • Ability to register services with dynamic paths
    • Feign based MSF4J Client Support
    • Spring Configuration externalization support based on YAML and properties files

    In addition to the above features, MSF4J supports analysis with visualization with WSO2 Data Analytics Server (DAS), and includes a set of comprehensive samples which demonstrate how to use MSF4J features and build Microservices Architecture (MSA) based solutions. The base pack is also reduced significantly and now it is around 5 MB. This release also includes several bug fixes to the previous version of MSF4J.

    How you can contribute

    We welcome contributors: head over to wso2.com/community to find out more. If you have any suggestions or are interested in WSO2 MSF4J 2.1.0 discussions, please join the [email protected] or [email protected] mailing lists.

    Reporting Issues

    Please report issues and documentation errors regarding WSO2 MSF4J 2.1.0 through the Github issue tracking system

    Source code(tar.gz)
    Source code(zip)
  • v2.0.0(Jul 22, 2016)

    WSO2 MSF4J is a lightweight, high performance microservices runtime. It also provides a very simple programming model for developing Java based microservices.

    This release of the WSO2 MSF4J includes the following key features. For further details please refer to the Product Page.

    What’s New in This Release

    • Spring support MSF4J now supports Spring annotations and runtime
    • Swagger support Generate Swagger definitions for your microservices and annotate services using Swagger annotations
    • Exception mapper support Allows mapping of Java exceptions to custom HTTP responses
    • Streaming output support Provides full control over streaming to the service developer
    • FormParam and FormDataParam annotation support Provides support to handle x-form-application-urlencoded and multipart/form-data requests with form submission
    • FormParamIterator support Provides full control to the developer over form field processing
    • Circuit breaker support Nygard’s circuit breaker pattern is supported via Netflix Hystrix
    • Improved thread model and transport architecture Netty and execution thread pools can now be customized according to the required service characteristics

    In addition to the above features, MSF4J supports analysis with visualization with WSO2 Data Analytics Server (DAS), and includes a set of comprehensive samples which demonstrate how to use MSF4J features & build Microservices Architecture (MSA) based solutions. This release also includes several bug fixes to the previous version of MSF4J. To find out more, visit the MSF4J product page.

    How you can contribute

    We welcome contributors: head over to wso2.com/community to find out more. If you have any suggestions or are interested in WSO2 MSF4J 2.0.0 discussions, please join the [email protected] or [email protected] mailing lists.

    Reporting Issues

    Please report issues and documentation errors regarding WSO2 MSF4J 2.0.0 through the public issue tracking system.

    Source code(tar.gz)
    Source code(zip)
  • v1.0.0(Feb 15, 2016)

    WSO2 MSF4J provides a lightweight, high performance microservices runtime in addition to a very simple programming model for developing Java based microservices.

    This release of the WSO2 MSF4J includes the following key features. For further details please see the Product Page.

    Key Features

    • Annotation based definition of microservices
    • High performance Netty based transport
    • WSO2 Developer Studio based tooling for microservices development starting from a Swagger API definition
    • HTTP request and response streaming
    • Custom interceptors
    • Support for metrics & visualization of metrics using WSO2 Data Analytics Server (DAS) dashboards
    • Support for securing microservices
    • Integration with rendering engines such as Mustache
    • Comprehensive samples demonstrating how to develop microservices based solutions
    Source code(tar.gz)
    Source code(zip)
    wso2msf4j-dist-1.0.0.zip(18.30 MB)
  • v1.0.0-RC6(Feb 12, 2016)

    When developing MSF4J applications, we need to use several poms provided by MSF4J. Since they are not yet uploaded to the maven central, we have to add the MSF4J maven repo url to the project to resolve them. For that, the following segment should be added to the project pom before building. So to test this RC, please add the following segment to your pom.xml files (in the samples etc)

    <repositories>
        <repository>
            <id>wso2-nexus</id>
            <url>http://maven.wso2.org/nexus/content/repositories/orgwso2-333</url>
        </repository>
    </repositories>
    
    Source code(tar.gz)
    Source code(zip)
    wso2msf4j-dist-1.0.0.zip(18.30 MB)
  • v1.0.0-RC5(Feb 10, 2016)

    When developing MSF4J applications, we need to use several poms provided by MSF4J. Since they are not yet uploaded to the maven central, we have to add the MSF4J maven repo url to the project to resolve them. For that, the following segment should be added to the project pom before building. So to test this RC, please add the following segment to your pom.xml files (in the samples etc)

    <repositories> <repository> <id>wso2-nexus</id> <url>http://maven.wso2.org/nexus/content/repositories/orgwso2-327/</url> </repository> </repositories>

    Source code(tar.gz)
    Source code(zip)
    wso2msf4j-dist-1.0.0.zip(18.30 MB)
  • v1.0.0-alpha(Oct 31, 2015)

    WSO2 Microservices Server 1.0.0-alpha Released!

    We are pleased to announce the 1.0.0-alpha release of WSO2 Microservices Server (MSS), which is the very first public release of this new product from WSO2. It is now available to download from here. The source and tag location for this release are available here.

    WSO2 MSS provides a lightweight, high performance microservices runtime in addition to a very simple programming model for developing Java based microservices.

    The alpha release of WSO2 MSS 1.0.0-alpha includes the following key features. For further details please see the documentation.

    Key Features

    • Quick & simple development model using simple annotations • Lightweight & high performance • Custom interceptors • JWT based security • Metrics gathering & publishing to WSO2 Data Analytics Server • Dashboard showing metrics as well as microservice request/response statistics • Request streaming support • WSO2 DevStudio based tooling for generating microservices projects starting from a Swagger API definition • Comprehensive samples demonstrating how to develop microservices application, also showing how to deploy & manage the deployment using Docker & Kubernetes

    Samples

    A good place to start with WSO2 MSS is by running the samples included in the release. Refer to the README files in the sample directories on how to build & run the samples.

    How To Contribute

    If you have any suggestions or are interested in WSO2 MSS discussions, you can join the [email protected] mailing list.

    Reporting Issues

    We encourage you to report issues, documentation errors regarding WSO2 MSS 1.0.0-alpha through the public issue tracking system.

    Thanks, WSO2 Microservices Server Team

    Source code(tar.gz)
    Source code(zip)
    wso2mss-1.0.0-alpha.zip(20.27 MB)
Owner
WSO2
Welcome to the WSO2 source code! For info on working with the WSO2 repositories and contributing code, click the link below.
WSO2
Lightweight framework for building java microservices

Ja-micro Ja-micro is a lightweight Java framework for building microservices. Introduction Ja-micro is a framework that allows developers to easily de

Sixt 621 Aug 21, 2022
Microserver is a Java 8 native, zero configuration, standards based, battle hardened library to run Java Rest Microservices via a standard Java main class. Supporting pure Microservice or Micro-monolith styles.

Microserver is a Java 8 native, zero configuration, standards based, battle hardened library to run Java Rest Microservices via a standard Java main class. Supporting pure Microservice or Micro-monolith styles.

AOL 936 Dec 19, 2022
Sample application demonstrating an order fulfillment system decomposed into multiple independant components (e.g. microservices). Showing concrete implementation alternatives using e.g. Java, Spring Boot, Apache Kafka, Camunda, Zeebe, ...

Sample application demonstrating an order fulfillment system decomposed into multiple independant components (e.g. microservices). Showing concrete implementation alternatives using e.g. Java, Spring Boot, Apache Kafka, Camunda, Zeebe, ...

Bernd Ruecker 1.2k Dec 14, 2022
Source Code for 'Pro Java Microservices with Quarkus and Kubernetes' by Nebrass Lamouchi

Apress Source Code This repository accompanies Pro Java Microservices with Quarkus and Kubernetes by Nebrass Lamouchi (Apress, 2021). Download the fil

Apress 24 Oct 31, 2022
Takin is an Java-based, open-source system designed to measure online or test environmental performance test for full-links, Especially for microservices

Takin is an Java-based, open-source system designed to measure online environmental performance test for full-links, Especially for microservices. Through Takin, middlewares and applications can identify real online traffic and test traffic, ensure that they enter the right databases.

ShulieTech 1.2k Dec 21, 2022
A powerful flow control component enabling reliability, resilience and monitoring for microservices. (面向云原生微服务的高可用流控防护组件)

Sentinel: The Sentinel of Your Microservices Introduction As distributed systems become increasingly popular, the reliability between services is beco

Alibaba 20.4k Dec 31, 2022
ColocationSim: Simulate Colocation Datacenter in a Fine Granularity with Microservices and Interference Modeling

ColocationSim Introduction 将在线作业和离线作业混合部署在同一集群(简称混部,Colocation)提升数据中心资源利用率的主流方法,如何在保证在线作业性能的前提下最大化集群的资源利用率成为混部相关研究中最主要问题。混部作业调度算法从集群层面解决这一问题,是学术界、企业界的

null 93 Jan 4, 2023
KBE Spring Boot Microservices

SFG Beer Works - Brewery Microservices This project has a services of microservices for deployment via Docker Compose and Kubernetes. You can access t

John Thompson 29 Nov 2, 2022
Apache Dubbo is a high-performance, java based, open source RPC framework.

Apache Dubbo Project Apache Dubbo is a high-performance, Java-based open-source RPC framework. Please visit official site for quick start and document

The Apache Software Foundation 38.3k Jan 9, 2023
LINE 4.1k Jan 2, 2023
A simple rpc framework.

werpc 微RPC 介绍 A simple rpc framework —— werpc. RPC(Remote Procedure Call):远程过程调用,像调用本地方法一样调用远程过程。采用Client-Server结构,通过request-response消息模式实现。 RPC框架就是指封

stubbornwdb 29 Dec 5, 2022
Cloud native multi-runtime microservice framework

Femas: Cloud native multi-runtime microservice framework Show me femas username:admin password:123456 If you like,star fork it and join us English | 简

PolarisMesh 352 Apr 23, 2022
[JAVA] Projeto exemplo de uma arquitetura modular em Java

Arquitetura modular O objetivo do bom design de software, como já diria Robert C. Martin, em seu livro 'Clean Architecture: A Craftsman's Guide to Sof

HelpDEV 97 Dec 29, 2022
Java client for Consul HTTP API

consul-api Java client for Consul HTTP API (http://consul.io) Supports all API endpoints (http://www.consul.io/docs/agent/http.html), all consistency

Ecwid 402 Jan 6, 2023
Define Java service providers by annotating them directly

Annotated Service Provider Define JVM service providers by annotating the provider class directly. This annotation processor will add to the class-pat

Emily 5 Oct 31, 2021
Lightweight framework for building java microservices

Ja-micro Ja-micro is a lightweight Java framework for building microservices. Introduction Ja-micro is a framework that allows developers to easily de

Sixt 621 Aug 21, 2022
A fast, lightweight and more productive microservices framework

A fast, lightweight and cloud-native microservices framework. Stack Overflow | Google Group | Gitter Chat | Subreddit | Youtube Channel | Documentatio

null 3.5k Jan 5, 2023
💡极致性能的企业级Java服务器框架,RPC,游戏服务器框架,web应用服务器框架。(Extreme fast enterprise Java server framework, can be RPC, game server framework, web server framework.)

?? 为性能而生的万能服务器框架 ?? Ⅰ. zfoo简介 ?? 性能炸裂,天生异步,Actor设计思想,无锁化设计,基于Spring的MVC式用法的万能RPC框架 极致序列化,原生集成的目前二进制序列化和反序列化速度最快的 zfoo protocol 作为网络通讯协议 高可拓展性,单台服务器部署,

null 1k Jan 1, 2023