• Need scalability? Don’t forget pricing

    In most discussions about scalability, we often approach the topic as a pure technical/architecture challenge, and ignore cost issues. The problem is that when we truly scale our application, and want to benefit from economies of scale, we’re going to…

  • GigaSpaces Training in Hong Kong from Oct 13-17, 2008

    GigaSpaces is proud to announce the successful completion of its first training course for its partners in Asia Pacific.  ' The 3-days Basic and 2-days Advance courses packed in a hectic programme with topics ranging from basic concepts of our Space Based Architecture such as Topologies, Cluster Schema, OpenSpaces Development Framework, Space Operations, Transaction Support, Messaging, Mirror Services, to more advanced topics such as Filters, Web Application Support and Apache Load Balancing, SLAs, Advanced Remoting and Execution Framework, and many
    Read More

  • Feedback on the GigaSpaces-EC2 Framework

    Our UK partners  NTE  posted on their a blog a detailed feedback  for the EC2 Framework private beta . Ian thanks for your feedback, we really appreciate it. 
    I have to say I’m quite excited by the amount of traction our EC2 and cloud solution is receiving these days.
    I encourage all of our users to provide feedback and suggest things we should do differently or better.  
    With that in mind, let me comment on Ian’s great feedback.
    Issue 1 – Adding ports to security groups
    You need to open the following ports on the “default” security group in order to use the framework 
    TCP Port 22 – used for SSH communication to the AMIs    
    TCP Port 80 – used for deploying the GigaSpaces Web Management Center and the Ganglia monitoring tool
    TCP Port 443 – used for secured http. (we fixed the typo, thanks!)
    You can do the above very easily using the elastic fox plugin (no need to install the Amazon API). Click the “security groups” tab and then click the “Grant Permission” green check mark. We will add this to our docs.
    The private beta currently supports the default security group. The next release will have support for custom security groups, and then it will be recommended to create your own group and not to use the default one. 
    Issue 2 – start-ui = true
    “true” and “admin application” is the same thing, in the next release we’ve changed the default in the data-example to be “admin-application”. 
    Issue 3 – Starting the GigaSpaces Management Tool. 
    In the current version we still have some issues with the UI connectivity, It has been fixed for the next release. Adding the nxclient local installation as a better workaround, is a good idea, we will updated the docs accordingly.
    Step-by-step Instructions
    The cloud framework can save some of the trouble of doing this, but obviously if you want to use the EC2 API directly, your post  contains a very helpful description. Thank you. We will work on adding a “step-by-step” guide to our WIKI as well.  
    A few notes I would like to add:
    1. As mentioned above I recommend using the FireFox Plugin  to open the ports.
    2. Please make sure the AWS Account ID you are using is dedicated to GigaSpaces (i.e. not used to run AMIs which are not GigaSpaces related), we don’t want to bill you for non-GigaSpaces usage :)
    3. Port 22 is used for SSH communication to the AMIs
    4. Monitoring – we have ganglia built-in to the cloud framework AMIs, you can point to the UI machine with /ganglia at the end of the public IP and view the entire cluster.
    Cheers
    Dekel
    Not a user yet? Interested in access to the private beta? Click here.
  • Feedback on the GigaSpaces-EC2 Framework

    Our UK partners  NTE  posted on their a blog a detailed feedback  for the EC2 Framework private beta . Ian thanks for your feedback, we really appreciate it. I have to say I’m quite excited by the amount of traction our EC2 and cloud solution …

  • Feedback on the GigaSpaces-EC2 Framework

    Our UK partners  NTE  posted on their a blog a detailed feedback  for the EC2 Framework private beta . Ian thanks for your feedback, we really appreciate it. 
    I have to say I’m quite excited by the amount of traction our EC2 and cloud solution is receiving these days.
    I encourage all of our users to provide feedback and suggest things we should do differently or better.  
    With that in mind, let me comment on Ian’s great feedback.
    Issue 1 – Adding ports to security groups
    You need to open the following ports on the “default” security group in order to use the framework 
    TCP Port 22 – used for SSH communication to the AMIs    
    TCP Port 80 – used for deploying the GigaSpaces Web Management Center and the Ganglia monitoring tool
    TCP Port 443 – used for secured http. (we fixed the typo, thanks!)
    You can do the above very easily using the elastic fox plugin (no need to install the Amazon API). Click the “security groups” tab and then click the “Grant Permission” green check mark. We will add this to our docs.
    The private beta currently supports the default security group. The next release will have support for custom security groups, and then it will be recommended to create your own group and not to use the default one. 
    Issue 2 – start-ui = true
    “true” and “admin application” is the same thing, in the next release we’ve changed the default in the data-example to be “admin-application”. 
    Issue 3 – Starting the GigaSpaces Management Tool. 
    In the current version we still have some issues with the UI connectivity, It has been fixed for the next release. Adding the nxclient local installation as a better workaround, is a good idea, we will updated the docs accordingly.
    Step-by-step Instructions
    The cloud framework can save some of the trouble of doing this, but obviously if you want to use the EC2 API directly, your post  contains a very helpful description. Thank you. We will work on adding a “step-by-step” guide to our WIKI as well.  
    A few notes I would like to add:
    1. As mentioned above I recommend using the FireFox Plugin  to open the ports.
    2. Please make sure the AWS Account ID you are using is dedicated to GigaSpaces (i.e. not used to run AMIs which are not GigaSpaces related), we don’t want to bill you for non-GigaSpaces usage :)
    3. Port 22 is used for SSH communication to the AMIs
    4. Monitoring – we have ganglia built-in to the cloud framework AMIs, you can point to the UI machine with /ganglia at the end of the public IP and view the entire cluster.
    Cheers
    Dekel
    Not a user yet? Interested in access to the private beta? Click here.
  • CloudCamp London is back

    It’s that time again. Cloud Camp London is scheduled for November 13th. CloudCamp is an unconference where early adopters of Cloud Computing technologies exchange ideas, and if you were there last time you will know what to expect, if not come along and get acquainted. It’s a great event to see new technologies and get to grips with the paradigm shift that is occurring.

    CloudCamp

  • GigaSpaces as Alternative to GoogleAppEngine for the Enterprise

    I Just came across an interesting post by Josh Heitzman who writes about his negative experience with Google App Engine, which led him to examine a list of Alternatives to Google App Engine. He points out GigaSpaces XAP as one…

  • Dynamic Service Deployment

    I recently created an integration with SunGrid Engine. This was easy to do – requiring only that a listener be written that hears JMX events that are produced by our product. As you may know, with GigaSpaces you can create watches for the services yo…

  • Cloud Summit Event in Sunny Tel Aviv

    Cloud summit event is coming up with lots of interesting lectures from Google, Yahoo, Amazon, eBayYou can see the full program here. In my presentation “Getting ready for the clouds” I’m going to talk about the steps that can be…

  • Memory Capacity Planning – The Footprint Benchmark

    The goal of this benchmark is to measure the memory footprint of the indexes the space maintains to boost read/take operations when searching for matching objects. This should help users to plan the amount of memory to allocate when doing their capacity planning prior deploying the application.  See blow the final Conclusions and the detailed report: – XAP 6.6 consumes less memory compared to XAP 6.5 with indexed data. – XAP 6.6 consumes about 85 bytes less per index value
    Read More