Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Reference_description_with_linked_URLs____________________Notes____________________________________________________________


https://microservices.io/Microservices

file:///Users/jimmason/Google%20Drive/_docs/howto/jee/frameworks/
Comparing_Java_REST_API_Frameworks_-_jconf.dev_2020.pdf

Comparing_Java_REST_API_Frameworks_-_jconf.dev_2020.pdf

https://drive.google.com/file/d/1vr5_jae2KghjIOyB6cpix47KB7fwUv5d/
view?usp=sharing

Raible - compare Java REST Micronaut, Quarkus, Spring Boot

work w Grails, JHipster front ends



REST tutorials
https://dzone.com/articles/rest-api-your-guide-to-getting-started-quicklyREST tutorial with Swagger and Docker - Dzone




models
https://microservices.io/patterns/data/event-sourcing.htmlevent sourcing vs current state for entities
https://microservices.io/Microservices patterns


...

https://microservices.io/patterns/data/event-sourcing.html

problem

How to reliably/atomically update the database and publish messages/events?

forces

2PC - 2 phase commit not an option

solution

A good solution to this problem is to use event sourcing. Event sourcing persists the state of a business entity such an Order or a Customer as a sequence of state-changing events. Whenever the state of a business entity changes, a new event is appended to the list of events. Since saving an event is a single operation, it is inherently atomic. The application reconstructs an entity’s current state by replaying the events.

...

Code Block
languagejava
titleOrder class
collapsetrue
public class Order extends ReflectiveMutableCommandProcessingAggregate<Order, OrderCommand> {

  private OrderState state;
  private String customerId;

  public OrderState getState() {
    return state;
  }

  public List<Event> process(CreateOrderCommand cmd) {
    return EventUtil.events(new OrderCreatedEvent(cmd.getCustomerId(), cmd.getOrderTotal()));
  }

  public List<Event> process(ApproveOrderCommand cmd) {
    return EventUtil.events(new OrderApprovedEvent(customerId));
  }

  public List<Event> process(RejectOrderCommand cmd) {
    return EventUtil.events(new OrderRejectedEvent(customerId));
  }

  public void apply(OrderCreatedEvent event) {
    this.state = OrderState.CREATED;
    this.customerId = event.getCustomerId();
  }

  public void apply(OrderApprovedEvent event) {
    this.state = OrderState.APPROVED;
  }


  public void apply(OrderRejectedEvent event) {
    this.state = OrderState.REJECTED;
  }


Here is an example of an event handler in the CustomerService that subscribes to Order events:


Code Block
languagejava
titleCustomerService class
collapsetrue
@EventSubscriber(id = "customerWorkflow")
public class CustomerWorkflow {

  @EventHandlerMethod
  public CompletableFuture<EntityWithIdAndVersion<Customer>> reserveCredit(
          EventHandlerContext<OrderCreatedEvent> ctx) {
    OrderCreatedEvent event = ctx.getEvent();
    Money orderTotal = event.getOrderTotal();
    String customerId = event.getCustomerId();
    String orderId = ctx.getEntityId();

    return ctx.update(Customer.class, customerId, new ReserveCreditCommand(orderTotal, orderId));
  }

}

...

see m Services: SOAP, REST, API

Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are

  • Highly maintainable and testable
  • Loosely coupled
  • Independently deployable
  • Organized around business capabilities
  • Owned by a small team

The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an organization to evolve its technology stack.




Potential Value Opportunities

...