10 Considerations When Transferring Enterprise Applications to the Cloud
- Security - Data at Rest/Transit
- Software License Model
- Performance
- Disk I/O
- Application Infrastructure Sharing
- Hybrid Model
- Network Connectivity
- Prod /Non-Prod Environments
- Storage
- Open Source vs Proprietary
If you are using spring and JPA, it is very likely that you utilize ehcache (or another cache provider). And you do that in two separate scenarios: JPA 2nd level cache and spring method caching.
When you configure your application, you normally set the 2nd level cache provider of your JPA provider (hibernate, in my case) and you also configure spring with the “cache” namespace. Everything looks OK and you continue with the project. But there’s a caveat. If you follow the most straightforward way, you get two separate cache managers which load the same cache configuration file. This is not bad per-se, but it is something to think about – do you really need two cache manager and the problems that may arise from this?
Probably you don’t. So you have to get rid of the redundant manager. To do that, you need to set your spring cache manager as shared.
Cassandra Gets Atomic Batches, Virtual Nodes, CQL Improvements
Cassandra 1.2 was recently released with several improvements:
Cassandra Gets Atomic Batches, Virtual Nodes, CQL Improvements
Cassandra 1.2 was recently released with several improvements:
- Atomic batches for better transactional integrity, even if the coordinator fails mid-batch.
- Virtual Nodes allows better control over clustering. You can also upgrade an existing node to vnodes
- CQL3, with several improvements such as a new native binary protocol, support for collection types, a system keyspace.
- Faster serialization through use of binary format instead of JSON
- Cassandra 1.2 is designed to handle several terabytes of data per node, compared to upto 500 GB disk-space limit recommended in 1.0.
Are your Software Development Projects using Agile?
Gartner’s analysts (Thomas Murphy and David Norton) predict that by 2012 “agile development methods will be utilized in 80% of all software development projects”.
Spring 3.2 Released
- Asynchronous MVC processing on Servlet 3.0, with Spring MVC handler methods being able to return Callables and DeferredResults
- A ContentNegotiationStrategy is now available for resolving the requested media types from an incoming request.
- A new @MatrixVariable annotation which adds support for extracting matrix variables (name-value pairs within path segments) from the request URI.
- Improvements have been made to testing, with the inclusion of the formerly-standalone Spring MVC Test project, and support for loading WebApplicationContexts in the TestContext framework.
- Spring now allows for @Autowired and @Value to be used as meta-annotations, so that a developer can build custom injection annotations in combination with specific qualifiers.
- Spring provides an early CacheManager adapter for JCache, building against the JCache 0.5 preview. Full JCache support is expected next year, when Java EE 7 is released.
JAX-RS 2.0 and Bean Validation 1.1 First Java EE 7 JSRs to Win Public Approval
Java Enterprise Edition version 7 is well under way.
Oracle's JCP Program Office identifies the full Java EE 7 JSR feature list as:
- JSR 107: JCACHE - Java Temporary Caching API
- JSR 236: Concurrency Utilities for Java EE
- JSR 338: Java Persistence 2
- JSR 346: Contexts and Dependency Injection 1.1 for Java EE
- JSR 352: Batch Applications for the Java Platform
- JSR 349: Bean Validation 1.1
- JSR 339: JAX-RS 2.0: The Java API for RESTful Web Services
Sencha has created Fastbook, an HTML5 application closely mocking Facebook’s native application and displaying similar performance both on iOS and Android in an attempt to demonstrate that “HTML5 is ready.”
Mark Zuckerberg, CEO of Facebook, said a few months ago that “the biggest mistake that we made as a company is betting too much on HTML5 as opposed to native because it just wasn’t there,” and the company decided to create native applications for iOS and Android, the later being launched less than a week ago. The general comment was that HTML5 is not “ready”, it is not fast enough, and there are difficulties developing it due to lack of proper tooling.
No comments:
Post a Comment