microservices

We have two separate projects as follows GAE Standard on JAVA runtime, let us say- APP1 GAE Flexible on Python runtime, let us say- APP2 We want to move both the projects in one micro-services application project with two services, say APP1service (default), and APP2service. Wanted to check if it is possible to host standard and flexible GAE services sharing one application identity in microservices setup? Quick answer is highly appreciated. ps. Google documentation does not answer this question directly and hints that it is unlikely. Yes, it is possible to have any mix of environments and

I am using current Spring boot version (1.4.x) and wondering if it has any default timeout for api calls. I have tested it by putting breakpoints but it was keep waiting and didn't time-out. I was also trying to configure default timeout for all my spring-boot apps by using some annotation or yml settings. I found couple of alternatives (one of them here ) but using callable actually adding extra non-business logic code where setting something in xml bean is out of fashion in latest spring boot applications. You can try server.connection-timeout=5000 in your application.properties.From the

原文同步至 http://waylau.com/ahout-microservices/ 自 2014 年始，Microservices（微服务）一词越来越火爆，不谈 Microservices 彷佛就 out 了。那么什么是 Microservices？Microservices 架构与传统的架构有什么区别？何时应该采用 Microservices？如何构建 Microservices？ 本文，就针对上述提到的问题，来简单介绍下 Microservices。 什么是 Microservices 微服务的诞生并非偶然: 领域驱动设计 指导我们如何分析并模型化复杂的业务； 敏捷方法论 帮助我们消除浪费，快速反馈； 持续交付 促使我们构建更快、更可靠、更频繁的软件部署和交付能力；虚拟化和基础设施自动化(Infrastructure As Code)则帮助我们简化环境的创建、安装； DevOps 文化的流行以及特性团队的出现，使得小团队更加全功能化。这些都是推动微服务诞生的重要因素。 实际上，业界对于微服务本身并没有一个严格的定义。James Lewis 和 Martin Fowler 对 Microservices 架构做了如下定义： 简言之，Microservices 架构风格就像是把小的服务开发成单一应用的形式， 运行在其自己的进程中，并采用轻量级的机制进行通信（一般是 HTTP

We have several projects that are microservices, every project is independent (running on separate spring boot server, exposing rest services, using separate DB schema...) We use maven to manage the dependencies. Is it a good idea to have a parent pom declaring each microservices as modules? And so helping to manage the common dependencies (like the lib servlet-api witch is used in every project, to remove it of all of them and declare it in only the parent pom) The 'problem' with a multi-module parent pom is that, without complicated profiles, it locks the modules in the same release cycle