org.factcast:factcast-server-rest

factcast is a 'good enough' event store using PostgreSQL for persistence, and offers REST and GRPC interfaces.

License	The Apache Software License, Version 2.0
GroupId	org.factcast
ArtifactId	factcast-server-rest
Last Version	0.0.10
Release Date	Sep 11, 2018
Type	jar
Description	factcast is a 'good enough' event store using PostgreSQL for persistence, and offers REST and GRPC interfaces.
Project Organization	Mercateo AG

Download factcast-server-rest

Filename	Size
factcast-server-rest-0.0.10.pom
factcast-server-rest-0.0.10.jar	54 KB
factcast-server-rest-0.0.10-tests.jar	41 KB
factcast-server-rest-0.0.10-sources.jar	20 KB
factcast-server-rest-0.0.10-javadoc.jar	144 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.factcast/factcast-server-rest/ -->
<dependency>
    <groupId>org.factcast</groupId>
    <artifactId>factcast-server-rest</artifactId>
    <version>0.0.10</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.factcast/factcast-server-rest/
implementation 'org.factcast:factcast-server-rest:0.0.10'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.factcast/factcast-server-rest/
implementation ("org.factcast:factcast-server-rest:0.0.10")

Apache Buildr

'org.factcast:factcast-server-rest:jar:0.0.10'

Apache Ivy

<dependency org="org.factcast" name="factcast-server-rest" rev="0.0.10">
  <artifact name="factcast-server-rest" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.factcast', module='factcast-server-rest', version='0.0.10')
)

Scala SBT

libraryDependencies += "org.factcast" % "factcast-server-rest" % "0.0.10"

Leiningen

[org.factcast/factcast-server-rest "0.0.10"]

Dependencies

compile (8)

Group / Artifact	Type	Version
org.springframework.boot : spring-boot-starter-jersey	jar
org.glassfish.hk2 : spring-bridge	jar	2.5.0-b36
com.mercateo.rest : rest-schemagen-spring	jar	0.1.17
org.factcast : factcast-core	jar	0.0.10
org.glassfish.jersey.media : jersey-media-sse	jar	2.25.1
org.springframework.boot : spring-boot-starter-actuator	jar
com.google.guava : guava	jar
com.google.code.findbugs : annotations	jar	3.0.1u2

provided (1)

Group / Artifact	Type	Version
org.projectlombok : lombok	jar

test (14)

Group / Artifact	Type	Version
org.springframework.boot : spring-boot-starter-jetty	jar
org.junit.platform : junit-platform-engine	jar	1.2.0
org.junit.platform : junit-platform-runner	jar	1.2.0
org.junit.vintage : junit-vintage-engine	jar	5.2.0
org.junit.jupiter : junit-jupiter-migrationsupport	jar	5.2.0
org.mockito : mockito-core	jar
org.factcast : factcast-store-inmem	jar	0.0.10
org.factcast : factcast-core	test-jar	0.0.10
io.github.restdocsext : restdocsext-jersey	jar	0.1.1
org.glassfish.jersey.core : jersey-client	jar	2.25.1
org.glassfish.jersey.test-framework.providers : jersey-test-framework-provider-inmemory	jar	2.25.1
com.mercateo.rest : rest-hateoas-client	jar	0.1.0
org.springframework : spring-test	jar
org.assertj : assertj-core	jar

Project Modules

There are no modules declared in this project.

Announcement

Please be aware that there is a friendly fork over at https://github.com/factcast/factcast/ from 0.1.0 on, that may or may not diverge from this repo.

FactCast

is a 'good enough' event store using PostgreSQL for persistence, and offers remoting via GRPC.

This project is not yet ready for primetime

It is not yet released, the API may change, the documentation is incomplete.

... under active development.

The Problem at hand

In a micro-service world, teams choose their own tools of trade. This is a very important benefit of using Microservices in the first place, and you do not want to mess with this principle. However, where Subsystems communicate with each other (most likely crossing those team borders) you need some common ground. Event Sourcing is a great pattern here (as well as within those subsystems) because of the decoupling effect of its use.

So, what is needed is some technical solution, that everyone can easily agree on, because it forces as little technical dependencies on the clients as possible. GRPC and similar technological choices provide this solution as well as streaming, so we have all we need. Oh and one thing: Whatever solution we choose to store and stream forward needs to be failure tolerant, somewhat scalable and should pose minimal operational complexity and overhead to an existing system.

This is where some of the above solutions pose a possible problem:

While all of them are most probably great, when it comes to clustering, backup, data-/application-management and fail-over, none of these are trivial problems and most of them bring their own (certainly great) solution.

Gee, i wish there was a solution, that is flexible, platform neutral and could be operated at scale with what we already know...

Read more on factcast.org

Detailed changlelog

the procurement platform for your business

Versions

Version
0.0.10 Sep 11, 2018
0.0.6 Apr 3, 2018