Swipe to navigate through the chapters of this book
By now, we’ve read about Spring and dependency injection, along with topics like web services (particularly REST services), transaction, persistence, and security. These are likely to be the "most important" parts of the Spring ecosystem, generally speaking, but we’ve barely scratched the surface of the Spring ecosystem itself, much less projects that use Spring without being part of the Spring project.
Please log in to get access to this content
”Reactive programming is programming with asynchronous data streams” is taken from https://gist.github.com/staltz/868e7e9bc2a7b8c1f754 , which summarizes reactive programming quite well, despite some adult language that may not be perfectly appropriate for some minors.
This definition is shamelessly taken verbatim from https://aws.amazon.com/message-queue/ – we wanted to write our own purely original definition but this one kept being better than everything we came up with.
For topics, “safe” means slightly different things. If there are no listeners for a pub/sub topic, the messages sent to the topic tend to vanish: imagine saying something in an empty room and you’ll have an example of what would happen. There’s nobody to listen, so whatever you said will be lost. With a queue, however, it’s more like a bulletin board; put a message on a bulletin board, and a consumer will pick up the message when they come by.
A “projection,” if you aren’t aware, is a custom collection of fields, normally in the context of a database query of some kind. If you were to request a name from one source and an account balance from a different source, that’d be called a “projection.” Yes, this is awfully stuffy.
- Next Steps
Joseph B. Ottinger
- Sequence number
- Chapter number
- Chapter 11