I’ve heard so many positive experiences with it. A true enterprise solution for a true enterprise problem, proven by the market and with a long history. Monica - Yes! Exactly! Just what I was thinking! It seems like a perfect match and the real deal for us. Absolutely fantastic! Everybody is so excited! I’ve been promoted to the role of an architect, so now I have to select the stack we will be using. We are planning on becoming the next Facebook or Google. So, we are building our Next Big Thing, you know. Monica - Hey John, glad you found some time for me. He’s a Hibernate expert, and he’s going to help you. Hibernate Sounds Like A Silver Bulletīen - Hello Monica, I’d like to introduce John. Fortunately, her colleague, Ben, knows the right guy. However, it is always a good idea to check a few things before starting a project. Hibernate is a well known and supported JPA standard. She knows that in the Java world there is only one good tool for handling database communication: Hibernate. Monica has recently been promoted to the role of architect and is now responsible for laying out the technology stack for a new product at her company. Let’s take a look at what can go wrong if you blindly use Hibernate just because it’s the accepted standard.Ĭonsider Monica, a Java developer. The obvious answer is to just use Hibernate, right? 90% of Java developers would agree with you, but does that make it the right decision? You want to support all kinds of data, and ideally, support all sorts of databases. You want to pick the best object-oriented abstraction of your flexible data model because you do not want to deal with plain SQL. You need to make the fundamental decisions that will stick with you for the rest of the project. Imagine that you are a Java developer, and you’re about to start your next big project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |