|
7 | 7 |
|
8 | 8 | The Spring Boot for {geode-name} (SBDG) project includes the `org.springframework.geode:apache-geode-extensions` module |
9 | 9 | to make use of the {geode-name} {apache-geode-javadoc}[APIs] in a Spring and non-Spring application context more |
10 | | -effective. While this module is relatively new, it contains several, necessary API extensions already. |
| 10 | +effective. While this module is relatively new, it already contains several necessary API extensions. |
11 | 11 |
|
12 | | -{geode-name} {apache-geode-javadoc}[APIs] are quite complex and difficult to use properly, especially without prior |
13 | | -knowledge or experience to do so. Users very often get things wrong and is the main reason why Spring's APIs |
14 | | -for {geode-name} are invaluable; they lead users to do the right thing from the start, first and foremost. |
| 12 | +{geode-name} {apache-geode-javadoc}[APIs] can be complex and difficult to use properly, especially without prior |
| 13 | +knowledge or experience. Users often get things wrong, which is why Spring's APIs |
| 14 | +for {geode-name} are invaluable. They lead users to do the right thing from the start, first and foremost. |
15 | 15 |
|
16 | | -However, this module does not simply exist only to help users use {geode-name}'s APIs more effectively. In fact, with |
17 | | -Spring's abstractions, it should not be necessary to use {geode-name} APIs at all, e.g. like when using the Spring Cache |
| 16 | +However, this module does not exist only to help users use {geode-name}'s APIs more effectively. In fact, with |
| 17 | +Spring's abstractions, it should not be necessary to use {geode-name} APIs at all -- for example, when using the Spring Cache |
18 | 18 | Abstraction for caching or the Spring Data Repository abstraction for DAO development. This module is necessary |
19 | | -to enable Spring for {geode-name} to overcome and adapt to the limitations the API in a Spring and application context |
20 | | -in order to do what Spring for {geode-name} needs to do that makes the experience familiar to Spring users. |
| 19 | +to enable Spring for {geode-name} to overcome and adapt to the limitations of the API in a Spring application context. |
| 20 | +That lets Spring for {geode-name} offer an experience familiar to Spring users. |
21 | 21 |
|
22 | | -In general, Spring shields users from design problems as well as changes in 3rd party library APIs, which could |
| 22 | +In general, Spring shields users from design problems as well as changes in third party library APIs that could |
23 | 23 | adversely affect your Spring applications when integrating with these libraries. Spring's APIs provide a layer of |
24 | | -indirection along with enhanced capabilities (e.g. Exception translation). |
| 24 | +indirection along with enhanced capabilities (such as exception translation). |
25 | 25 |
|
26 | 26 | TIP: Spring Data for {geode-name} (SDG) also {spring-data-geode-docs-html}/#apis[offers] some relief when using |
27 | 27 | {geode-name}'s APIs. |
|
0 commit comments