Gigaspaces.com - Application Server

Webinars Q&A - XAP 7.1 - Making Dynamic Scaling Simple

  • Is it actual JPA or JPA as a shell over JDO? (like Google uses JDO as a persistence API (in the Google cloud))
  • It’s an actual JPA that relies on the native query engine in our platform. The GigaSpaces XAP 7.1 release already includes a series of optimizations to our query engine to support this model. See 7.1 release notes for details.
  • What about security? This has been a major issue for us not to get on board with solutions such as Amazon. For example, they don't offer physical security of the server; anyone can walk away with it... We work in a strongly regulated environment (pharma), so compliance, audit trail and security are show stoppers...
  • Yes – in our earlier release we revamped our entire product security and now it covers all components of our middleware, from the administration tools to the data services. In XAP 7.1 we’ve added an enhanced security filter. You can read more about our security feature here
  • Is REST implementation available in XAP 7.1?
  • No. It will be available in our next release.
  • What has been improved/simplified in terms of persistency in XAP 7.1?
  • XAP 7.1. includes the following enhancements on our mirror services:
    1.Persistent redo-log – enables storing messages for a fairly long period while the mirror database is down, and reply to them as soon as it recovers.
    2.We added more fine-grained monitoring that provides a real-time view of the redo-log and the activity on the mirror side.
    3.Better handling of transaction scope. See 7.1 release notes for details.