Cache

[Julio Cesar Marques]

Hi there!

I'm planning to use a cache server (like redis) in my design.
Is that allowed?

I'm asking because in essay it says: "the architecture must be based on the Java EE platform"

[K. Tsang]

What make you think a Java EE architecture need to use a cache server?

[Julio Cesar Marques]

Well, in situations that i have to keep information in session I'll have problems on scaling my application (ps. a Sticky Session is not a valid solution in my POV) so, the Cache will keep that information and as long app scales information will be still available.

[K. Tsang]

Point noted.

But do remember objects in cache can still become outdated just like those transfer/value objects.

[Julio Cesar Marques]

I'm kind of afraid about use an (outsider) solution and that wouldn't be accepted.

[K. Tsang]

I don't recommend saying what product. A cache server is a cache server. For the assignment sake, a Java compatible cache server.

[Julio Cesar Marques]

Roger that!

[Heliton Rodrigues Aranha Filho]

For my 2 cents, I did specify the caching solution in the assumptions file. As long as the overall solution is JEE based, I don't think Oracle cares that much about minor components from other companies or open source groups (I've heard of people who got the cert and used Spring!)

Worry about providing the best solution for the business problem, that's what they care. The rest is just specs.

[Andres Olarte]

There's nothing wrong with using a cache server per se. I would just make sure that you justify the added complexity. Do you have a situation in which normal session replication wouldn't be suitable? If yes, then document that, and use your cache server to solve the problem.
I think the same with regards to mentioning Redis, if there something in particular in Redis that will help you solve the problem as opposed to something like HazelCast or Coherence? Then document that.
Otherwise it might seem like a "Golden Hammer": I know Redis, so I'm going to use Redis regardless of requirements.
I did mention a couple of very particular piece of software, to solve a critical part of the problem. In my solution I even had a whole section justifying that.

[Julio Cesar Marques]

Hi Andres!

This isn't a golden plate at all!
My requirement is very clear when it says application must be able to scale freely and in my opinion Session EJB or Managed bean session scoped is a huge blocker to this requirement. If in real life i refused to use Sticky sessions I won't do this in my assignment either!

In other matters i agreed with you!

Cheers!

[Mike Degteariov]

Hello Julio,

Do you want to cache the user input, that user enters across several screens ?
Or is this some other data ?

[Julio Cesar Marques]

Something like that, yes!
But major cases will be used to keep user data shared over N app instances on PaaS.
So... PaaS providers already have in their stacks Cache services, my plan is just consume that feature which is there ;)

Best Regards!