Atomikos's profile picture. Reliability through Atomicity: manage your distributed transactions with our embeddable #java transaction manager - just drop it in your classpath and transact.

Atomikos

@Atomikos

Reliability through Atomicity: manage your distributed transactions with our embeddable #java transaction manager - just drop it in your classpath and transact.

Pinned

FREE Training Session: Microservice Data Consistency Pitfalls Trying to say "no" to distributed transactions? Watch this to learn about the distributed transactions you did not know you were doing atomikos.teachable.com/p/microservice…


Data loss doesn’t always look like an outage. Sometimes it is just one missing record that no one notices - until it is too late.


How Spreadshirt used Atomikos to migrate away from the JEE app server dld.bz/ggmpM #JavaEE

Atomikos's tweet image. How Spreadshirt used Atomikos to migrate away from the JEE app server dld.bz/ggmpM #JavaEE

Why LVM (insurance) uses Atomikos dld.bz/ggmrd

Atomikos's tweet image. Why LVM (insurance) uses Atomikos dld.bz/ggmrd

Advantages of a shared database for your microservices -only one High-Availability component to maintain and monitor -consistent backup images are possible -consistent hot-failover is easier Learn more (free training session) atomikos.com/Blog/SecretsAb… #microservices

Atomikos's tweet image. Advantages of a shared database for your microservices

-only one High-Availability component to maintain and monitor
-consistent backup images are possible
-consistent hot-failover is easier

Learn more (free training session)

atomikos.com/Blog/SecretsAb… 
#microservices

Here are some micro services best practices: - Keep code at a a similar level of maturity - Separate built for each microservice - Single responsibility - Deploy into containers - Micro frontend - Orchestrating microservices If you can only choose one which one would you choose?

Atomikos's tweet image. Here are some micro services best practices:
- Keep code at a a similar level of maturity
- Separate built for each microservice
- Single responsibility
- Deploy into containers
- Micro frontend
- Orchestrating microservices

If you can only choose one which one would you choose?

Microservice testing strategies: Which ones are you using? You can find out more about TDD in this presentation about "TDD: Where did it all go wrong?" infoq.com/presentations/…

Atomikos's tweet image. Microservice testing strategies: Which ones are you using?

You can find out more about TDD in this presentation about "TDD: Where did it all go wrong?" 
infoq.com/presentations/…

Eventually consistent is just a fancy way of saying “you’re on your own if it fails.”


The real architecture decisions aren’t in the diagrams. They are in how you handle failure, retries, and ordering.


How to make distributed transactions work in Tomcat dld.bz/ggmnv #tomcat

Atomikos's tweet image. How to make distributed transactions work in Tomcat dld.bz/ggmnv #tomcat

Disaster recovery: Imagine you need a bugfix in a hurry but the internet goes down dld.bz/ggjD9 #bugfix

Atomikos's tweet image. Disaster recovery: Imagine you need a bugfix in a hurry but the internet goes down dld.bz/ggjD9 #bugfix

Loading...

Something went wrong.


Something went wrong.