JMS: only java, it is a specification
AMPQ: universal, it is a protocol, it is open standard for messaging
JMS doesn't define a protocol.
JMS is an API and AMQP is a protocol.
AMQP supports 4 message models: Direct, Fanout, Topic, Headers
| public static long getWeekends(final LocalDate start, final LocalDate end) { | |
| final DayOfWeek startDayOfWeek = start.getDayOfWeek(); | |
| final DayOfWeek endDayOfWeek = end.getDayOfWeek(); | |
| final long days = ChronoUnit.DAYS.between(start, end); | |
| final long weekends = ((days + startDayOfWeek.getValue())/7); | |
| return weekends + (endDayOfWeek == DayOfWeek.FRIDAY ? 1 : 0); | |
| } |
| # Use envFrom to load Secrets and ConfigMaps into environment variables | |
| apiVersion: apps/v1beta2 | |
| kind: Deployment | |
| metadata: | |
| name: mans-not-hot | |
| labels: | |
| app: mans-not-hot | |
| spec: | |
| replicas: 1 |
9 March, 2019
We were discussing with @erusev what we can do with async operation when using useReducer() in our application. Our app is simple and we don't want to use a state management library. All our requirements are satisfied with using one root useReducer(). The problem we are facing and don't know how to solve is async operations.
In a discussion with Dan Abramov he recommends Solution 3 but points out that things are fresh with hooks and there could be better ways of handling the problem.
Thank you everybody, Your comments makes it better
sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"Integrate JMH (Java Microbenchmarking Harness) with Spring (Boot) and make developing and running benchmarks as easy and convinent as writing tests.
Wrap the necessary JMH boilerplate code within JUnit to benefit from all the existing test infrastructure Spring (Boot) provides. It should be as easy and convinent to write benchmarks as it is to write tests.
| @startuml | |
| ' uncomment the line below if you're using computer with a retina display | |
| ' skinparam dpi 300 | |
| !define Table(name,desc) class name as "desc" << (T,#FFAAAA) >> | |
| ' we use bold for primary key | |
| ' green color for unique | |
| ' and underscore for not_null | |
| !define primary_key(x) <b>x</b> | |
| !define unique(x) <color:green>x</color> | |
| !define not_null(x) <u>x</u> |