[Java programming language only]

Planning to develop Java applications

Before you develop Java applications, you should be familiar with the available APIs, plug-ins, and any considerations that are required.

Java API overview
WebSphere® eXtreme Scale provides several features that are accessed programmatically using the Java™ programming language through application programming interfaces (APIs) and system programming interfaces.
Java plug-ins overview
A WebSphere eXtreme Scale plug-in is a component that provides a certain type of function to the pluggable components that include ObjectGrid and BackingMap. WebSphere eXtreme Scale provides several plug points to allow applications and cache providers to integrate with various data stores, alternative client APIs and to improve overall performance of the cache. The product ships with several default, prebuilt plug-ins, but you can also build custom plug-ins with the application.
REST data services overview
The WebSphere eXtreme Scale REST data service is a Java HTTP service that is compatible with Microsoft WCF Data Services (formally ADO.NET Data Services) and implements the Open Data Protocol (OData). Microsoft WCF Data Services is compatible with this specification when using Visual Studio 2008 SP1 and the .NET Framework 3.5 SP1.
Spring framework overview
Spring is a framework for developing Java applications. WebSphere eXtreme Scale provides support to allow Spring to manage transactions and configure the clients and servers comprising your deployed in-memory data grid.
Java class loader and classpath considerations
Because WebSphere eXtreme Scale stores Java objects in the cache by default, you must define classes on the classpath wherever the data is accessed.
Relationship management
Object-oriented languages such as Java, and relational databases support relationships or associations. Relationships decrease the amount of storage through the use of object references or foreign keys.
Cache key considerations
WebSphere eXtreme Scale uses hash maps to store data in the grid, where a Java object is used for the key.
Data for different time zones
When inserting data with calendar, java.util.Date, and timestamp attributes into an ObjectGrid, you must ensure these date time attributes are created based on same time zone, especially when deployed into multiple servers in various time zones. Using the same time zone based date time objects can ensure the application is time-zone safe and data can be queried by calendar, java.util.Date and timestamp predicates.

Parent topic: Planning to develop WebSphere eXtreme Scale applications

Related tasks

Planning to develop Microsoft .NET applications

Last updated: 2021-03-29