design,architecture,microservices
The API Gateway pattern is a good way to implement a public API in front of a set of microservices: http://microservices.io/patterns/apigateway.html
Have your primary database publish events every time a database mutation occurs, and let the replicated services subscribe to this event and apply the same mutation on their replicated data. You already use a message broker, so you can leverage your existing stack for broadcasting the events. By having replication...
architecture,erlang,docker,elixir,microservices
This is a very open question but I will try to illustrate why Elixir/Erlang may be the best platform out there for developing distributed systems (regardless if you are working with microservices). First, let's start with some background. The Erlang VM and its standard library were designed upfront for building...
I have never worked with EJB directly but I have worked with EJB teams, mainly creating microservices that interacted (both as server and client) with the EJB services. IMHO, the big difference with EJB is that it is created to handle larger applications. There are a many aspects and technologies...
amazon-web-services,docker,elastic-beanstalk,microservices,ec2-container-service
We are currently using Amazon ECS to accomplish exactly what you are talking about trying to achieve. You can define your Docker Container as a Task definition and then Create an ECS Service which will handle number of instances, scaling, etc. One thing to note is Amazon mentions the word...
c#,.net,rest,asp.net-web-api,microservices
REST services do not have a schema or WSDL type of function to define the format of the service. This is what makes them more light weight compared to traditional web services. There is something called WADL, or Web Application Description Language, but this is not really a standard, and...
You microservice design is poor. You are modeling (location and items) 1 class = 1 microservice and this is not a good idea. You shoul modeling microservices like Aggregate Roots in DDD; even with its own bounded context. So, in your case, you should model an Aggregate Root with location,...
ruby,web-applications,docker,unix-socket,microservices
Looks like you may want to look into docker swarm, they're actively working on these use cases. I wouldn't recommend building your own communication channel, stick with http or maybe use spdy if you're really concerned about performance. Anything you introduce will make using these upcoming solutions more difficult. Also...
spring-boot,spring-integration,microservices
There is no anything specific on the matter. Spring Boot utilizes IntegrationAutoConfiguration to switch on @EnableIntegration and with that you can go ahead with best from both worlds: Boot stuff to inject, e.g. AmqpTemplate, MongoTemplate, DataSource etc. to the Spring Integration configs or use from SI XML components definitions. See...
amazon-web-services,amazon-sqs,microservices,event-based-programming
I think you are doing it wrong. It looks to me like you are using the same queue to do multiple different things. You are better of using a single queue for a single purpose. Instead of putting an event into the 'registration-new' queue and then having two different services...
send all the required data from the browser, or just the id of the house and client and the service will handle the rest? Typically, if the house and client aren't changing in this request, just send their IDs, e.g. { sale: { price: "100000.00", houseID: 123, clientID: 456...
maven,tomcat,jenkins,spring-boot,microservices
The problem is that Jenkins doesn't handle spawning child process from builds very well. Workaround suggested by @Steve in the comment (nohuping) didn't change the behaviour in my case, but a simple workaround was to schedule app's start by using the at unix command: > echo "mvn spring-boot:run" | at...
The 'problem' with a multi-module parent pom is that, without complicated profiles, it locks the modules in the same release cycle (assuming you're using the Release Plugin, which you should be). The way I work with Maven is to have a parent pom that declares: common dependencies (logging APIs, JUnit,...
json,serialization,thrift,microservices,data-interchange
As with every strongly typed system, one of the major advantanges is without a doubt that if you make mistakes, it fails early in the process, typically at the compilation stage, which is a good thing. Second biggest advantage IMHO is what you already said: because the fields and types...
node.js,docker,coreos,microservices
My take is do not use an in-container process supervisor (forever, pm2) and instead use docker restart policy via the --restart=always (or one of the other flavors of that option). This is more inline with the overall docker philosophy, and should operate very similarly to in-container process supervision since docker...
The problem you are describing is called service lookup / service registry / resource lookup / .. and it depends. It depends on how large your system is and how dynamic it is. If you only have few components, it might be feasible enough to store the necessary information in...
java,spring-integration,esb,microservices
This apparently can't be done easily at the moment. My research brings me to the conclusion the only way is to use external tools: New Relic Service Map - Commercial. Probably only diagramming running microservice systems, because it's a monitoring system. AppDynamics - Commercial. Probably only diagramming running microservice systems,...
node.js,rest,stream,microservices
This is one of the best use cases for message queues. Your basically create a queue for data to be translated by the translate service, and a queue for data which is already translated and ready to be sent back to the user. Your REST layer and translation layer publish...
spring-data-rest,hateoas,spring-cloud,microservices
The basic steps are the following ones: The service needs to discover the resources of the other service. The service then adds a link to the resources it renders where necessary. I have a very rudimentary example of these steps in this repository. The example consists of two services: a...
scala,sbt,akka,spray,microservices
The issue as it seems transitive dependency of the dependency is resulting with two different versions of metrics-core. The best thing to do would be to used the right library dependency so that you end up with a single version of this library. Please use https://github.com/jrudolph/sbt-dependency-graph , if it is...
amazon-web-services,amazon-ec2,spring-cloud,microservices,amazon-elastic-beanstalk
As mentioned in the above comments, AWS will raise your limits if you have a legit use case - why wouldn't they? they are in the business of selling you services. But since you have asked for suggestion other than increasing those limits, and since you are in the early...
php,magento,soa,single-page-application,microservices
There is nothing that says you architecture is not a MS architecture just because you're using magento and PHP. But, you have to consider a few things: Think in terms of always being able to rewrite any of the services in any language and deploy somewhere the total system should...
ruby-on-rails,ruby,multithreading,parallel-processing,microservices
Some alternatives (just brainstorming): Just drop HTTP and use pub-sub with a queue. Have the producer queueing items, a number of consumers processing them (and triggering state changes, in this case with HTTP if you fancy it). If you really want to HTTP, I think there are a couple of...
angularjs,rest,proxy,delegation,microservices
I have now evolved from n00b to n00b++ regarding Angular. The solution lies within the HTML-snippets used for templates within Angular. I can define a html template with a JS file and an HTML file. The JS file refers to the HTML page by a URL. Usually (in the samples...
c#,esb,servicebus,masstransit,microservices
The question is really about coupling. How coupled are your various services? 'Standalone' implies a level of loose coupling, but in order to interoperate, some level of coupling is required. The challenge is to couple as loosely as possible whilst maintaining the interoperability that will allow your components to work...
git,github,vagrant,fig,microservices
I decided to go with fig. If a microservice depends on another microservice fig will reference this service using ../ This assumes that all services are checked out as siblings. This can also easily be accomplished using git sub trees. My dev_ops repro contains my Vagrant file for boot2docker, etc....
web-services,oauth,oauth-2.0,microservices
As you state this is an internal use case where you control the resources protected by your Resource Server, the Authorization Server and the clients accessing the resources so you may choose to use client_credentials for accessing user data. It compares to (or actually is) a "service account" that may...