Friday Meeting Summary, Jan 30
This week, I’m teaching the Resin administration course, so last week’s meeting dealt a lot with preparations for that and the focus of the training. We’ll be discussing Resin 3.1 in depth this time, as opposed to last time when we also include Resin 3.2. Now that 3.2 is turning into Resin 4.0 and the first release isn’t out yet, we wanted to show the students a nice stable version.
The other main topic of the meeting was technical whitepapers. Nam is working on finishing up with his paper on Quercus performance (preview: 400% over standard PHP with APC), so that should be available quite soon. The other whitepaper we have in the planning stages is for the new Resin 4.0 cloud functionality. We had a nice phone meeting with a customer on Thursday to give a roadmap of where Resin and Caucho are going and they were very interested in using the cloud features, so we got even more inspired. This particular customer was interested in doing an internal EC2-like deployment (I think they meant hot redeploys with virtualization), so Resin 4.0’s capabilities would fit that quite well. They wanted more in-depth details about how Resin will achieve 1) distributed caching/sessions 2) cluster-wide deployment and 3) dynamic start and stop of cluster members. So far we’ve discussed the clustering in high-level terms, but now that it’s becoming real, it seems people want to get technical to convince themselves it will actually work and to see if it will fit the purpose they have in mind.
We had a brainstorming session on the topics we want to make sure are in the cloud whitepaper. They’re listed below. Please take a look at them and if you see anything missing, we’d love to hear about it.
- What is the triad?
- Distributed caching
- GIT repository
- Distributed sessions
- Remote deployment
- Timeouts and timing
- Persistence
- Consistency
- Queuing/pipelining
- EDA
- How will the cluster be organized?
- Inter/intra-cluster communication
- Virtualization
- Logical and application partitioning
- Dynamic reprovisioning
- Standby startup
- Mechanics of deployment
- Management
- Cache maintenance messages
- Repository distribution messages
Obviously this is a sloppy, brainstormed list, but if you see anything glaringly missing or something you think we should spend a lot of time on that is listed, please comment below. Thanks!