Disclaimer: most of this post is subjective. No attempt has been made here to strictly define anything, just trying to contextualize and give a global overview of the concepts and how they relate to each other. I thought I knew what REST/”RESTFul”, restfulservices, webservices, SOA and microservices I’d say that all these terms fall into … Read more
There are some errors that should not be retried because they seem permanent: 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 409 Conflict – it depends 410 Gone 411 Length Required 412 Precondition Failed 413 Payload Too Large 414 URI Too Long … Read more
I didn’t read the article, so I can only speculate what he can mean exactly, but as he gives ESB as an example against microservices and ZeroMQ as an example for micro services I hope my speculation will be pretty exact: One of the ideas of Unix (and Linux) is to build small independent applications … Read more
It seems that your dependency <dependency> <groupId>com.h2database</groupId> <artifactId>h2</artifactId> <scope>runtime</scope> </dependency> has to be in dependencies element, not in dependencyManagement. Just look at this. Or maybe you have a child artifact, in that case you must share another pom xml.
Heroku is a very simple Platform-as-a-Service company. The way Heroku works is very straightforward: You have multiple projects (services) in Git repos. You create a Heroku app for each project (each Git repo). You then push your code from each Git repo to their respective Heroku app. Heroku assigns you a public URL for each … Read more
You can use a single shared database with tables that owned by different microservices if your data is heavily related. Also in case you have strong requirements on data consistency and availiblty of a service. There is pros and cons. Pros Reliability You can have totally consistent incremental backup of the entire system without downtime … Read more
Microservices in my own, hopefully simple terms Monoliths Traditionally web applications are big. You write one piece of software that runs on a server and answers requests in form of HTML, XML or JSON. If you want your web application to do something new, you add that functionality to the existing application. Such big systems … Read more
Of course you can. Microservices are just REST-Services. You need to understand how REST-Services work. After that just write 2 Microservices (2 Rest-Services: producer-service and consumer-service) with Spring-boot, let them run under different server-ports, call the consumer-service from the other, and that’s it: you have your Microservices. Now this is the primitive way to write … Read more
I’ve had a fair amount of experience with microservices and local development and here’s been some approaches I’ve seen: Run all the things locally on docker or k8. If using k8, then a tool like skaffolding can make it easier to run and debug a service locally in the IDE but put it into your … Read more
With Docker Toolbox that’s a little tricky, but actually the core-2.0 has nothing to do here. It’s all about docker, docker-toolbox, and VS. First of all: Is this the way one is supposed to start up that docker services? I have tried running this executable, and it seems to be working. Yes it is. If … Read more