We’ve know it for a while, but this independent blog post confirms the facts: linear scalability.
Due to a server migration you may experiencing problems with support emails. We are working to resolve the problem.
In the meantime, thanks for your understanding and patience.
Check out this news post to learn more about DataNucleus and the details of this news item…
Best wishes for the new year to all of you, from all of us!
We are asking for community input on the following: over time, our initialization mechanism (property file, system properties, properties supplied programmatically) has been polluted a bit and as a result the lookups are not always intuitive. We would like to improve this and are working on a new design proposed here. Let us know what you think!
Proposed new property lookup procedure when Atomikos starts:
1. default properties are looked up via a property file in the Atomikos jars (should always be found)
2. override with specific custom properties looked up in the jta.properties file in the classpath (like now)
3. if no jta.properties found: NO logging to System.err any more (so no need to disable that with system props either)
4. override with specific properties that are set programmatically on the UserTransactionService
5. resolve any placeholder properties (i.e., ant-style expansion of references to other props)
6. this yields the final properties to use for the init procedure
What do you think? Did we miss something important?
BRIC countries have the tremendous opportunity to start out with no legacy, no old-style infrastructure like application servers, no message brokers, no enterprise service bus (ESB) or other nonsense like that - the typical stuff big enterprise vendors will try to trick you into (if they do: just ignore them - you will be better off).
Instead, BRIC countries have the luxury of being able to pick a light-weight model such as JEE without application server to achieve unlimited scalability at virtually no cost, using commodity hardware and software.
With the recent economic crises in both the US and Europe, it is the BRIC countries that are helping out (instead of the other way around). The future will involve a lot more BRIC. And with that, a lot more Atomikos.
Western companies that want to be as agile, productive and competitive as the BRIC countries: what are you waiting for? Call us to get an introduction and migration path for your legacy.
If you have been purchasing the ‘Enterprise Architecture’ portfolio from the big O then guess what: you’ve paid way too much for something you don’t need, and which will overload your (way too heavy) hardware even more.
We’ve been claiming this for years so it is about time to show it: how to replace Tuxedo applications with open source and free software. Coming soon to this site!
Stay with us…
PS Tuxedo is a registered trademark owned by Oracle
This blog post describes yet again how you can use best-of-breed components to do the job.
In particular, it describes integration of Atomikos as well as all of the other cool libraries that together outperform the application server in simplicity, cost and performance… Good job!
I would like to dedicate this post to all of our users who have been kind enough to give us their feedback via our online survey (you know, the one you receive by email once you register for download).
First of all, thank you very much for your feedback - this type of information is invaluable for any business, especially a start-up like us. Being agile as we are, any inconveniences found can be quickly corrected in our products and our business model.
So what are the results so far? Well, I won’t keep you in suspense any longer so let me just outline the summary:
- About 90% of the respondents would feel bad about missing our products in future projects
- About 60% have recommended our products to other people
Up to you to decide if this is good or bad - but we certainly are pleased with that result! Once again, a big thank you to our community!