I think that from the development perspective, there isn't a big deal of difference between a monolith and microservices. Basically, once you have properly packaged your monolith in terms of business
domains etc like invoicing, finance, HR...., then it's just a question of creating a bunch of jar files in the proper format. Of course common modules may go in to web-inf/lib so all micro services can use that code.
However, what about monitoring after it goes to production? do you believe the IT industry currently has a good set of tools to say,
1) deploy 1/2 microservices in isolation,
2) administer a subset of services independent of others like performing property updates.
3) restart one/two microservices and ensure that the App is fine.
4) Restarting dependent services in proper order.
As a comparison, for a monolith running in jboss 7, all the above could be done via JMX-Console. Ideally something like this would suit for micro services.