Baruch Sadogursky

David Sachdev wrote:As a Software Architect that has spend the last handful of years with a strong focus on the DevOps and Cloud world, it will be very interesting to see your approach to the task.  I'm curious how much of the book focuses in on MicroServices, and how to migrate there - and if there is a focus on greenfield MicroServices development.  Looking over your tools most are familiar, but some are new to me - and I'm looking forwared to digging into some of those new tools and digging in.

Sounds good! Let us know if you have any questions

Maven is only one of the tools we show in the book, not because we promote it, but because the industry uses it. It is the most popular build tool and package manager for Java, and it works perfectly in the DevOps setting, being a "project comprehension tool" (as Maven describes itself) it makes the build project understandable and predictable for all parties.

Kingsly Theodar Rajasekar wrote:As a DevOps architect, I wonder what this book covers in terms of security in pipeline?  Especially with the recent security incidents like SolarWinds where they say root cause is their DevOps pipeline.  Likewise does this book also cover policy-as-code, or similar mechanics to enforce security in CI or CD pipeline?

Great question! We have an entire chapter on security where we talk about exactly that – supply chain security. You gonna love it!

Sun also see Constansts Interface as an antipattern. This is the primary reason for the "static import" feature, which is now applied in J2SE 1.5.

What I ment by utilty class is a helper class with static methods, and maybe some a REALY global constansts either. As much as I know it is a well sread practice with nothing wrong with it.

Constants interface considered a design antipattern. Don't use it. Just arrange the constants in classes they belong to. Another possibilty is to create utility class. It may consist only variables for start, but you may wish to add some helper methods in it later.

If the user can't find the record, it can be of varios reasons - record not found between other records, record marked as deleted, or record can not be read. Those are different causes of the same problem. I wrapped the IOException in RecordNotFoundException. It makes sense to me.

The option of passing the locking responsibility to the client brings a lot of complexivity to the application. Once you follow that strategy, you should track inactive/disconnected clients, in other words, make your server stateful.
On the other hand, by using a proxy or a facade you make the locked operations atomic, which release you from the need of mantainig conversation state with the client, makes your life easier, the application simplier, and once you'll want to change the locking strategy, you can switch the facade, or get rid of it totally.

One question - why to notify after adding cookie to the HashTable? How adding the lock to the table can change the waiting condition of the waiting threads? Correct me if I am wrong, but the only place in which the waiting condition can change is in the unlock() method - so it's the place to notify.

I have a big problem with the update() method, which doesn't throw the damn exception... Invent some RuntimeException while DuplicateKeyException exists seems somewhere ugly to me. I ignore it for meanwhile, but have opened a Thread in mind...

Baruch Sadogursky
Israel
No. 32

Originally posted by Satish Avadhanam:
On the client side, I catch RuntimeException to indicate the server has been shutdown and application has to be terminated.

Catching RuntimeException doesn't seem quite right for me in any circumstances.

The really interesting thing happen, when using UTF-8 encoding. In UTF-8 the chars can be both one or two bytes, so multiply by 2 won't work.

What do you mean by "won't be able to show it"? Sun will sue you if you'll show the code you wrote to someone? Come on, you taking the whole thing way too far. My SCJD project is my, pretty worthless (as a product) code! Once I will pass - I'll do with it whatever I want, if I'll find what to do with it.

Satish, if you don't mind about the copyright issues, send me your assignment, I want to check, that you really don't have more serious issues to take care of