Microserver微服务框架 v1.2.6.zip

# Microserver [](https://travis-ci.org/aol/micro-server) [](https://gitter.im/aol/micro-server?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) A convenient modular engine for Microservices. Microserver plugins offer seamless integration with Spring (core), Jersey, Guava, Tomcat, Grizzly, reactive programming, Hibernate (& Spring Data), Spring Boot, Codahale Metrics, Swagger and more to come! * [Microserver screencast : getting started with plugins](https://www.youtube.com/watch?v=sYn2cVTkfcM)  ### Microserver plugins video [](https://youtu.be/sYn2cVTkfcM) ## Quick start Install Microserver with Grizzly, Jackson and Jersey (Gradle config below) ```groovy compile group: 'com.oath.microservices', name:'micro-grizzly-with-jersey', version:'x.yz' ``` Install Microserver with Tomcat, Jackson and Jersey (Gradle config below) ```groovy compile group: 'com.oath.microservices', name:'micro-tomcat-with-jersey', version:'x.yz' ``` Create and run a simple app ```java @Rest @Path("/test") public class SimpleApp { public static void main(String[] args){ new MicroserverApp(()->"test-app").run(); } @GET public String myEndPoint(){ return "hello world!"; } } ``` Browse to *http://localhost:8080/test-app/test* See the response *hello world!* Add plugins by adding them to your build file - rerun the app to get new end points, Spring beans and more! ## Easy to use async NIO based REST Return any reactive-streams Publisher from your REST end point to make them execute asynchronously automatically. E.g. Using Future from [cyclops-react](cyclops-react.io) ```java @GET public Future<String> myEndPoint(){ return Future.of(()->{ sleep(); return "hello world!"; }, Executors.newFixedThreadPool(1)); } ``` Would be equivalent to the following code ```java @GET public void myEndPoint(@Suspended AsyncResponse asyncResponse){ Future.of(()->{ sleep(); asyncResponse.resume("hello world!"); return 1; }, Executors.newFixedThreadPool(1)); } ``` # Why Microserver? Microserver is a plugin engine for building Spring and Spring Boot based microservices. Microserver supports pure microservice and micro-monolith development styles. The micro-monolith style involves packaging multiple services into a single deployment - offering developers the productivity of microservice development without the operational risk. This can help teams adopt a Microservices architecture on projects that are currently monoliths. Microserver plugins are orthogonal to Microservices. They solve a common problem in Microservice development whereby services are broken up and deployed separately but the code remains entangled in a monolithic common library. By making use of a plugin system that follows the same modular architectural principals as microservice development, teams can keep cross-service concerns and infrastructure in properly size, coherent and cohesive plugin modules. # Tutorial and overview [Tutorial](https://github.com/aol/micro-server/wiki/Getting-started-:-Tutorial) [Tutorial code](https://github.com/aol/micro-server/tree/master/micro-tutorial) ## Note on Fat Jars Microserver (& Cyclops) have a plugin architecture and make use of the Java Service Loader mechanism. Make sure your Fat Jar implementation is configured to aggregate services. With the Gradle Shadow Jar you do this with ```groovy shadowJar { mergeServiceFiles() } ``` ### Quick start youtube video [](https://www.youtube.com/watch?v=McXy9oGRpfA&feature=youtu.be) Note the main launch class has been changed from MicroServerStartup to MicroserverApp ## Blurb Microserver is a zero configuration, standards based, battle hardened library to run Java Rest Microservices via a standard Java main class. It has been used in production in AOL since July 2014. ## Get Microserver  * micro-grizzly-with-jersey [](https://maven-badges.herokuapp.com/maven-central/com.oath.microservices/micro-grizzly-with-jersey) * micro-tomcat-with-jersey [](https://maven-badges.herokuapp.com/maven-central/com.oath.microservices/micro-tomcat-with-jersey) * micro-core [](https://maven-badges.herokuapp.com/maven-central/com.oath.microservices/micro-core) * micro-boot : Microserver driving Spring Boot [](https://maven-badges.herokuapp.com/maven-central/com.oath.microservices/micro-boot) * micro-spring-boot : Spring Boot driving Microserver [](https://maven-badges.herokuapp.com/maven-central/com.oath.microservices/micro-spring-boot) ## Info [wiki](https://github.com/aol/micro-server/wiki) [Google Group](https://groups.google.com/forum/#!forum/micro-server) [Example Apps : Microserver Core with Grizzly and Jersey](https://github.com/aol/micro-server/tree/master/micro-grizzly/src/test/java/app) [Example Apps : Microserver Boot](https://github.com/aol/micro-server/tree/master/micro-boot/src/test/java/app) [Java Doc : Microserver Core](http://www.javadoc.io/doc/com.oath.microservices/micro-core/0.62) [Java Doc : Microserver Boot](http://www.javadoc.io/doc/com.oath.microservices/micro-core/0.62) ### Maven dependency Microserver Grizzly with Jersey ```xml <dependency> <groupId>com.oath.microservices</groupId> <artifactId>micro-grizzly-with-jersey</artifactId> <version>x.yz</version> </dependency> ``` Microserver Spring Boot ```xml <dependency> <groupId>com.oath.microservices</groupId> <artifactId>micro-spring-boot</artifactId> <version>x.yz</version> </dependency> ``` ### Gradle dependency Microserver core ```groovy compile group: 'com.oath.microservices', name:'micro-core', version:'x.yz' ``` Microserver Spring Boot ```groovy compile group: 'com.oath.microservices', name:'micro-spring-boot', version:'x.yz' ``` ## Tech Stack Microserver core is a lightweight server configuration engine built using Spring, Cyclops and Jackson. ## Zero Configuration No directory structure is imposed by the server and no XML is required. There is no framework config. Just a jar file and your application. You can, of course, configure your application without limit. Example working application :- ### The main class :- ```java public class AppRunnerTest { public static void main(String[] args) throws InterruptedException { new MicroserverApp(() -> "test-app").run(); } } ``` This will deploy a REST server on port 8080 (configurable by test-app.port in application.properties), it will also automagically capture any Rest