3:39 a.m.
Whilst we were in Antwerp, Manik, Shane, Rodney and I sat down to think a bit about what
this means. A few of the salient points we discussed are:
Good clustering support (Pete)
---------------------------------
* Ensure we always externalize any application state e.g. store it in the session, CDI
supports this beautifully!
* Make sure we can externalize "framework" state i.e. any state we store in the
framework that can't be trivially rediscovered when a new node starts. The Weld core
works like this, as do portable extensions which are coded well, and use Contextual to
store state.
- An idea is to add the ability to generate the class metadata (and perhaps even the
bean metadata?) at compile time, and store in some binary format inside the jar. This can
then be read in when the app starts, rather than using reflection to study the classes.
This may lead to faster boot (needs research!)
* Think about replication when we write the core, extensions and apps, and ensure that we
allow for efficient replication
Multi-tennanted apps (Shane is going to lead this effort)
-----------------------------
* How are they configured externally from the app itself (e.g. the idea for how to read in
properties Gavin blogged about)
* Isolation
* Security?
* Integrating with distributed datastores such as Infinispan, this is intrusive into your
data model as some things which work well in RDBMS don't work so well here
Testing (Pete)
----------
* Mainly infrastructure for us, may be useful for others?
* How do we test in GAE?
* How do we test in EC2/Rackspace (talk to Bob McWhirter)
Images (Shane)
----------
* Thincrust images e.g. with Weld installed onto Tomcat (useful for getting started?)
11:26 a.m.
New subject: [seam-dev] Weld/Seam in the cloud
Hi Pete,
Very interesting, bad luck I couldn't attend this event. Don't forget
about the Hibernate Search/Lucene indexes: The Hibernate Search and
Infinispan teams are managing a joined effort to produce a distributed
Lucene directory to store the index state in Infinispan.
For status updates track HSEARCH-307 (yet to implement), or have a look into
http://www.jboss.org/community/wiki/InfinispanasaDirectoryforLucene
regards,
Sanne
2009/11/21 Pete Muir <pmuir(a)redhat.com>:
Whilst we were in Antwerp, Manik, Shane, Rodney and I sat down to
think a bit about what this means. A few of the salient points we discussed are:
Good clustering support (Pete)
---------------------------------
* Ensure we always externalize any application state e.g. store it in the session, CDI
supports this beautifully!
* Make sure we can externalize "framework" state i.e. any state we store in the
framework that can't be trivially rediscovered when a new node starts. The Weld core
works like this, as do portable extensions which are coded well, and use Contextual to
store state.
- An idea is to add the ability to generate the class metadata (and perhaps even the
bean metadata?) at compile time, and store in some binary format inside the jar. This can
then be read in when the app starts, rather than using reflection to study the classes.
This may lead to faster boot (needs research!)
* Think about replication when we write the core, extensions and apps, and ensure that we
allow for efficient replication
Multi-tennanted apps (Shane is going to lead this effort)
-----------------------------
* How are they configured externally from the app itself (e.g. the idea for how to read
in properties Gavin blogged about)
* Isolation
* Security?
* Integrating with distributed datastores such as Infinispan, this is intrusive into your
data model as some things which work well in RDBMS don't work so well here
Testing (Pete)
----------
* Mainly infrastructure for us, may be useful for others?
* How do we test in GAE?
* How do we test in EC2/Rackspace (talk to Bob McWhirter)
Images (Shane)
----------
* Thincrust images e.g. with Weld installed onto Tomcat (useful for getting started?)
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
6:17 a.m.
New subject: [seam-dev] Weld/Seam in the cloud
Hi Sanne,
Yes, as part of the "integrating with distributed databases" we did talk a bit
about how the Hibernate Search is a good match for the cloud. Really, this item on the
todo list is more of a documentation/blog/tutorial issue, than something we can address
IMO. Something to make sure people are aware of...
Pete
On 22 Nov 2009, at 17:26, Sanne Grinovero wrote:
Hi Pete,
Very interesting, bad luck I couldn't attend this event. Don't forget
about the Hibernate Search/Lucene indexes: The Hibernate Search and
Infinispan teams are managing a joined effort to produce a distributed
Lucene directory to store the index state in Infinispan.
For status updates track HSEARCH-307 (yet to implement), or have a look into
http://www.jboss.org/community/wiki/InfinispanasaDirectoryforLucene
regards,
Sanne
2009/11/21 Pete Muir <pmuir(a)redhat.com>:
> Whilst we were in Antwerp, Manik, Shane, Rodney and I sat down to think a bit about
what this means. A few of the salient points we discussed are:
>
> Good clustering support (Pete)
> ---------------------------------
> * Ensure we always externalize any application state e.g. store it in the session,
CDI supports this beautifully!
> * Make sure we can externalize "framework" state i.e. any state we store in
the framework that can't be trivially rediscovered when a new node starts. The Weld
core works like this, as do portable extensions which are coded well, and use Contextual
to store state.
> - An idea is to add the ability to generate the class metadata (and perhaps even
the bean metadata?) at compile time, and store in some binary format inside the jar. This
can then be read in when the app starts, rather than using reflection to study the
classes. This may lead to faster boot (needs research!)
> * Think about replication when we write the core, extensions and apps, and ensure
that we allow for efficient replication
>
>
> Multi-tennanted apps (Shane is going to lead this effort)
> -----------------------------
> * How are they configured externally from the app itself (e.g. the idea for how to
read in properties Gavin blogged about)
> * Isolation
> * Security?
> * Integrating with distributed datastores such as Infinispan, this is intrusive into
your data model as some things which work well in RDBMS don't work so well here
>
>
> Testing (Pete)
> ----------
> * Mainly infrastructure for us, may be useful for others?
> * How do we test in GAE?
> * How do we test in EC2/Rackspace (talk to Bob McWhirter)
>
>
> Images (Shane)
> ----------
> * Thincrust images e.g. with Weld installed onto Tomcat (useful for getting
started?)
> _______________________________________________
> seam-dev mailing list
> seam-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
5512
days inactive
5514
days old
2 comments
2 participants
participants (2)
-
Pete Muir -
Sanne Grinovero