Category Archives: Java/Java EE

Toastmasters Pathways – Research and Presenting

Posted on by
Reply

See my main Presentation Mastery Pathways page for some context. You become eligible to start this project after completing your icebreaker.

Again, you watch videos and answer questions interactively. The videos and questions cover both research and how to organize your speech. This means that the research and presenting speech is a mix of the old CC (Competent Communicator) speeches 2 and 7.

You get two worksheets to prepare. One is the speech outline to cover main points with support/evidence. The other is a guide to researching and citing your sources. The worksheets are another thing that differentiates Pathways from “the old way”. Both are useful if new to giving a speech. You don’t have to follow them if you want to organize your speech in a different way.

I gave my speech about SpeechCraft. Which is something I researched a few months ago. So research did happen. And it was great because my evaluation was done by someone who had never evaluated anyone before. He had a good observation that I hadn’t heard before. Different perspectives are great!

I was also Toastmaster at this meeting so I marked it off in my profile. See the logging your roles section for more on that.

SpringOne live blog – going cloud native at Comcast

Posted on by
Reply

Going Cloud Native at Comcast
Speaker: Todd Migliore

For more posts from Spring One 2017, see the Spring One blog table of contents

Problems

  • 10 year old services
  • Had to scale platform has a whole with physical services. Couldn’t scale one service
  • Shared release calendar for 15 dev teams.
  • Only did deployments once a month.
  • Took two hours to deploy all services.
  • Had to deploy in middle of night to minimize impact
  • Three level support team. Ops team split from dev and test teams. Finger pointing when there was an outage.
  • Data store was active (east coast) and passive (west coast.) There was a 60 minute outage to transfer. Instead would troubleshoot for an hour before giving up and having another hour outage.

The challenge

  • Needed to transform while still running

The approach

  • Held a submmit
  • Got smartest folks in room to answer “how are we going to get out of this mess”
  • Someone suggested migrating apps to cloud
  • Hard to move to cloud. WebSphere/WebLogic, rack database, monolith
  • Then someone suggested microservices

Microservices – why it should be small

  • Agile – deploy to prod in minutes
  • Elastic – scale in minutes
  • Resilient – survive outages form back end dependencies
  • Distributed – automatic failover
  • Event driven – stream data to other services
  • Developed and run by a single team
  • If you service talks to more than one dependency, it is not a microservice
  • Need to define what that one thing is for your microservice
  • Should own its own data.

Note: my session was right after this one so I spent the end getting ready for mine.

SpringOne live blog – Productize Your Service

Posted on by
Reply

Productize your Services – a path towards effective microservices development
Speaker: Stephan Hagemann (Pivotal)

For more posts from Spring One 2017, see the Spring One blog table of contents

Services

  • When do one big thing, split it into a bunch of smaller things
  • Who needs to talk to whom to see what they want to do

Agile

  • Boat analogy – agile is turning gracefully as quickly as need to
  • We don’t know what’s coming
  • Try to build in the right way

Lean

  • Less costly ways of learning what need to learn in order to know doing right thing
  • Ex: computer model before build physical object
  • Boat analogy – small boat, prototype

User centered design

  • Create solutions in context within constraints
  • Think about requirements
  • Constraints change over time. Ex: technological advancement
  • Through iterations, winner shapes next set of options

Two Speed IT – bad idea

  • Made slide red because bad idea
  • Idea that change is hard so will change customer facing apps first and leave the old stuff alone
  • Speed 1 – nothing happening
  • Speed 2 – go fast and then get stuck when need to wait for something at speed 1
  • Forcing people to use your API doesn’t work. That’s where shadow IT comes from.

Productized service

  • Nice story about out of date docs, people who changes jobs and eventually finding out a service wasn’t implemented. Then he showed the code. [I missed how the service got implemented. Or maybe that it was implemented and never went to prod]
  • Pivotal has marketplace so can find available service
  • Example of a nice service – see if license is valid for your artifacts